Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Technical sales engineering: demos, solution design, RFP responses, and POC management.
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills sales-engineer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .claude/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills sales-engineer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales-success/sales-engineer .agents/skills/sales-engineer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .agents/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills sales-engineer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales-success/sales-engineer .cursor/skills/sales-engineer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .cursor/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path sales-success/sales-engineer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills sales-engineer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales-success/sales-engineer .gemini/skills/sales-engineer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .gemini/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills sales-engineerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales-success/sales-engineer .github/skills/sales-engineer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .github/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill sales-engineer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills sales-engineer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales-success/sales-engineer .opencode/skills/sales-engineer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sales-engineer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/sales-engineer into .opencode/skills/sales-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-engineer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sales-engineerTechnical 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. 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.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,357 words, ~3,942 tokens.
.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.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.
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
# 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 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"]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 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] || Category | Meaning |
|---|---|
| Full | Fully meets this requirement today |
| Partial | Partially meets, with explanation of gap |
| Roadmap | Planned for [specific timeframe] |
| Partner | Addressed via [named partner integration] |
| N/A | Not applicable to the solution |
| ID | Requirement | Response | Detail |
|---|---|---|---|
| R1 | SSO via SAML 2.0 | Full | Native SAML 2.0 support with all major IdPs |
| R2 | On-premise deployment | Partial | Available as private cloud; bare-metal on roadmap Q3 |
| R3 | Real-time analytics | Full | Sub-second dashboards with custom metrics |
| R4 | HIPAA compliance | Roadmap | BAA available Q2 2026 |
The agent applies LAER for every technical objection:
| Objection | Response 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 |
# 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].# 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| Problem | Root Cause | Resolution |
|---|---|---|
| Demo falls flat; audience disengaged | Feature dump instead of pain-based storytelling; wrong use cases selected | Always 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 competitor | Generic answers; missing compliance matrix; late submission | Build 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 convert | Success criteria were vague; scope creep expanded beyond manageable bounds | Define 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 recurring | Incomplete competitive preparation; SE not involved early enough in cycle | Update 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 demo | Insufficient environment preparation; stale test data | Always 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 complete | AE under pressure to accelerate deal; incomplete understanding of prospect needs | Push 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 buyer | Qualify 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. |
| Metric | Target | Measurement Method |
|---|---|---|
| Demo-to-advance rate | 70%+ | Deals advancing to next stage after demo / Total demos delivered |
| POC conversion rate | 60%+ | POCs resulting in proposal or closed-won / Total POCs |
| RFP win rate | 45%+ | RFPs won / RFPs submitted (qualified only) |
| Technical win rate | 80%+ | Deals where technical evaluation was won / Total technical evaluations |
| Demo NPS / feedback score | 4.0+ out of 5 | Post-demo survey from attendees |
| Time-to-demo | Under 5 business days from request | Days from demo request to demo delivery |
| RFP response time | 100% on-time submission | Submissions before deadline / Total RFPs |
| Battle card currency | Updated within last 90 days | Percentage of battle cards reviewed in current quarter |
In Scope:
Out of Scope:
Limitations:
| Integration | Direction | Purpose | Handoff Artifact |
|---|---|---|---|
| Account Executive | AE -> SE | Demo requests, discovery context, deal strategy alignment | Discovery notes, stakeholder map, competitive landscape, demo requirements |
| Solutions Architect | SE -> SA | Complex enterprise deals requiring deep architecture design | Technical discovery output, integration requirements, security assessment needs |
| Product Team | SE -> Product | Feature gaps surfaced during evaluations, competitive intel | Feature request log, RFP gap analysis, competitive capability comparison |
| Customer Success Manager | SE -> CSM | Technical context for post-sale onboarding | POC results, technical configuration, integration specs, known limitations |
| Sales Operations | SE -> Ops | Technical win/loss data, demo activity metrics | Technical win/loss reports, demo conversion data |
| Marketing | Bidirectional | Technical content needs (whitepapers, solution briefs); competitive positioning | Content requests, competitive analysis, technical differentiation points |
| Engineering | SE -> Eng | Escalation for deep technical questions; product feedback | Technical escalation tickets, product feedback summaries |
Workflow Handoff Protocol:
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in sales-success/sales-engineer of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sales Engineer this skillborghei/Claude-Skills | 881 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 40 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Onboarding Proposalhoangnb24/repository-harness | 1.2k | — | ~4k | Automated safety check: Pass | MIT | |
| No Negative EchoLB623/no-negative-echo | 897 | — | ~965 | Automated safety check: Pass | MIT | |
| GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude | 11k | — | ~3k | Automated safety check: Notes | MIT | |
| Architectural ProposalsFritzAndFriends/SharpSite | 145 | 2 repos | ~1.6k | Automated safety check: Pass | MIT |
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
hoangnb24/repository-harness
Use only when the user explicitly invokes $audit-onboarding-proposal.
LB623/no-negative-echo
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.
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.
FritzAndFriends/SharpSite
How to write comprehensive architectural proposals that drive alignment before code is written
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…
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
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.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
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.
Sales Engineer fits situations like: preparing demos; responding to RFPs/RFIs; scoping proof-of-concepts; building battle cards.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.