[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7EDPCEDESTRMD3DF7CHKH":3,"skill-same:01M7D7EDPCEDESTRMD3DF7CHKH":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D7EDPCEDESTRMD3DF7CHKH","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'.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","business-growth\u002Fskills\u002Fsales-engineer","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill sales-engineer",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill sales-engineer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill sales-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002FSKILL.md",true,[45,51,55,59,63,67,73,77,81,87,91],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Fdemo_script_template.md","ASSET","资产文件",7744,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fassets\u002Fdemo_script_template.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fexpected_output.json",14764,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fassets\u002Fexpected_output.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fpoc_scorecard_template.md",5771,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fassets\u002Fpoc_scorecard_template.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fsample_rfp_data.json",7663,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fassets\u002Fsample_rfp_data.json",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Ftechnical_proposal_template.md",6855,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fassets\u002Ftechnical_proposal_template.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcompetitive-positioning-framework.md","REFERENCE","参考文档",9421,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Freferences\u002Fcompetitive-positioning-framework.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fpoc-best-practices.md",11349,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Freferences\u002Fpoc-best-practices.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Frfp-response-guide.md",7340,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Freferences\u002Frfp-response-guide.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fcompetitive_matrix_builder.py","SCRIPT","脚本",17622,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fscripts\u002Fcompetitive_matrix_builder.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fpoc_planner.py",26723,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fscripts\u002Fpoc_planner.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Frfp_response_analyzer.py",19885,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002Fscripts\u002Frfp_response_analyzer.py",[96,103,110,117,124,131],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]