Conversion and lifecycle
Technical sales enablement
Help a technical champion turn demonstrated value and unresolved risks into an informed internal decision.
Open-source skill · format validated
When this is useful
Create discovery guides, technical evaluation plans, champion briefs, objection handling, and sales handoffs for developer tools and data products. Use for moving a qualified technical evaluation toward an informed buying decision; not for sending unsolicited outreach.
What to bring
Prospect task and environment, user/champion/buyer/reviewer roles, observed value, remaining objections, buying process, and authorized evidence.
What you can work toward
A discovery or evaluation plan, role map, evidence-backed objection table, champion brief, and owned next step.
Developer-tool version
Turn an individual successful task into an honest team-evaluation memo: dependency and maintenance owner, integration effort, deployment and security review, commercial fit, reversibility, and an owned next test. Do not call a local demo production adoption.
Data-product version
Turn a reconciled evaluation slice into an honest decision memo: source/destination fit, approved data boundary, recovery, recurring operation, procurement, cost predictability, and owner. State remaining production tests and a no-go option.
How to use it
Choose the version for your product type and follow its repository installation instructions. Keep the skill folder, references and any assets together. Each skill works on its own; reuse a shared brief when helpful rather than repeating a full intake.
The source follows the open Agent Skills format and is MIT licensed. Live research and execution depend on the tools and permissions available in your host. Preparing a plan or draft does not itself authorize publishing, messaging, spending or production changes.
A starting prompt
Use the technical sales enablement skill for our developer tool or data product. Our task is [specific task], our supported environment is [environment], and the decision is [decision]. Use these facts and sources: [evidence]. Produce the requested artifact, label unknowns, and do not invent results or perform external actions beyond my authorization.
How to judge the result
Do not turn a successful demo into a claimed customer outcome. Do not treat unverified certifications or roadmap items as currently available.
Check that the product-specific version changes the recommendation, the requested deliverable is complete, and proposed tests are distinguished from observed results. Format validation does not establish how a model will perform on your product.
From input to reviewed output
Put it to work
- Choose the collection for your product type and install the relevant skill with its bundled references and assets.
- Supply the task, supported behavior, existing evidence and constraints that affect the decision. Reuse context already available.
- Ask for the concrete deliverable, distinguishing facts, hypotheses, unknowns and any untested instructions.
- Check the product-specific acceptance criteria, source claims and next steps before using or publishing the output.
Limits and tradeoffs
Do not turn a successful demo into a claimed customer outcome. Do not treat unverified certifications or roadmap items as currently available. No fresh-host model performance is claimed; verify output against your product, evidence and authorized environment.