sales-engineer
by alirezarezvanisales-engineer helps Sales Engineering teams analyze RFP/RFI coverage, build competitive feature matrices, draft technical proposals, and plan POCs using repository templates, references, and Python scripts.
This skill scores 78/100, making it a solid listing candidate for directory users who want structured pre-sales engineering support. The repository provides a clear trigger description, a substantial workflow, reusable templates, reference guides, and scripts for RFP analysis, competitive matrices, and POC planning. Users should still expect to adapt the sample inputs and templates to their own product, competitors, and sales process.
- Strong triggerability: the frontmatter clearly names RFP/RFI responses, proposal requests, competitor comparisons, feature matrices, POC planning, demo prep, and pre-sales engineering as use cases.
- Useful operational assets: includes templates for demo scripts, POC scorecards, technical proposals, sample RFP data, and an expected JSON output example.
- Agent leverage beyond prompting: bundled scripts for RFP response analysis, competitive matrix building, and POC planning give the agent concrete workflows to execute.
- No install command is provided in SKILL.md, so users may need to infer setup from the repository structure.
- The included sample data and templates are generic, so teams must customize product capabilities, competitive information, and customer-specific requirements before relying on outputs.
Overview of sales-engineer skill
What the sales-engineer skill is for
The sales-engineer skill is a pre-sales workflow for analyzing RFP/RFI coverage, building competitive feature comparisons, preparing technical proposals, and planning proof-of-concept engagements. It is best suited for Sales Engineering teams, solution consultants, founders handling enterprise sales, and AI agents supporting bid response or demo preparation.
Best-fit use cases for Sales Engineering
Use this skill when you need structured help with:
- RFP or RFI requirement scoring
- Coverage gap analysis before submitting a proposal
- Competitive positioning and feature matrix creation
- POC qualification, scope definition, and scorecard design
- Customer-specific demo script preparation
- Technical proposal drafting with gap mitigation plans
The strongest fit is complex B2B sales where technical requirements, integrations, security, and proof points affect the buying decision.
What makes this skill more useful than a prompt
A generic prompt can summarize an RFP, but the sales-engineer skill adds a repeatable sales engineering operating model. The repository includes templates for demo scripts, POC scorecards, technical proposals, and sample RFP data, plus scripts for RFP analysis, competitive matrix building, and POC planning. That makes it more actionable for teams that need consistent outputs across opportunities.
Important adoption considerations
This skill is not a substitute for product knowledge, legal review, pricing approval, or executive deal strategy. It works best when you provide real requirement lists, honest coverage status, customer priorities, competitor context, and known constraints. If the inputs are vague, the skill may produce polished but low-confidence sales material.
How to Use sales-engineer skill
sales-engineer install and repository path
Install the skill from the GitHub repository with:
npx skills add alirezarezvani/claude-skills --skill sales-engineer
The source path is:
business-growth/skills/sales-engineer
After install, read SKILL.md first to understand the five-phase workflow. Then inspect the supporting files that affect output quality:
assets/sample_rfp_data.jsonassets/expected_output.jsonassets/demo_script_template.mdassets/poc_scorecard_template.mdassets/technical_proposal_template.mdreferences/rfp-response-guide.mdreferences/competitive-positioning-framework.mdreferences/poc-best-practices.mdscripts/rfp_response_analyzer.pyscripts/competitive_matrix_builder.pyscripts/poc_planner.py
Inputs the sales-engineer skill needs
For RFP analysis, provide requirements in a structured format with requirement ID, category, priority, coverage status, estimated effort, notes, and mitigation. The sample JSON shows the expected shape and is the best starting point.
For competitive work, provide your product capabilities, competitor names, buyer priorities, market segment, and evidence level for each claim. Avoid asking for a “feature matrix” without defining the customer’s evaluation criteria.
For POC planning, provide deal value, decision timeline, champion status, budget confidence, required integrations, success criteria, available SE resources, and whether the POC is competitive or sole-vendor.
Turning a rough goal into a strong prompt
Weak prompt:
“Help me respond to this RFP.”
Stronger prompt:
“Use the sales-engineer skill to analyze this RFP for an enterprise analytics platform. Score each requirement as full, partial, planned, or gap. Separate must-have gaps from should-have gaps, estimate effort hours, propose mitigation for each gap, and recommend whether we should proceed to proposal. Customer priorities are security, API integrations, and time to value. Output a coverage summary, risk table, and proposal-ready gap mitigation section.”
This works better because it tells the skill what decision you need, how to classify requirements, and which buyer priorities should influence the recommendation.
Practical sales-engineer usage workflow
Start with discovery: map customer pain points, technical environment, integrations, security needs, and decision criteria. Then run or adapt the RFP analyzer against your structured requirement data. Use the output to decide whether the opportunity is qualified enough to continue.
Next, build the solution design and competitive positioning. Use the reference framework to weight feature categories by customer importance instead of creating a flat checklist. Then prepare the demo or POC using the templates, making sure each demo scene or POC task ties back to a documented requirement.
For implementation, run scripts locally only after reviewing the expected input format. For example, the repository demonstrates the RFP analyzer pattern:
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json
Use the sample assets as models, not as customer-ready content.
sales-engineer skill FAQ
Is sales-engineer good for beginners?
Yes, if the user understands the deal context. The templates provide helpful structure for newer Sales Engineers, especially around POC scorecards and demo preparation. However, beginners still need product, market, and customer knowledge; the skill will not invent reliable technical claims.
When should I not use this skill?
Do not use sales-engineer for purely marketing copy, generic outbound emails, legal contract review, or pricing strategy. It is also a poor fit for small transactional deals where a detailed POC, RFP analysis, or competitive matrix would waste time.
How is it different from ordinary ChatGPT or Claude prompts?
Ordinary prompts depend heavily on the user remembering every step. The sales-engineer skill provides a dedicated workflow, decision checkpoints, templates, references, and scripts. That makes it better for repeatable Sales Engineering work where consistency, scoring logic, and proposal artifacts matter.
Does it fit existing CRM or sales tooling?
The repository does not appear to provide native CRM integration. Treat it as a workflow and artifact-generation layer. You can copy outputs into Salesforce, HubSpot, Notion, Google Docs, proposal tools, or internal deal rooms after review.
How to Improve sales-engineer skill
Improve sales-engineer outputs with better evidence
The highest-impact improvement is better source data. Include real RFP text, stakeholder notes, architecture constraints, security requirements, competitor mentions, deal stage, and win themes. For each claim, distinguish confirmed facts from assumptions. This reduces the risk of confident but unsupported proposal language.
Common failure modes to watch for
Watch for inflated coverage scores, vague mitigation plans, unweighted competitor comparisons, and POCs that test too many scenarios. The references emphasize scope control: a strong POC should validate a few buyer-critical use cases, not every feature in the platform.
Also review any generated technical proposal for commitments your product, support, legal, or delivery teams cannot honor.
Iteration pattern after the first output
After the first output, ask the skill to critique the result from three angles:
- Buyer risk: what would the customer still doubt?
- Delivery risk: what would be hard to implement or support?
- Competitive risk: where could a rival credibly attack the proposal?
Then revise the RFP response, demo plan, or POC scorecard using only the changes that improve deal clarity or reduce execution risk.
Customizing the skill for your sales motion
To make the sales-engineer skill more valuable, adapt the templates to your company’s qualification rules, common integrations, security language, approved differentiators, and standard POC limits. Add your own product-specific scoring guidance and disallowed claims so agents produce outputs that are not only persuasive but also accurate and reviewable.