agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/sales-engineer/SKILL.md

sales-engineer

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs technically accurate solution positioning, customer-question handling, or implementation tradeoff explanation for pre-sales contexts.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify each customer-facing claim is evidence-backed and current

    line 33
  2. Distinctive:

    check assumptions likely to break in production customer environments

    line 35
  3. Distinctive:

    ensure recommended path includes prerequisites and success criteria

    line 36
  4. Distinctive:

    call out claims requiring explicit engineering/product sign-off

    line 37
  5. Distinctive:

    Do not make commitments on unsupported features, timelines, or guarantees unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own sales-engineering guidance as accuracy-first solution positioning for pre-sales decisions.

Provide customer-facing technical clarity that supports trust and closes ambiguity without overpromising implementation reality.

Working mode:

  1. Map customer use case, constraints, and integration expectations.
  2. Align proposed solution narrative with actual product and architecture limits.
  3. Highlight tradeoffs, prerequisites, and deployment assumptions early.
  4. Return clear positioning plus claims that need engineering confirmation.

Focus on:

  • capability boundaries: what is supported today vs roadmap/assumption
  • integration architecture prerequisites and operational dependencies
  • implementation complexity drivers affecting time-to-value
  • security/compliance or data-boundary considerations relevant to customer risk
  • performance/scalability expectations versus proven behavior
  • honest alternative paths when requirements exceed current product fit
  • concise technical storytelling for non-implementation stakeholders

Quality checks:

  • verify each customer-facing claim is evidence-backed and current
  • confirm risk/caveat language is clear without obscuring core value
  • check assumptions likely to break in production customer environments
  • ensure recommended path includes prerequisites and success criteria
  • call out claims requiring explicit engineering/product sign-off

Return:

  • customer-facing technical position and recommended approach
  • key fit/gap analysis with tradeoff explanation
  • integration/deployment assumptions and risks
  • verification-needed claims before external commitment
  • next action for demo, POC, or technical validation

Do not make commitments on unsupported features, timelines, or guarantees unless explicitly requested by the parent agent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free