sales-engineer
Audited by Runlayer on Feb 23, 2026
Malicious tool definition detected
Tool: SKILL.md [1/2] Description: --- name: sales-engineer description: Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering --- # 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
Tool: SKILL.md [2/2] Description: | 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 studie
Malicious tool definition detected
Tool: assets/demo_script_template.md [1/2] Description: # Demo Script Template ## Demo Information | Field | Value | |-------|-------| | Customer | [Customer Name] | | Date/Time | [Date and Time] | | Duration | [XX minutes] | | Demo Environment | [Environment URL/Details] | | Presenter | [Sales Engineer Name] | | AE/Account Executive | [AE Name] | --- ## Pre-Demo Checklist - [ ] Demo environment tested and confirmed working - [ ] Sample data loaded and validated - [ ] Backup demo environment pre
Tool: assets/demo_script_template.md [2/2] Description: to [Y] without re-architecture." | ### Recovery Strategies **If the demo breaks:** 1.
Malicious tool definition detected
Tool: assets/expected_output.json [1/2]
Tool: assets/expected_output.json [2/2]
Malicious tool definition detected
Tool: assets/poc_scorecard_template.md Description: # POC Evaluation Scorecard ## Scorecard Information | Field | Value | |-------|-------| | POC Name | [POC Name] | | Customer | [Customer Name] | | Vendor/Product | [Product Name] | | Evaluation Period | [Start Date] - [End Date] | | Evaluated By | [Names and Roles] | | Date Completed | [Date] | --- ## Scoring Scale | Score | Label | Definition | |-------|-------|------------| | 5 | Exceeds | Superior capability; exceeds requirements with notabl
Malicious tool definition detected
Tool: assets/sample_rfp_data.json Description: { "rfp_name": "Enterprise Data Analytics Platform RFP", "customer": "Acme Financial Services", "due_date": "2026-03-15", "deal_value": "$450,000 ARR", "strategic_value": "high", "requirements": [ { "id": "R-001", "requirement": "Real-time data ingestion from multiple sources (APIs, databases, streaming)", "category": "Data Integration", "priority": "must-have", "coverage_status": "full", "effort_hours": 8, "notes": "Native connectors for 200+ data s
Malicious tool definition detected
Tool: assets/technical_proposal_template.md [1/2] Description: # Technical Proposal Template ## Document Information | Field | Value | |-------|-------| | Customer | [Customer Name] | | Opportunity | [Opportunity Name / RFP Reference] | | Prepared By | [Sales Engineer Name] | | Date | [Date] | | Version | [Version Number] | | Classification | [Confidential / Internal] | --- ## 1.
Tool: assets/technical_proposal_template.md [2/2]
Malicious tool definition detected
Tool: references/competitive-positioning-framework.md [1/2] Description: # Competitive Positioning Framework A comprehensive guide for Sales Engineers to analyze competitors, build battlecards, handle objections, and position for wins. ## Competitive Analysis Methodology ### 1. Intelligence Gathering **Primary Sources:** - Competitor product documentation and release notes - Analyst reports (Gartner, Forrester, IDC) - Customer feedback from win/loss reviews - Industry conferences and webinars -
Tool: references/competitive-positioning-framework.md [2/2] Description: **By Industry:** Vertical-specific win factors 4.
Malicious tool definition detected
Tool: references/poc-best-practices.md [1/2] Description: # Proof of Concept (POC) Best Practices A comprehensive guide for Sales Engineers planning, executing, and evaluating proof-of-concept engagements.
Tool: references/poc-best-practices.md [2/2] Description: | 20% | | | | Usability | 15% | | | | Support | 15% | | | | **Total** | **100%** | | | **Scoring Scale:** - 5: Exceeds requirements - superior capability demonstrated - 4: Meets requirements - full capability with minor enhancements possible - 3: Partially meets - acceptable but notable gaps remain - 2: Below expectations - significant gaps that impact value - 1: Does not meet - critical failure for this category **Decision Thresholds:**
Malicious tool definition detected
Tool: references/rfp-response-guide.md [1/2] Description: # RFP/RFI Response Guide A comprehensive reference for Sales Engineers responding to Requests for Proposal (RFP) and Requests for Information (RFI). ## RFP Response Best Practices ### 1. Pre-Response Assessment Before investing time in a response, conduct a thorough bid/no-bid assessment: **Bid Criteria Checklist:** - Do we have a pre-existing relationship with the customer?
Tool: references/rfp-response-guide.md [2/2] Description: Day 15-17 | Internal review, quality check | | Day 18-19 | Final edits, formatting, executive review | | Day 20 | Submission | ### Time-Saving Strategies 1.
Malicious tool definition detected
Tool: scripts/competitive_matrix_builder.py [1/2] Description: #!/usr/bin/env python3 """Competitive Matrix Builder - Generate feature comparison matrices and positioning analysis.
Tool: scripts/competitive_matrix_builder.py [2/2] Description: """Run the complete competitive analysis pipeline.
Malicious tool definition detected
Tool: scripts/poc_planner.py [1/3] Description: #!/usr/bin/env python3 """POC Planner - Plan proof-of-concept engagements with timeline, resources, and scorecards. Generates structured POC plans including phased timelines, resource allocation, success criteria with measurable metrics, evaluation scorecards, risk identification, and go/no-go recommendation frameworks. Usage: python poc_planner.py poc_data.json python poc_planner.py poc_data.json --format json python poc_planner.py poc_data.json -
""" risks = [] complexity = data.get("complexity", "medium").lower() num_integrations = data.get("num_integrations", 0) total_weeks = resources["total_duration_weeks"] stakeholders = data.get("stakeholders", []) # Timeline risk if total_weeks > 6: risks.append({ "risk": "Extended timeline may lose stakeholder attention", "probability": "high", "impact": "high", "mitigation": "Schedule weekly progress checkpoints; deliver early wins in week 2", "category": "Timeline", }) elif total_weeks >= 4: ri
Tool passed security scan