- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add borghei/Claude-Skills --skill sales-engineer -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add borghei/Claude-Skills --skill sales-engineer -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add borghei/Claude-Skills --skill sales-engineer -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add borghei/Claude-Skills --skill sales-engineer -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/borghei/Claude-Skills/tree/HEAD/business-growth/sales-engineerDari penerbit
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.
Role: Sales Engineer / Solutions Architect Domain: Pre-Sales Engineering, Solution Design, Technical Demos, Proof of Concepts Business Type: SaaS / Pre-Sales Engineering
Before producing the deliverable, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Objective: Understand customer requirements, technical environment, and business drivers.
Activities:
Tools: Use rfp_response_analyzer.py to score initial requirement alignment.
Output: Technical discovery document, requirement map, initial coverage assessment.
Objective: Design a solution architecture that addresses customer requirements.
Activities:
Tools: Use competitive_matrix_builder.py to identify differentiators and vulnerabilities.
Output: Solution architecture, competitive positioning, technical differentiation strategy.
Objective: Deliver compelling technical demonstrations tailored to stakeholder priorities.
Activities:
Templates: Use demo_script_template.md for structured demo preparation.
Output: Customized demo, stakeholder-specific talking points, feedback capture.
Objective: Execute a structured proof-of-concept that validates the solution.
Activities:
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.
Objective: Deliver a technical proposal that supports the commercial close.
Activities:
Templates: Use technical_proposal_template.md for the proposal document.
Output: Technical proposal, implementation timeline, risk mitigation plan.
Script: scripts/rfp_response_analyzer.py
Purpose: Parse RFP/RFI requirements, score coverage, identify gaps, and generate bid/no-bid recommendations.
Coverage Categories:
Priority Weighting:
Bid/No-Bid Logic:
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.
Script: scripts/competitive_matrix_builder.py
Purpose: Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.
Feature Scoring:
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:
Script: scripts/poc_planner.py
Purpose: Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards.
Default Phase Breakdown:
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:
../../marketing/../../product-team/../../c-level-advisor/../customer-success-manager/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
Bid/No-Bid Logic:
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
Scoring: Full (3), Partial (2), Limited (1), None (0)
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_planner.py poc_data.json --format json
Default Phase Breakdown: Week 1 Setup, Weeks 2-3 Core Testing, Week 4 Advanced Testing, Week 5 Evaluation
In scope: RFP/RFI response analysis and scoring, competitive feature matrix construction, proof-of-concept planning and evaluation, demo preparation frameworks, technical proposal structure, win/loss analysis methodology, and stakeholder engagement tracking across the 5-phase pre-sales workflow (Discovery, Solution Design, Demo, POC, Proposal).
Out of scope: Sales strategy and territory planning (account executive function), pricing and commercial terms negotiation (use pricing-strategy), post-sale implementation and customer success (use customer-success-manager), marketing content and competitive messaging (use marketing skills), and product roadmap decisions based on RFP gaps (use product-team). Tools analyze static data exports -- no integrations with CRM systems (Salesforce, HubSpot) or RFP platforms (Loopio, Arphie).
Limitations: Bid/no-bid thresholds are configurable but defaults assume B2B SaaS with 30%+ win-rate targets. Competitive matrix scoring is only as accurate as the input data -- validate scores with field experience against specific competitors. POC timelines assume standard 5-week engagement; highly regulated industries (healthcare, government) may require 2-3x longer. AI-assisted RFP tools (emerging in 2025-2026) can reduce response time 60-80% but are not integrated here.
Last Updated: March 2026 Status: Production-ready Tools: 3 Python automation scripts References: 3 knowledge base documents Templates: 5 asset files
>
---name: sales-engineerdescription: >---# business-growth/sales-engineer/SKILL.mdFAQ
Unduh business-growth/sales-engineer/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/borghei/Claude-Skills.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.