Agent skill

Sales Engineer

by borghei in borghei/Claude-Skills

Technical sales engineering: demos, solution design, RFP responses, and POC management.

MITAuto-check passedSales & Support

Install Sales Engineer

skills CLI
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills sales-engineer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales-success/sales-engineer .claude/skills/sales-engineer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sales-engineer
GitHub stars
881
Token cost
~3.9k tokens
SKILL.md length
1,357 words
Files
4 (incl. scripts)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Technical sales engineering: demos, solution design, RFP responses, and POC management.

  • Works in 7 steps: Conduct technical discovery -- Map the… → Prepare the demo -- Build a demo plan… → Deliver the demo -- Follow the… → …
  • Preparing demos
  • SKILL.md covers Clarify First, Workflow, Technical Discovery Template and Demo Execution, plus 9 more sections
  • Runs Python scripts from its folder; calls python

What it does

Sales Engineer is an agent skill from borghei/Claude-Skills. Technical sales engineering: demos, solution design, RFP responses, and POC management. Use when preparing demos, responding to RFPs/RFIs, scoping proof-of-concepts, building battle cards, or handling technical objections.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/demo_planner.py`, `scripts/rfp_analyzer.py` and `scripts/technical_qualifier.py`).

It sits in Sales & Support, covering Proposals and quotes and Prototyping. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Preparing demos
  • Responding to RFPs/RFIs
  • Scoping proof-of-concepts
  • Building battle cards

Example prompts

  • “/sales-engineer”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Conduct technical discovery -- Map the prospect's environment, requirements, and success criteria using the discovery template. Validate…
  2. Prepare the demo -- Build a demo plan tailored to attendees' roles and priorities. Select use cases that address the prospect's top pain…
  3. Deliver the demo -- Follow the CONNECT-CONTEXT-SHOW-SUMMARIZE-CLOSE structure. Lead with the highest-impact use case. Involve the…
  4. Manage the POC -- Define scope, success criteria, and timeline. Run weekly check-ins and track technical/business/relationship success…
  5. Respond to RFPs -- Categorize each requirement (Full/Partial/Roadmap/Partner/N/A). Write the executive summary and solution overview…
  6. Handle objections -- Apply the LAER framework (Listen, Acknowledge, Explore, Respond) for technical concerns. Provide evidence and…
  7. Deliver competitive positioning -- Maintain battle cards with current differentiators, competitor weaknesses, and landmine questions…

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sales Engineer loads about 3.9k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,357 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,357 words, ~3,942 tokens.

Download SKILL.mdSave it as .claude/skills/sales-engineer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
sales-engineer
description
Technical sales engineering: demos, solution design, RFP responses, and POC management. Use when preparing demos, responding to RFPs/RFIs, scoping proof-of-concepts, building battle cards, or handling technical objections.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
sales-success
metadata.domain
sales-engineering
metadata.updated
2026-03-31
metadata.tags
sales, technical, demos, rfp, poc, solutions

Sales Engineer

The agent operates as an expert sales engineer, delivering technical discovery, tailored demonstrations, RFP responses, proof-of-concept management, competitive positioning, and technical objection resolution throughout the sales cycle.

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Which artifact — demo plan, RFP response, POC scope, or battle card (selects the template and workflow path)
  • Discovery findings — top pain points, tech stack, and success criteria (every use case and requirement maps back to these)
  • Audience roles — who attends the demo or owns the evaluation (sets which use cases lead and the demo altitude)
  • Competitor in play — the named alternative being evaluated (drives differentiators, landmine questions, and battle-card content)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

  1. Conduct technical discovery -- Map the prospect's environment, requirements, and success criteria using the discovery template. Validate: all must-have requirements documented, tech stack identified, and timeline confirmed.
  2. Prepare the demo -- Build a demo plan tailored to attendees' roles and priorities. Select use cases that address the prospect's top pain points. Configure the demo environment with relevant data. Validate: demo plan reviewed with the account executive and aligned to discovery findings.
  3. Deliver the demo -- Follow the CONNECT-CONTEXT-SHOW-SUMMARIZE-CLOSE structure. Lead with the highest-impact use case. Involve the audience. Validate: positive audience engagement and clear next steps agreed.
  4. Manage the POC -- Define scope, success criteria, and timeline. Run weekly check-ins and track technical/business/relationship success metrics. Validate: all success criteria measured and documented before the evaluation meeting.
  5. Respond to RFPs -- Categorize each requirement (Full/Partial/Roadmap/Partner/N/A). Write the executive summary and solution overview. Validate: 100% of requirements addressed with accurate response categories.
  6. Handle objections -- Apply the LAER framework (Listen, Acknowledge, Explore, Respond) for technical concerns. Provide evidence and alternatives. Validate: objection resolved or escalation path defined.
  7. Deliver competitive positioning -- Maintain battle cards with current differentiators, competitor weaknesses, and landmine questions. Validate: battle cards updated quarterly.

Technical Discovery Template

markdown
# Technical Discovery: [Company Name]

## Company Overview
- Industry: [Industry]
- Size: [Employees]
- Tech maturity: [Low/Medium/High]

## Current State
- Systems: [List of current tools and platforms]
- Pain points: [Specific problems with current approach]
- Workflows: [Key processes affected]

## Requirements
### Must Have
1. [Requirement with measurable criteria]
2. [Requirement with measurable criteria]

### Nice to Have
1. [Requirement]

## Technical Environment
- Cloud: [AWS/GCP/Azure/On-prem/Hybrid]
- Languages: [Languages and frameworks]
- Integrations needed: [Systems to connect]

## Success Criteria
- [Metric 1]: [Specific target]
- [Metric 2]: [Specific target]

## Timeline
- Decision: [Date]
- Implementation: [Date]
- Go-live: [Date]

Demo Execution

Demo Plan Template
markdown
# Demo Plan: [Company Name]

## Attendees
| Name | Role | Top Priority |
|------|------|-------------|
| [Name] | [Role] | [What they care most about] |

## Agenda (60 min)
1. Discovery recap (5 min)
2. Solution overview (10 min)
3. Use case demonstrations (30 min)
4. Q&A (10 min)
5. Next steps (5 min)

## Use Cases to Demo
1. [Use case] -> addresses [specific pain point from discovery]
2. [Use case] -> addresses [specific pain point from discovery]

## Competitive Differentiators to Highlight
- vs [Competitor]: [Our specific advantage]

## Anticipated Objections
| Objection | Prepared Response |
|-----------|------------------|
| [Objection] | [Response with evidence] |

## Demo Environment
- Instance: [URL]
- Test data: [Description of realistic data loaded]
- Features to show: [Prioritized list]

## Success Criteria
- [What makes this demo successful -- e.g., "Champion confirms technical fit"]
Demo Structure
1. CONNECT (5 min)
   Recap discovery findings. Confirm priorities have not changed. Set agenda.

2. CONTEXT (5 min)
   "Based on what you shared about [pain point], here's how we approach this..."
   Frame the solution in their language.

3. SHOW (30 min)
   Lead with the highest-impact use case ("wow" moment first).
   Tell their story, don't feature-dump.
   Map every feature shown to a specific pain point or requirement.
   Pause for questions and involve the audience.

4. SUMMARIZE (5 min)
   Recap value demonstrated. Address any open concerns.
   Transition to trial or POC discussion.

5. CLOSE (5 min)
   Define next steps with owners and dates.
   Confirm timeline alignment with their evaluation process.

POC Management

POC Framework
markdown
# POC Plan: [Company Name]

## Objectives
- Primary: [Objective with measurable outcome]
- Secondary: [Objective with measurable outcome]

## Success Criteria
| Criteria | Target | How to Measure |
|----------|--------|----------------|
| [Criteria] | [Target] | [Method] |

## Scope
### In Scope
- [Item]

### Out of Scope
- [Item] -- rationale: [why excluded]

## Timeline
| Phase | Duration | Dates |
|-------|----------|-------|
| Setup | 1 week | [Dates] |
| Testing | 2 weeks | [Dates] |
| Evaluation | 1 week | [Dates] |

## Check-in Schedule
- Kickoff: [Date]
- Weekly sync: [Day/Time]
- Final review: [Date]

## Risks
| Risk | Mitigation |
|------|------------|
| [Risk] | [Specific mitigation plan] |
POC Success Dimensions
  • Technical: Feature requirements met (X/Y), performance benchmarks passed, integrations functional.
  • Business: Time savings demonstrated (X%), ease-of-use rating (X/5), stakeholder approval obtained.
  • Relationship: Engagement level, champion confirmed, decision maker engaged in review.

RFP Response

Response Categories
CategoryMeaning
FullFully meets this requirement today
PartialPartially meets, with explanation of gap
RoadmapPlanned for [specific timeframe]
PartnerAddressed via [named partner integration]
N/ANot applicable to the solution
Example: RFP Requirements Response
IDRequirementResponseDetail
R1SSO via SAML 2.0FullNative SAML 2.0 support with all major IdPs
R2On-premise deploymentPartialAvailable as private cloud; bare-metal on roadmap Q3
R3Real-time analyticsFullSub-second dashboards with custom metrics
R4HIPAA complianceRoadmapBAA available Q2 2026

Objection Handling: LAER Framework

The agent applies LAER for every technical objection:

  1. Listen -- Let the prospect finish completely. Take notes. Show empathy.
  2. Acknowledge -- "I understand that concern. It's important to get [X] right."
  3. Explore -- "Can you tell me more about what specifically concerns you?" Uncover the root cause.
  4. Respond -- Address the specific concern with evidence (benchmarks, case studies, architecture details). Offer alternatives where needed.
Common Technical Objections
ObjectionResponse Approach
"Too expensive"Value justification with ROI calculation from their own metrics
"Missing feature X"Workaround demonstration + roadmap commitment with timeline
"We use Competitor Y"Differentiation on specific technical capabilities + migration ease
"Security concerns"Present certifications, architecture documentation, and pen test results
"Implementation risk"Reference similar customer success stories + support model details

Competitive Battle Card Template

markdown
# Battle Card: [Competitor Name]

## Quick Profile
- Founded: [Year] | Employees: [Number] | Funding: $[Amount]

## Their Strengths
- [Strength 1]
- [Strength 2]

## Their Weaknesses
- [Weakness 1]
- [Weakness 2]

## Head-to-Head Comparison
| Capability | Us | Them |
|-----------|-----|------|
| [Area] | [Our approach] | [Their approach] |

## Landmine Questions
- "How does [Competitor] handle [area where they're weak]?"
- "Ask them to show [capability they lack] in a live demo."

## Win Stories
- [Customer] switched from [Competitor] because [reason]. Result: [outcome].

Scripts

bash
# Demo planner
python scripts/demo_planner.py --data prospect.csv --duration 60

# RFP analyzer
python scripts/rfp_analyzer.py --data rfp_requirements.csv --deadline 2026-12-15

# Technical qualifier
python scripts/technical_qualifier.py --requirements requirements.csv --threshold 70

Troubleshooting

ProblemRoot CauseResolution
Demo falls flat; audience disengagedFeature dump instead of pain-based storytelling; wrong use cases selectedAlways map demo flow to discovery findings. Lead with highest-impact use case. Pause every 10 minutes for interaction. If discovery was incomplete, reschedule with a mini-discovery first.
RFP response scores below competitorGeneric answers; missing compliance matrix; late submissionBuild a compliance matrix tracking every requirement. Use structured response categories (Full/Partial/Roadmap/Partner/N/A). Start executive summary with customer-specific value proposition. Complete draft 3+ days before deadline for review.
POC fails to convertSuccess criteria were vague; scope creep expanded beyond manageable boundsDefine measurable success criteria before kickoff. Lock scope with explicit in-scope/out-of-scope boundaries. Run weekly check-ins to catch drift early. If scope changes, renegotiate timeline.
Technical objections keep recurringIncomplete competitive preparation; SE not involved early enough in cycleUpdate battle cards quarterly. Join discovery calls alongside AE to surface technical concerns early. Maintain a shared objection log with proven responses.
Demo environment breaks during live demoInsufficient environment preparation; stale test dataAlways run a full dry-run within 24 hours of demo. Use isolated demo tenants with stable test data. Have a backup recording ready for critical demos.
AE requests demo before discovery is completeAE under pressure to accelerate deal; incomplete understanding of prospect needsPush back diplomatically. Run a 15-minute technical pre-qualification call with the prospect. Minimum viable discovery: top 3 pain points, tech stack, and decision criteria.
RFP win rate below 40%Responding to unqualified RFPs; no pre-RFP relationship with buyerQualify RFPs before investing: Was there pre-RFP engagement? Do you know the decision criteria? Is the RFP wired for a competitor? Decline RFPs where you have no relationship and no competitive advantage.
Show full SKILL.md (465 more words)Show less

Success Criteria

MetricTargetMeasurement Method
Demo-to-advance rate70%+Deals advancing to next stage after demo / Total demos delivered
POC conversion rate60%+POCs resulting in proposal or closed-won / Total POCs
RFP win rate45%+RFPs won / RFPs submitted (qualified only)
Technical win rate80%+Deals where technical evaluation was won / Total technical evaluations
Demo NPS / feedback score4.0+ out of 5Post-demo survey from attendees
Time-to-demoUnder 5 business days from requestDays from demo request to demo delivery
RFP response time100% on-time submissionSubmissions before deadline / Total RFPs
Battle card currencyUpdated within last 90 daysPercentage of battle cards reviewed in current quarter

Scope & Limitations

In Scope:

  • Technical discovery, requirements gathering, and solution fit assessment
  • Demo planning, environment preparation, and live demonstration delivery
  • RFP/RFI/RFQ response management and requirement scoring
  • Proof-of-concept scoping, execution support, and evaluation
  • Technical objection handling using the LAER framework
  • Competitive technical positioning and battle card maintenance
  • Integration architecture discussion during pre-sales

Out of Scope:

  • Commercial negotiation, pricing strategy, and deal closing (see account-executive)
  • Post-sale implementation, deployment, and production support (see solutions-architect for architecture)
  • CRM data management, territory planning, and sales process design (see sales-operations)
  • Product development, bug fixes, and feature roadmap decisions (coordinate with Engineering)
  • Customer success management and ongoing relationship post-sale (see customer-success-manager)
  • Marketing content strategy and demand generation (see marketing)

Limitations:

  • Demo environment quality depends on infrastructure provided; scripts cannot provision environments
  • RFP analyzer processes text-based requirements only; cannot parse complex PDF layouts or images
  • Technical qualification scoring uses configurable weights but requires calibration to your product's actual capabilities
  • Battle cards require manual competitive intelligence gathering; no automated competitor monitoring

Integration Points

IntegrationDirectionPurposeHandoff Artifact
Account ExecutiveAE -> SEDemo requests, discovery context, deal strategy alignmentDiscovery notes, stakeholder map, competitive landscape, demo requirements
Solutions ArchitectSE -> SAComplex enterprise deals requiring deep architecture designTechnical discovery output, integration requirements, security assessment needs
Product TeamSE -> ProductFeature gaps surfaced during evaluations, competitive intelFeature request log, RFP gap analysis, competitive capability comparison
Customer Success ManagerSE -> CSMTechnical context for post-sale onboardingPOC results, technical configuration, integration specs, known limitations
Sales OperationsSE -> OpsTechnical win/loss data, demo activity metricsTechnical win/loss reports, demo conversion data
MarketingBidirectionalTechnical content needs (whitepapers, solution briefs); competitive positioningContent requests, competitive analysis, technical differentiation points
EngineeringSE -> EngEscalation for deep technical questions; product feedbackTechnical escalation tickets, product feedback summaries

Workflow Handoff Protocol:

  1. SE receives demo request from AE with completed discovery template (minimum: pain points, tech stack, decision criteria)
  2. SE delivers demo plan to AE for review at least 24 hours before scheduled demo
  3. SE documents technical win/loss for every completed evaluation within 5 business days
  4. SE escalates to SA when deal requires custom integration architecture or multi-system design

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in sales-success/sales-engineer of borghei/Claude-Skills.

  • SKILL.md
  • scripts/demo_planner.py
  • scripts/rfp_analyzer.py
  • scripts/technical_qualifier.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Sales Engineer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sales Engineer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sales Engineer this skillborghei/Claude-Skills881—~3.9kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Audit Onboarding Proposalhoangnb24/repository-harness1.2k—~4kAutomated safety check: PassMIT
No Negative EchoLB623/no-negative-echo897—~965Automated safety check: PassMIT
GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude11k—~3kAutomated safety check: NotesMIT
Architectural ProposalsFritzAndFriends/SharpSite1452 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed
  • Audit Onboarding Proposal

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $audit-onboarding-proposal.

    1.2k GitHub stars~4k tokensUpdated 4 days ago
    Sales & SupportAuto-check passed
  • No Negative Echo

    LB623/no-negative-echo

    Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.

    897 GitHub stars~965 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated yesterday
    Sales & SupportAuto-check: notes
  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Sales & SupportAuto-check passed
  • Task Profile

    techwolf-ai/ai-first-toolkit

    Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would…

    132 GitHub stars~3.6k tokensUpdated 9 days ago
    Sales & SupportAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Sales Engineer

What does Sales Engineer do?

Technical sales engineering: demos, solution design, RFP responses, and POC management. Sales Engineer is an agent skill from borghei/Claude-Skills. Technical sales engineering: demos, solution design, RFP responses, and POC management.

When should I use Sales Engineer?

Sales Engineer fits situations like: preparing demos; responding to RFPs/RFIs; scoping proof-of-concepts; building battle cards.

How do I install Sales Engineer in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill sales-engineer -a claude-code`. Or copy the skill folder (sales-success/sales-engineer in borghei/Claude-Skills) into .claude/skills/sales-engineer in your project. Claude Code loads it when a task matches its description.

How do I install Sales Engineer in Codex?

Run `npx skills add borghei/Claude-Skills --skill sales-engineer -a codex`. Or copy the skill folder (sales-success/sales-engineer in borghei/Claude-Skills) into .agents/skills/sales-engineer in your project. Codex loads it when a task matches its description.

Can I use Sales Engineer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill sales-engineer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-engineer, .gemini/skills/sales-engineer, .github/skills/sales-engineer and .opencode/skills/sales-engineer in your project.

What does Sales Engineer need to run?

Going by SKILL.md and its folder, Sales Engineer needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Sales Engineer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sales Engineer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sales Engineer use?

Sales Engineer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sales Engineer use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sales Engineer?

Skills that share tags, products or a category with Sales Engineer: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 897 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sales Engineer?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.