sales-engineer
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering
Install / Use
npx skills add borghei/Claude-Skills --skill sales-engineerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of sales-engineer
sales-engineer scores 92/100 on our quality scale, 908th of 2,769 Automation skills we index (top 33%).
Its SKILL.md is 17 KB long, well organised into 34 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so sales-engineer is actively maintained.
- Our last check on 2026-10-28 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
sales-engineer compared with similar skills
All 4 of these similar skills score higher than sales-engineer; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| sales-engineer (this skill)by borghei | 92 | 817 | 57d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install sales-engineer?
- Run
npx skills add borghei/Claude-Skills --skill sales-engineer. The install tabs above show the steps for each supported agent. - Which AI agents does sales-engineer work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is sales-engineer safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is sales-engineer still maintained?
- The repository was last updated about 2 months ago, so sales-engineer is actively maintained.
Skill content
View source on GitHubname: sales-engineer description: > Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth domain: sales-engineering updated: 2026-03-31 tags: [sales-engineering, demos, poc, technical-sales, solutions]
Sales Engineer Skill
A production-ready skill package for pre-sales engineering that bridges technical expertise and sales execution. Provides automated analysis for RFP/RFI responses, competitive positioning, and proof-of-concept planning.
Overview
Role: Sales Engineer / Solutions Architect Domain: Pre-Sales Engineering, Solution Design, Technical Demos, Proof of Concepts Business Type: SaaS / Pre-Sales Engineering
What This Skill Does
- RFP/RFI Response Analysis - Score requirement coverage, identify gaps, generate bid/no-bid recommendations
- Competitive Technical Positioning - Build feature comparison matrices, identify differentiators and vulnerabilities
- POC Planning - Generate timelines, resource plans, success criteria, and evaluation scorecards
- Demo Preparation - Structure demo scripts with talking points and objection handling
- Technical Proposal Creation - Framework for solution architecture and implementation planning
- Win/Loss Analysis - Data-driven competitive assessment for deal strategy
Key Metrics
| Metric | Description | Target | |--------|-------------|--------| | Win Rate | Deals won / total opportunities | >30% | | Sales Cycle Length | Average days from discovery to close | <90 days | | POC Conversion Rate | POCs resulting in closed deals | >60% | | Customer Engagement Score | Stakeholder participation in evaluation | >75% | | RFP Coverage Score | Requirements fully addressed | >80% |
Clarify First
Before producing the deliverable, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Which deliverable — RFP/RFI coverage analysis, competitive matrix, or POC plan (selects the tool and phase)
- [ ] Customer requirements + priorities — the must/should/nice-to-have list (drives weighted coverage and the bid/no-bid call)
- [ ] Competitor(s) in the deal — needed for the feature matrix, differentiators, and battlecard
- [ ] POC scope + success criteria — when planning a POC, the use cases and measurable go/no-go bar (prevents an unbounded POC)
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 deliverable.
5-Phase Workflow
Phase 1: Discovery & Research
Objective: Understand customer requirements, technical environment, and business drivers.
Activities:
- Conduct technical discovery calls with stakeholders
- Map customer's current architecture and pain points
- Identify integration requirements and constraints
- Document security and compliance requirements
- Assess competitive landscape for this opportunity
Tools: Use rfp_response_analyzer.py to score initial requirement alignment.
Output: Technical discovery document, requirement map, initial coverage assessment.
Phase 2: Solution Design
Objective: Design a solution architecture that addresses customer requirements.
Activities:
- Map product capabilities to customer requirements
- Design integration architecture
- Identify customization needs and development effort
- Build competitive differentiation strategy
- Create solution architecture diagrams
Tools: Use competitive_matrix_builder.py to identify differentiators and vulnerabilities.
Output: Solution architecture, competitive positioning, technical differentiation strategy.
Phase 3: Demo Preparation & Delivery
Objective: Deliver compelling technical demonstrations tailored to stakeholder priorities.
Activities:
- Build demo environment matching customer's use case
- Create demo script with talking points per stakeholder role
- Prepare objection handling responses
- Rehearse failure scenarios and recovery paths
- Collect feedback and adjust approach
Templates: Use demo_script_template.md for structured demo preparation.
Output: Customized demo, stakeholder-specific talking points, feedback capture.
Phase 4: POC & Evaluation
Objective: Execute a structured proof-of-concept that validates the solution.
Activities:
- Define POC scope, success criteria, and timeline
- Allocate resources and set up environment
- Execute phased testing (core, advanced, edge cases)
- Track progress against success criteria
- Generate evaluation scorecard
Tools: Use poc_planner.py to generate the complete POC plan.
Templates: Use poc_scorecard_template.md for evaluation tracking.
Output: POC plan, evaluation scorecard, go/no-go recommendation.
Phase 5: Proposal & Closing
Objective: Deliver a technical proposal that supports the commercial close.
Activities:
- Compile POC results and success metrics
- Create technical proposal with implementation plan
- Address outstanding objections with evidence
- Support pricing and packaging discussions
- Conduct win/loss analysis post-decision
Templates: Use technical_proposal_template.md for the proposal document.
Output: Technical proposal, implementation timeline, risk mitigation plan.
Python Automation Tools
1. RFP Response Analyzer
Script: scripts/rfp_response_analyzer.py
Purpose: Parse RFP/RFI requirements, score coverage, identify gaps, and generate bid/no-bid recommendations.
Coverage Categories:
- Full (100%) - Requirement fully met by current product
- Partial (50%) - Requirement partially met, workaround or configuration needed
- Planned (25%) - On product roadmap, not yet available
- Gap (0%) - Not supported, no current plan
Priority Weighting:
- Must-Have: 3x weight
- Should-Have: 2x weight
- Nice-to-Have: 1x weight
Bid/No-Bid Logic:
- Bid: Coverage score >70% AND must-have gaps <=3
- Conditional Bid: Coverage score 50-70% OR must-have gaps 2-3
- No-Bid: Coverage score <50% OR must-have gaps >3
Usage:
# Human-readable output
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json
# JSON output
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json
# Help
python scripts/rfp_response_analyzer.py --help
Input Format: See assets/sample_rfp_data.json for the complete schema.
2. Competitive Matrix Builder
Script: scripts/competitive_matrix_builder.py
Purpose: Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.
Feature Scoring:
- Full (3) - Complete feature support
- Partial (2) - Partial or limited feature support
- Limited (1) - Minimal or basic feature support
- None (0) - Feature not available
Usage:
# Human-readable output
python scripts/competitive_matrix_builder.py competitive_data.json
# JSON output
python scripts/competitive_matrix_builder.py competitive_data.json --format json
Output Includes:
- Feature comparison matrix with scores
- Weighted competitive scores per product
- Differentiators (features where our product leads)
- Vulnerabilities (features where competitors lead)
- Win themes based on differentiators
3. POC Planner
Script: scripts/poc_planner.py
Purpose: Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards.
Default Phase Breakdown:
- Week 1: Setup - Environment provisioning, data migration, configuration
- Weeks 2-3: Core Testing - Primary use cases, integration testing
- Week 4: Advanced Testing - Edge cases, performance, security
- Week 5: Evaluation - Scorecard completion, stakeholder review, go/no-go
Usage:
# Human-readable output
python scripts/poc_planner.py poc_data.json
# JSON output
python scripts/poc_planner.py poc_data.json --format json
Output Includes:
- POC plan with phased timeline
- Resource allocation (SE, engineering, customer)
- Success criteria with measurable metrics
- Evaluation scorecard (functionality, performance, integration, usability, support)
- Risk register with mitigation strategies
- Go/No-Go recommendation framework
Reference Knowledge Bases
| Reference | Description |
|-----------|-------------|
| references/rfp-response-guide.md | RFP/RFI response best practices, compliance matrix, bid/no-bid framework |
| references/competitive-positioning-framework.md | Competitive analysis methodology, battlecard creation, objection handling |
| references/poc-best-practices.md | POC planning methodology, success criteria, evaluation frameworks |
Asset Templates
| Template | Purpose |
|----------|---------|
| assets/technical_proposal_template.md | Technical proposal with executive summary, solution architecture, implementation plan |
| assets/demo_script_template.md | Demo script with agenda, talking points, objection handling |
| assets/poc_scorecard_template.md | POC evaluation scorecard with weighted scoring |
| assets/sample_rfp_data.json | Sample RFP data for testing the analyzer |
| assets/expected_output.json | Expected output from rfp_response_analyzer.py |
Communication Style
- Technical yet accessible - Translate complex concepts for business stakeholders
- Confident and consultative - Position as trusted advisor, not vendor
- Evidence-based - Back every claim with data, demos, or case studies
- Stakeholder-aware - Tailor depth and focus to audience (CTO vs. end user vs. procurement)
Integration Points
- Marketing Skills - Leverage competitive intelligence and messaging frameworks from
../../marketing/ - Product Team - Coordinate on roadmap items flagged as "Planned" in RFP analysis from
../../product-team/ - C-Level Advisory - Escalate strategic deals requiring executive engagement from
../../c-level-advisor/ - Customer Success - Hand off POC results and success criteria to CSM from
../customer-success-manager/
Tool Reference
1. rfp_response_analyzer.py
Parses RFP/RFI requirements and scores coverage using Full/Partial/Planned/Gap categories. Generates weighted coverage scores, gap analysis, effort estimation, and bid/no-bid recommendations.
python scripts/rfp_response_analyzer.py rfp_data.json
python scripts/rfp_response_analyzer.py rfp_data.json --format json
| Flag | Type | Description |
|------|------|-------------|
| rfp_data.json | positional | Path to JSON file with RFP requirements and coverage data |
| --format | optional | Output format: text (default) or json |
Bid/No-Bid Logic:
- Bid: Coverage score >70% AND must-have gaps <=3
- Conditional Bid: Coverage score 50-70% OR must-have gaps 2-3
- No-Bid: Coverage score <50% OR must-have gaps >3
2. competitive_matrix_builder.py
Generates feature comparison matrices, calculates weighted competitive scores, identifies differentiators and vulnerabilities, and produces win themes.
python scripts/competitive_matrix_builder.py competitive_data.json
python scripts/competitive_matrix_builder.py competitive_data.json --format json
| Flag | Type | Description |
|------|------|-------------|
| competitive_data.json | positional | Path to JSON file with feature comparison data |
| --format | optional | Output format: text (default) or json |
Scoring: Full (3), Partial (2), Limited (1), None (0)
3. poc_planner.py
Generates structured POC plans with phased timelines, resource allocation, success criteria, evaluation scorecards, risk registers, and go/no-go frameworks.
python scripts/poc_planner.py poc_data.json
python scripts/poc_pl
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
