[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7199DASQA25Z41GT2BCPH38":3,"skill-same:01M7199DASQA25Z41GT2BCPH38":120},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M7199DASQA25Z41GT2BCPH38","sales-engineer",null,"Analyzes RFP\u002FRFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win\u002Floss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.","dahaliztupe-sketch\u002FKalmeron-Two","dahaliztupe-sketch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271085317?v=4","01M719765Q83P08JCQ1SWNQR0N","01M719766HQBGF44W90MPJKTD2",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"sales engineer","sales","engineer","concept","competitive","competitors","poc","matrix","features","customer","product","scoring","tasks","analysis","bids","when","proof-of-concept","rfi","proposal","coverage","2026-11-10 10:12:30",false,"---\nname: \"sales-engineer\"\ndescription: Analyzes RFP\u002FRFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win\u002Floss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.\n---\n\n# Sales Engineer Skill\n\n## 5-Phase Workflow\n\n### Phase 1: Discovery & Research\n\n**Objective:** Understand customer requirements, technical environment, and business drivers.\n\n**Checklist:**\n- [ ] Conduct technical discovery calls with stakeholders\n- [ ] Map customer's current architecture and pain points\n- [ ] Identify integration requirements and constraints\n- [ ] Document security and compliance requirements\n- [ ] Assess competitive landscape for this opportunity\n\n**Tools:** Run `rfp_response_analyzer.py` to score initial requirement alignment.\n\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json > phase1_rfp_results.json\n```\n\n**Output:** Technical discovery document, requirement map, initial coverage assessment.\n\n**Validation checkpoint:** Coverage score must be >50% and must-have gaps ≤3 before proceeding to Phase 2. Check with:\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json | python -c \"import sys,json; r=json.load(sys.stdin); print('PROCEED' if r['coverage_score']>50 and r['must_have_gaps']\u003C=3 else 'REVIEW')\"\n```\n\n---\n\n### Phase 2: Solution Design\n\n**Objective:** Design a solution architecture that addresses customer requirements.\n\n**Checklist:**\n- [ ] Map product capabilities to customer requirements\n- [ ] Design integration architecture\n- [ ] Identify customization needs and development effort\n- [ ] Build competitive differentiation strategy\n- [ ] Create solution architecture diagrams\n\n**Tools:** Run `competitive_matrix_builder.py` using Phase 1 data to identify differentiators and vulnerabilities.\n\n```bash\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json --format json > phase2_competitive.json\n\npython -c \"import json; d=json.load(open('phase2_competitive.json')); print('Differentiators:', d['differentiators']); print('Vulnerabilities:', d['vulnerabilities'])\"\n```\n\n**Output:** Solution architecture, competitive positioning, technical differentiation strategy.\n\n**Validation checkpoint:** Confirm at least one strong differentiator exists per customer priority before proceeding to Phase 3. If no differentiators found, escalate to Product Team (see Integration Points).\n\n---\n\n### Phase 3: Demo Preparation & Delivery\n\n**Objective:** Deliver compelling technical demonstrations tailored to stakeholder priorities.\n\n**Checklist:**\n- [ ] Build demo environment matching customer's use case\n- [ ] Create demo script with talking points per stakeholder role\n- [ ] Prepare objection handling responses\n- [ ] Rehearse failure scenarios and recovery paths\n- [ ] Collect feedback and adjust approach\n\n**Templates:** Use `assets\u002Fdemo_script_template.md` for structured demo preparation.\n\n**Output:** Customized demo, stakeholder-specific talking points, feedback capture.\n\n**Validation checkpoint:** Demo script must cover every must-have requirement flagged in `phase1_rfp_results.json` before delivery. Cross-reference with:\n```bash\npython -c \"import json; rfp=json.load(open('phase1_rfp_results.json')); [print('UNCOVERED:', r) for r in rfp['must_have_requirements'] if r['coverage']=='Gap']\"\n```\n\n---\n\n### Phase 4: POC & Evaluation\n\n**Objective:** Execute a structured proof-of-concept that validates the solution.\n\n**Checklist:**\n- [ ] Define POC scope, success criteria, and timeline\n- [ ] Allocate resources and set up environment\n- [ ] Execute phased testing (core, advanced, edge cases)\n- [ ] Track progress against success criteria\n- [ ] Generate evaluation scorecard\n\n**Tools:** Run `poc_planner.py` to generate the complete POC plan.\n\n```bash\npython scripts\u002Fpoc_planner.py poc_data.json --format json > phase4_poc_plan.json\n\npython -c \"import json; p=json.load(open('phase4_poc_plan.json')); print('Go\u002FNo-Go:', p['recommendation'])\"\n```\n\n**Templates:** Use `assets\u002Fpoc_scorecard_template.md` for evaluation tracking.\n\n**Output:** POC plan, evaluation scorecard, go\u002Fno-go recommendation.\n\n**Validation checkpoint:** POC conversion requires scorecard score >60% across all evaluation dimensions (functionality, performance, integration, usability, support). If score \u003C60%, document gaps and loop back to Phase 2 for solution redesign.\n\n---\n\n### Phase 5: Proposal & Closing\n\n**Objective:** Deliver a technical proposal that supports the commercial close.\n\n**Checklist:**\n- [ ] Compile POC results and success metrics\n- [ ] Create technical proposal with implementation plan\n- [ ] Address outstanding objections with evidence\n- [ ] Support pricing and packaging discussions\n- [ ] Conduct win\u002Floss analysis post-decision\n\n**Templates:** Use `assets\u002Ftechnical_proposal_template.md` for the proposal document.\n\n**Output:** Technical proposal, implementation timeline, risk mitigation plan.\n\n---\n\n## Python Automation Tools\n\n### 1. RFP Response Analyzer\n\n**Script:** `scripts\u002Frfp_response_analyzer.py`\n\n**Purpose:** Parse RFP\u002FRFI requirements, score coverage, identify gaps, and generate bid\u002Fno-bid recommendations.\n\n**Coverage Categories:** Full (100%), Partial (50%), Planned (25%), Gap (0%).  \n**Priority Weighting:** Must-Have 3×, Should-Have 2×, Nice-to-Have 1×.\n\n**Bid\u002FNo-Bid Logic:**\n- **Bid:** Coverage >70% AND must-have gaps ≤3\n- **Conditional Bid:** Coverage 50–70% OR must-have gaps 2–3\n- **No-Bid:** Coverage \u003C50% OR must-have gaps >3\n\n**Usage:**\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json            # human-readable\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json  # JSON output\npython scripts\u002Frfp_response_analyzer.py --help\n```\n\n**Input Format:** See `assets\u002Fsample_rfp_data.json` for the complete schema.\n\n---\n\n### 2. Competitive Matrix Builder\n\n**Script:** `scripts\u002Fcompetitive_matrix_builder.py`\n\n**Purpose:** Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.\n\n**Feature Scoring:** Full (3), Partial (2), Limited (1), None (0).\n\n**Usage:**\n```bash\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json              # human-readable\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json --format json  # JSON output\n```\n\n**Output Includes:** Feature comparison matrix, weighted competitive scores, differentiators, vulnerabilities, and win themes.\n\n---\n\n### 3. POC Planner\n\n**Script:** `scripts\u002Fpoc_planner.py`\n\n**Purpose:** Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards.\n\n**Default Phase Breakdown:**\n- **Week 1:** Setup — environment provisioning, data migration, configuration\n- **Weeks 2–3:** Core Testing — primary use cases, integration testing\n- **Week 4:** Advanced Testing — edge cases, performance, security\n- **Week 5:** Evaluation — scorecard completion, stakeholder review, go\u002Fno-go\n\n**Usage:**\n```bash\npython scripts\u002Fpoc_planner.py poc_data.json              # human-readable\npython scripts\u002Fpoc_planner.py poc_data.json --format json  # JSON output\n```\n\n**Output Includes:** Phased POC plan, resource allocation, success criteria, evaluation scorecard, risk register, and go\u002Fno-go recommendation framework.\n\n---\n\n## Reference Knowledge Bases\n\n| Reference | Description |\n|-----------|-------------|\n| `references\u002Frfp-response-guide.md` | RFP\u002FRFI response best practices, compliance matrix, bid\u002Fno-bid framework |\n| `references\u002Fcompetitive-positioning-framework.md` | Competitive analysis methodology, battlecard creation, objection handling |\n| `references\u002Fpoc-best-practices.md` | POC planning methodology, success criteria, evaluation frameworks |\n\n## Asset Templates\n\n| Template | Purpose |\n|----------|---------|\n| `assets\u002Ftechnical_proposal_template.md` | Technical proposal with executive summary, solution architecture, implementation plan |\n| `assets\u002Fdemo_script_template.md` | Demo script with agenda, talking points, objection handling |\n| `assets\u002Fpoc_scorecard_template.md` | POC evaluation scorecard with weighted scoring |\n| `assets\u002Fsample_rfp_data.json` | Sample RFP data for testing the analyzer |\n| `assets\u002Fexpected_output.json` | Expected output from rfp_response_analyzer.py |\n\n## Integration Points\n\n- **Marketing Skills** - Leverage competitive intelligence and messaging frameworks from `..\u002F..\u002Fmarketing-skill\u002F`\n- **Product Team** - Coordinate on roadmap items flagged as \"Planned\" in RFP analysis from `..\u002F..\u002Fproduct-team\u002F`\n- **C-Level Advisory** - Escalate strategic deals requiring executive engagement from `..\u002F..\u002Fc-level-advisor\u002F`\n- **Customer Success** - Hand off POC results and success criteria to CSM from `..\u002Fcustomer-success-manager\u002F`\n\n---\n\n**Last Updated:** February 2026\n**Status:** Production-ready\n**Tools:** 3 Python automation scripts\n**References:** 3 knowledge base documents\n**Templates:** 5 asset files\n","# Sales Engineer Skill\n\n## 5-Phase Workflow\n\n### Phase 1: Discovery & Research\n\n**Objective:** Understand customer requirements, technical environment, and business drivers.\n\n**Checklist:**\n- [ ] Conduct technical discovery calls with stakeholders\n- [ ] Map customer's current architecture and pain points\n- [ ] Identify integration requirements and constraints\n- [ ] Document security and compliance requirements\n- [ ] Assess competitive landscape for this opportunity\n\n**Tools:** Run `rfp_response_analyzer.py` to score initial requirement alignment.\n\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json > phase1_rfp_results.json\n```\n\n**Output:** Technical discovery document, requirement map, initial coverage assessment.\n\n**Validation checkpoint:** Coverage score must be >50% and must-have gaps ≤3 before proceeding to Phase 2. Check with:\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json | python -c \"import sys,json; r=json.load(sys.stdin); print('PROCEED' if r['coverage_score']>50 and r['must_have_gaps']\u003C=3 else 'REVIEW')\"\n```\n\n---\n\n### Phase 2: Solution Design\n\n**Objective:** Design a solution architecture that addresses customer requirements.\n\n**Checklist:**\n- [ ] Map product capabilities to customer requirements\n- [ ] Design integration architecture\n- [ ] Identify customization needs and development effort\n- [ ] Build competitive differentiation strategy\n- [ ] Create solution architecture diagrams\n\n**Tools:** Run `competitive_matrix_builder.py` using Phase 1 data to identify differentiators and vulnerabilities.\n\n```bash\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json --format json > phase2_competitive.json\n\npython -c \"import json; d=json.load(open('phase2_competitive.json')); print('Differentiators:', d['differentiators']); print('Vulnerabilities:', d['vulnerabilities'])\"\n```\n\n**Output:** Solution architecture, competitive positioning, technical differentiation strategy.\n\n**Validation checkpoint:** Confirm at least one strong differentiator exists per customer priority before proceeding to Phase 3. If no differentiators found, escalate to Product Team (see Integration Points).\n\n---\n\n### Phase 3: Demo Preparation & Delivery\n\n**Objective:** Deliver compelling technical demonstrations tailored to stakeholder priorities.\n\n**Checklist:**\n- [ ] Build demo environment matching customer's use case\n- [ ] Create demo script with talking points per stakeholder role\n- [ ] Prepare objection handling responses\n- [ ] Rehearse failure scenarios and recovery paths\n- [ ] Collect feedback and adjust approach\n\n**Templates:** Use `assets\u002Fdemo_script_template.md` for structured demo preparation.\n\n**Output:** Customized demo, stakeholder-specific talking points, feedback capture.\n\n**Validation checkpoint:** Demo script must cover every must-have requirement flagged in `phase1_rfp_results.json` before delivery. Cross-reference with:\n```bash\npython -c \"import json; rfp=json.load(open('phase1_rfp_results.json')); [print('UNCOVERED:', r) for r in rfp['must_have_requirements'] if r['coverage']=='Gap']\"\n```\n\n---\n\n### Phase 4: POC & Evaluation\n\n**Objective:** Execute a structured proof-of-concept that validates the solution.\n\n**Checklist:**\n- [ ] Define POC scope, success criteria, and timeline\n- [ ] Allocate resources and set up environment\n- [ ] Execute phased testing (core, advanced, edge cases)\n- [ ] Track progress against success criteria\n- [ ] Generate evaluation scorecard\n\n**Tools:** Run `poc_planner.py` to generate the complete POC plan.\n\n```bash\npython scripts\u002Fpoc_planner.py poc_data.json --format json > phase4_poc_plan.json\n\npython -c \"import json; p=json.load(open('phase4_poc_plan.json')); print('Go\u002FNo-Go:', p['recommendation'])\"\n```\n\n**Templates:** Use `assets\u002Fpoc_scorecard_template.md` for evaluation tracking.\n\n**Output:** POC plan, evaluation scorecard, go\u002Fno-go recommendation.\n\n**Validation checkpoint:** POC conversion requires scorecard score >60% across all evaluation dimensions (functionality, performance, integration, usability, support). If score \u003C60%, document gaps and loop back to Phase 2 for solution redesign.\n\n---\n\n### Phase 5: Proposal & Closing\n\n**Objective:** Deliver a technical proposal that supports the commercial close.\n\n**Checklist:**\n- [ ] Compile POC results and success metrics\n- [ ] Create technical proposal with implementation plan\n- [ ] Address outstanding objections with evidence\n- [ ] Support pricing and packaging discussions\n- [ ] Conduct win\u002Floss analysis post-decision\n\n**Templates:** Use `assets\u002Ftechnical_proposal_template.md` for the proposal document.\n\n**Output:** Technical proposal, implementation timeline, risk mitigation plan.\n\n---\n\n## Python Automation Tools\n\n### 1. RFP Response Analyzer\n\n**Script:** `scripts\u002Frfp_response_analyzer.py`\n\n**Purpose:** Parse RFP\u002FRFI requirements, score coverage, identify gaps, and generate bid\u002Fno-bid recommendations.\n\n**Coverage Categories:** Full (100%), Partial (50%), Planned (25%), Gap (0%).  \n**Priority Weighting:** Must-Have 3×, Should-Have 2×, Nice-to-Have 1×.\n\n**Bid\u002FNo-Bid Logic:**\n- **Bid:** Coverage >70% AND must-have gaps ≤3\n- **Conditional Bid:** Coverage 50–70% OR must-have gaps 2–3\n- **No-Bid:** Coverage \u003C50% OR must-have gaps >3\n\n**Usage:**\n```bash\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json            # human-readable\npython scripts\u002Frfp_response_analyzer.py assets\u002Fsample_rfp_data.json --format json  # JSON output\npython scripts\u002Frfp_response_analyzer.py --help\n```\n\n**Input Format:** See `assets\u002Fsample_rfp_data.json` for the complete schema.\n\n---\n\n### 2. Competitive Matrix Builder\n\n**Script:** `scripts\u002Fcompetitive_matrix_builder.py`\n\n**Purpose:** Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.\n\n**Feature Scoring:** Full (3), Partial (2), Limited (1), None (0).\n\n**Usage:**\n```bash\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json              # human-readable\npython scripts\u002Fcompetitive_matrix_builder.py competitive_data.json --format json  # JSON output\n```\n\n**Output Includes:** Feature comparison matrix, weighted competitive scores, differentiators, vulnerabilities, and win themes.\n\n---\n\n### 3. POC Planner\n\n**Script:** `scripts\u002Fpoc_planner.py`\n\n**Purpose:** Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards.\n\n**Default Phase Breakdown:**\n- **Week 1:** Setup — environment provisioning, data migration, configuration\n- **Weeks 2–3:** Core Testing — primary use cases, integration testing\n- **Week 4:** Advanced Testing — edge cases, performance, security\n- **Week 5:** Evaluation — scorecard completion, stakeholder review, go\u002Fno-go\n\n**Usage:**\n```bash\npython scripts\u002Fpoc_planner.py poc_data.json              # human-readable\npython scripts\u002Fpoc_planner.py poc_data.json --format json  # JSON output\n```\n\n**Output Includes:** Phased POC plan, resource allocation, success criteria, evaluation scorecard, risk register, and go\u002Fno-go recommendation framework.\n\n---\n\n## Reference Knowledge Bases\n\n| Reference | Description |\n|-----------|-------------|\n| `references\u002Frfp-response-guide.md` | RFP\u002FRFI response best practices, compliance matrix, bid\u002Fno-bid framework |\n| `references\u002Fcompetitive-positioning-framework.md` | Competitive analysis methodology, battlecard creation, objection handling |\n| `references\u002Fpoc-best-practices.md` | POC planning methodology, success criteria, evaluation frameworks |\n\n## Asset Templates\n\n| Template | Purpose |\n|----------|---------|\n| `assets\u002Ftechnical_proposal_template.md` | Technical proposal with executive summary, solution architecture, implementation plan |\n| `assets\u002Fdemo_script_template.md` | Demo script with agenda, talking points, objection handling |\n| `assets\u002Fpoc_scorecard_template.md` | POC evaluation scorecard with weighted scoring |\n| `assets\u002Fsample_rfp_data.json` | Sample RFP data for testing the analyzer |\n| `assets\u002Fexpected_output.json` | Expected output from rfp_response_analyzer.py |\n\n## Integration Points\n\n- **Marketing Skills** - Leverage competitive intelligence and messaging frameworks from `..\u002F..\u002Fmarketing-skill\u002F`\n- **Product Team** - Coordinate on roadmap items flagged as \"Planned\" in RFP analysis from `..\u002F..\u002Fproduct-team\u002F`\n- **C-Level Advisory** - Escalate strategic deals requiring executive engagement from `..\u002F..\u002Fc-level-advisor\u002F`\n- **Customer Success** - Hand off POC results and success criteria to CSM from `..\u002Fcustomer-success-manager\u002F`\n\n---\n\n**Last Updated:** February 2026\n**Status:** Production-ready\n**Tools:** 3 Python automation scripts\n**References:** 3 knowledge base documents\n**Templates:** 5 asset files\n",{"name":5,"description":7},"main","13d9afadbb6a87d6209fe4bd6ca2bbe4553119ac",".agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer",0,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two","https:\u002F\u002Fkalmeron-two.vercel.app","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch","2026-10-05 12:24:53",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill sales-engineer",{"tool":62,"command":63},"bunx","bunx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill sales-engineer",{"tool":65,"command":66},"pnpm","pnpm dlx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill sales-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002FSKILL.md",true,[70,76,80,84,88,92,98,102,106,112,116],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Fdemo_script_template.md","ASSET","资产文件",7744,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fassets\u002Fdemo_script_template.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fexpected_output.json",14764,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fassets\u002Fexpected_output.json",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fpoc_scorecard_template.md",5771,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fassets\u002Fpoc_scorecard_template.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fsample_rfp_data.json",7663,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fassets\u002Fsample_rfp_data.json",{"path":89,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftechnical_proposal_template.md",6855,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fassets\u002Ftechnical_proposal_template.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcompetitive-positioning-framework.md","REFERENCE","参考文档",9421,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Freferences\u002Fcompetitive-positioning-framework.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fpoc-best-practices.md",11349,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Freferences\u002Fpoc-best-practices.md",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Frfp-response-guide.md",7340,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Freferences\u002Frfp-response-guide.md",{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fcompetitive_matrix_builder.py","SCRIPT","脚本",17622,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fscripts\u002Fcompetitive_matrix_builder.py",{"path":113,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fpoc_planner.py",26723,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fscripts\u002Fpoc_planner.py",{"path":117,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Frfp_response_analyzer.py",19885,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-growth-skills\u002Fsales-engineer\u002Fscripts\u002Frfp_response_analyzer.py",[121,134,159,178,207,237],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":43},"01M719SWYD9RGS97HJ69PXWY62","add-new-agent","خطوات تفصيليّة لإضافة وكيل ذكاء اصطناعي جديد إلى منصّة Kalmeron من الفكرة إلى الإنتاج","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002FSKILL.md",[128],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[130,131,132,133],"add","add new agent","new","new agent",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":151,"publishedAt":43},"01M719SSKNBA7T5NS7V6DP0PX4","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[140,143,146],{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":144,"categoryName":145,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[152,153,132,38,154,155,156,157,158],"writing skills","writing","work","editing","deployment","use","Existing",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":167,"publishedAt":43},"01M719SRFDNKA3044QD3FYZ05R","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[165,166],{"categoryNo":144,"categoryName":145,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[168,153,169,170,171,172,38,157,173,174,175,176,177],"writing plans","plans","code","requirements","you","for","task","multi","spec","multi-step task",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":190,"publishedAt":43},"01M719SPN5FM1JYJSR9DGJQPZ0","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[184,187],{"categoryNo":185,"categoryName":186,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":188,"categoryName":189,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000032","设计师",[191,192,193,194,195,196,197,198,199,200,201,170,173,202,203,204,157,38,205,206],"web design","web design guidelines","web","design","guidelines","review","accessibility","ux","audit","compliance","check","vercel","interface","web interface guidelines","best practices","file",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":211,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":218,"publishedAt":43},"01M719SK11T05QYVPTWWYMYY5B","vitest","Set up Vitest testing in any project — detects project type (Cloudflare Workers, React, Node), generates vitest.config.ts, test setup, utilities, and sample tests. Also covers mocking patterns, coverage config, workspace setup, and Jest migration. Trigger with 'set up vitest', 'add tests', 'configure vitest', 'migrate from jest', 'vitest config', 'add unit tests', or 'testing setup'.","MIT","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvitest\u002FSKILL.md",[214,215],{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":216,"categoryName":217,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[209,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,42,235,236],"cloudflare","cloudflare workers","config","node","sample","react","jest","migrate","configure","Utilities","up","testing","workspace setup","project","unit","SET","test setup","patterns",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":243,"publishedAt":43},"01M719SGV9R1N88QWAB7Y925HD","verification-loops","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions always.","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverification-loops\u002FSKILL.md",[],[244,245,246,247,157,248,249,250,251,252,253,254,154,255,256,38],"loops","verification","verification loops","claim","assertions","prs","complete","evidence","running","commands","about","claims","output"]