[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE1B1H4DPRV159PSC71Q0S":3,"skill-same:01M6AE1B1H4DPRV159PSC71Q0S":104},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6AE1B1H4DPRV159PSC71Q0S","cto-advisor",null,"Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"cto","cto advisor","advisor","management","debt","for","records","tech","dora metrics","frameworks","guidance","use","tech debt","architecture","strategy","decisions","calculator","team","templates","Evaluation","engineering","metrics","teams","2026-11-10 10:12:30",false,"---\nname: cto-advisor\ndescription: Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: cto-leadership\n  updated: 2025-10-20\n  python-tools: tech_debt_analyzer.py, team_scaling_calculator.py\n  frameworks: DORA-metrics, architecture-decision-records, engineering-metrics\n  tech-stack: engineering-management, team-organization\n---\n\n# CTO Advisor\n\nStrategic frameworks and tools for technology leadership, team scaling, and engineering excellence.\n\n## Keywords\nCTO, chief technology officer, technical leadership, tech debt, technical debt, engineering team, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, ADR, architecture decision records, technology strategy, engineering leadership, engineering organization, team structure, hiring plan, technical strategy, vendor evaluation, technology selection\n\n## Quick Start\n\n### For Technical Debt Assessment\n```bash\npython scripts\u002Ftech_debt_analyzer.py\n```\nAnalyzes system architecture and provides prioritized debt reduction plan.\n\n### For Team Scaling Planning\n```bash\npython scripts\u002Fteam_scaling_calculator.py\n```\nCalculates optimal hiring plan and team structure for growth.\n\n### For Architecture Decisions\nReview `references\u002Farchitecture_decision_records.md` for ADR templates and examples.\n\n### For Technology Evaluation\nUse framework in `references\u002Ftechnology_evaluation_framework.md` for vendor selection.\n\n### For Engineering Metrics\nImplement KPIs from `references\u002Fengineering_metrics.md` for team performance tracking.\n\n## Core Responsibilities\n\n### 1. Technology Strategy\n\n#### Vision & Roadmap\n- Define 3-5 year technology vision\n- Create quarterly roadmaps\n- Align with business strategy\n- Communicate to stakeholders\n\n#### Innovation Management\n- Allocate 20% time for innovation\n- Run hackathons quarterly\n- Evaluate emerging technologies\n- Build proof of concepts\n\n#### Technical Debt Strategy\n```bash\n# Assess current debt\npython scripts\u002Ftech_debt_analyzer.py\n\n# Allocate capacity\n- Critical debt: 40% capacity\n- High debt: 25% capacity  \n- Medium debt: 15% capacity\n- Low debt: Ongoing maintenance\n```\n\n### 2. Team Leadership\n\n#### Scaling Engineering\n```bash\n# Calculate scaling needs\npython scripts\u002Fteam_scaling_calculator.py\n\n# Key ratios to maintain:\n- Manager:Engineer = 1:8\n- Senior:Mid:Junior = 3:4:2\n- Product:Engineering = 1:10\n- QA:Engineering = 1.5:10\n```\n\n#### Performance Management\n- Set clear OKRs quarterly\n- Conduct 1:1s weekly\n- Review performance quarterly\n- Provide growth opportunities\n\n#### Culture Building\n- Define engineering values\n- Establish coding standards\n- Create learning programs\n- Foster collaboration\n\n### 3. Architecture Governance\n\n#### Decision Making\nUse ADR template from `references\u002Farchitecture_decision_records.md`:\n1. Document context and problem\n2. List all options considered\n3. Record decision and rationale\n4. Track consequences\n\n#### Technology Standards\n- Language choices\n- Framework selection\n- Database standards\n- Security requirements\n- API design guidelines\n\n#### System Design Review\n- Weekly architecture reviews\n- Design documentation standards\n- Prototype requirements\n- Performance criteria\n\n### 4. Vendor Management\n\n#### Evaluation Process\nFollow framework in `references\u002Ftechnology_evaluation_framework.md`:\n1. Gather requirements (Week 1)\n2. Market research (Week 1-2)\n3. Deep evaluation (Week 2-4)\n4. Decision and documentation (Week 4)\n\n#### Vendor Relationships\n- Quarterly business reviews\n- SLA monitoring\n- Cost optimization\n- Strategic partnerships\n\n### 5. Engineering Excellence\n\n#### Metrics Implementation\nFrom `references\u002Fengineering_metrics.md`:\n\n**DORA Metrics** (Deploy to production targets):\n- Deployment Frequency: >1\u002Fday\n- Lead Time: \u003C1 day\n- MTTR: \u003C1 hour\n- Change Failure Rate: \u003C15%\n\n**Quality Metrics**:\n- Test Coverage: >80%\n- Code Review: 100%\n- Technical Debt: \u003C10%\n\n**Team Health**:\n- Sprint Velocity: ±10% variance\n- Unplanned Work: \u003C20%\n- On-call Incidents: \u003C5\u002Fweek\n\n## Weekly Cadence\n\n### Monday\n- Leadership team sync\n- Review metrics dashboard\n- Address escalations\n\n### Tuesday\n- Architecture review\n- Technical interviews\n- 1:1s with directs\n\n### Wednesday\n- Cross-functional meetings\n- Vendor meetings\n- Strategy work\n\n### Thursday\n- Team all-hands (monthly)\n- Sprint reviews (bi-weekly)\n- Technical deep dives\n\n### Friday\n- Strategic planning\n- Innovation time\n- Week recap and planning\n\n## Quarterly Planning\n\n### Q1 Focus: Foundation\n- Annual planning\n- Budget allocation\n- Team goal setting\n- Technology assessment\n\n### Q2 Focus: Execution\n- Major initiatives launch\n- Mid-year hiring push\n- Performance reviews\n- Architecture evolution\n\n### Q3 Focus: Innovation\n- Hackathon\n- Technology exploration\n- Team development\n- Process optimization\n\n### Q4 Focus: Planning\n- Next year strategy\n- Budget planning\n- Promotion cycles\n- Debt reduction sprint\n\n## Crisis Management\n\n### Incident Response\n1. **Immediate** (0-15 min):\n   - Assess severity\n   - Activate incident team\n   - Begin communication\n\n2. **Short-term** (15-60 min):\n   - Implement fixes\n   - Update stakeholders\n   - Monitor systems\n\n3. **Resolution** (1-24 hours):\n   - Verify fix\n   - Document timeline\n   - Customer communication\n\n4. **Post-mortem** (48-72 hours):\n   - Root cause analysis\n   - Action items\n   - Process improvements\n\n### Types of Crises\n\n#### Security Breach\n- Isolate affected systems\n- Engage security team\n- Legal\u002Fcompliance notification\n- Customer communication plan\n\n#### Major Outage\n- All-hands response\n- Status page updates\n- Executive briefings\n- Customer outreach\n\n#### Data Loss\n- Stop writes immediately\n- Assess recovery options\n- Begin restoration\n- Impact analysis\n\n## Stakeholder Management\n\n### Board\u002FExecutive Reporting\n**Monthly**:\n- KPI dashboard\n- Risk register\n- Major initiatives status\n\n**Quarterly**:\n- Technology strategy update\n- Team growth and health\n- Innovation highlights\n- Budget review\n\n### Cross-functional Partners\n\n#### Product Team\n- Weekly roadmap sync\n- Sprint planning participation\n- Technical feasibility reviews\n- Feature estimation\n\n#### Sales\u002FMarketing\n- Technical sales support\n- Product capability briefings\n- Customer reference calls\n- Competitive analysis\n\n#### Finance\n- Budget management\n- Cost optimization\n- Vendor negotiations\n- Capex planning\n\n## Strategic Initiatives\n\n### Digital Transformation\n1. Assess current state\n2. Define target architecture\n3. Create migration plan\n4. Execute in phases\n5. Measure and adjust\n\n### Cloud Migration\n1. Application assessment\n2. Migration strategy (7Rs)\n3. Pilot applications\n4. Full migration\n5. Optimization\n\n### Platform Engineering\n1. Define platform vision\n2. Build core services\n3. Create self-service tools\n4. Enable team adoption\n5. Measure efficiency\n\n### AI\u002FML Integration\n1. Identify use cases\n2. Build data infrastructure\n3. Develop models\n4. Deploy and monitor\n5. Scale adoption\n\n## Communication Templates\n\n### Technology Strategy Presentation\n```\n1. Executive Summary (1 slide)\n2. Current State Assessment (2 slides)\n3. Vision & Strategy (2 slides)\n4. Roadmap & Milestones (3 slides)\n5. Investment Required (1 slide)\n6. Risks & Mitigation (1 slide)\n7. Success Metrics (1 slide)\n```\n\n### Team All-hands\n```\n1. Wins & Recognition (5 min)\n2. Metrics Review (5 min)\n3. Strategic Updates (10 min)\n4. Demo\u002FDeep Dive (15 min)\n5. Q&A (10 min)\n```\n\n### Board Update Email\n```\nSubject: Engineering Update - [Month]\n\nHighlights:\n• [Major achievement]\n• [Key metric improvement]\n• [Strategic progress]\n\nChallenges:\n• [Issue and mitigation]\n\nNext Month:\n• [Priority 1]\n• [Priority 2]\n\nDetailed metrics attached.\n```\n\n## Tools & Resources\n\n### Essential Tools\n- **Architecture**: Draw.io, Lucidchart, C4 Model\n- **Metrics**: DataDog, Grafana, LinearB\n- **Planning**: Jira, Confluence, Notion\n- **Communication**: Slack, Zoom, Loom\n- **Development**: GitHub, GitLab, Bitbucket\n\n### Key Resources\n- **Books**: \n  - \"The Manager's Path\" - Camille Fournier\n  - \"Accelerate\" - Nicole Forsgren\n  - \"Team Topologies\" - Skelton & Pais\n  \n- **Frameworks**:\n  - DORA metrics\n  - SPACE framework\n  - Team Topologies\n  \n- **Communities**:\n  - CTO Craft\n  - Engineering Leadership Slack\n  - LeadDev community\n\n## Success Indicators\n\n✅ **Technical Excellence**\n- System uptime >99.9%\n- Deploy multiple times daily\n- Technical debt \u003C10% capacity\n- Security incidents = 0\n\n✅ **Team Success**\n- Team satisfaction >8\u002F10\n- Attrition \u003C10%\n- Filled positions >90%\n- Diversity improving\n\n✅ **Business Impact**\n- Features on-time >80%\n- Engineering enables revenue\n- Cost per transaction decreasing\n- Innovation driving growth\n\n## Red Flags to Watch\n\n⚠️ Increasing technical debt  \n⚠️ Rising attrition rate  \n⚠️ Slowing velocity  \n⚠️ Growing incidents  \n⚠️ Team morale declining  \n⚠️ Budget overruns  \n⚠️ Vendor dependencies  \n⚠️ Security vulnerabilities\n","# CTO Advisor\n\nStrategic frameworks and tools for technology leadership, team scaling, and engineering excellence.\n\n## Keywords\nCTO, chief technology officer, technical leadership, tech debt, technical debt, engineering team, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, ADR, architecture decision records, technology strategy, engineering leadership, engineering organization, team structure, hiring plan, technical strategy, vendor evaluation, technology selection\n\n## Quick Start\n\n### For Technical Debt Assessment\n```bash\npython scripts\u002Ftech_debt_analyzer.py\n```\nAnalyzes system architecture and provides prioritized debt reduction plan.\n\n### For Team Scaling Planning\n```bash\npython scripts\u002Fteam_scaling_calculator.py\n```\nCalculates optimal hiring plan and team structure for growth.\n\n### For Architecture Decisions\nReview `references\u002Farchitecture_decision_records.md` for ADR templates and examples.\n\n### For Technology Evaluation\nUse framework in `references\u002Ftechnology_evaluation_framework.md` for vendor selection.\n\n### For Engineering Metrics\nImplement KPIs from `references\u002Fengineering_metrics.md` for team performance tracking.\n\n## Core Responsibilities\n\n### 1. Technology Strategy\n\n#### Vision & Roadmap\n- Define 3-5 year technology vision\n- Create quarterly roadmaps\n- Align with business strategy\n- Communicate to stakeholders\n\n#### Innovation Management\n- Allocate 20% time for innovation\n- Run hackathons quarterly\n- Evaluate emerging technologies\n- Build proof of concepts\n\n#### Technical Debt Strategy\n```bash\n# Assess current debt\npython scripts\u002Ftech_debt_analyzer.py\n\n# Allocate capacity\n- Critical debt: 40% capacity\n- High debt: 25% capacity  \n- Medium debt: 15% capacity\n- Low debt: Ongoing maintenance\n```\n\n### 2. Team Leadership\n\n#### Scaling Engineering\n```bash\n# Calculate scaling needs\npython scripts\u002Fteam_scaling_calculator.py\n\n# Key ratios to maintain:\n- Manager:Engineer = 1:8\n- Senior:Mid:Junior = 3:4:2\n- Product:Engineering = 1:10\n- QA:Engineering = 1.5:10\n```\n\n#### Performance Management\n- Set clear OKRs quarterly\n- Conduct 1:1s weekly\n- Review performance quarterly\n- Provide growth opportunities\n\n#### Culture Building\n- Define engineering values\n- Establish coding standards\n- Create learning programs\n- Foster collaboration\n\n### 3. Architecture Governance\n\n#### Decision Making\nUse ADR template from `references\u002Farchitecture_decision_records.md`:\n1. Document context and problem\n2. List all options considered\n3. Record decision and rationale\n4. Track consequences\n\n#### Technology Standards\n- Language choices\n- Framework selection\n- Database standards\n- Security requirements\n- API design guidelines\n\n#### System Design Review\n- Weekly architecture reviews\n- Design documentation standards\n- Prototype requirements\n- Performance criteria\n\n### 4. Vendor Management\n\n#### Evaluation Process\nFollow framework in `references\u002Ftechnology_evaluation_framework.md`:\n1. Gather requirements (Week 1)\n2. Market research (Week 1-2)\n3. Deep evaluation (Week 2-4)\n4. Decision and documentation (Week 4)\n\n#### Vendor Relationships\n- Quarterly business reviews\n- SLA monitoring\n- Cost optimization\n- Strategic partnerships\n\n### 5. Engineering Excellence\n\n#### Metrics Implementation\nFrom `references\u002Fengineering_metrics.md`:\n\n**DORA Metrics** (Deploy to production targets):\n- Deployment Frequency: >1\u002Fday\n- Lead Time: \u003C1 day\n- MTTR: \u003C1 hour\n- Change Failure Rate: \u003C15%\n\n**Quality Metrics**:\n- Test Coverage: >80%\n- Code Review: 100%\n- Technical Debt: \u003C10%\n\n**Team Health**:\n- Sprint Velocity: ±10% variance\n- Unplanned Work: \u003C20%\n- On-call Incidents: \u003C5\u002Fweek\n\n## Weekly Cadence\n\n### Monday\n- Leadership team sync\n- Review metrics dashboard\n- Address escalations\n\n### Tuesday\n- Architecture review\n- Technical interviews\n- 1:1s with directs\n\n### Wednesday\n- Cross-functional meetings\n- Vendor meetings\n- Strategy work\n\n### Thursday\n- Team all-hands (monthly)\n- Sprint reviews (bi-weekly)\n- Technical deep dives\n\n### Friday\n- Strategic planning\n- Innovation time\n- Week recap and planning\n\n## Quarterly Planning\n\n### Q1 Focus: Foundation\n- Annual planning\n- Budget allocation\n- Team goal setting\n- Technology assessment\n\n### Q2 Focus: Execution\n- Major initiatives launch\n- Mid-year hiring push\n- Performance reviews\n- Architecture evolution\n\n### Q3 Focus: Innovation\n- Hackathon\n- Technology exploration\n- Team development\n- Process optimization\n\n### Q4 Focus: Planning\n- Next year strategy\n- Budget planning\n- Promotion cycles\n- Debt reduction sprint\n\n## Crisis Management\n\n### Incident Response\n1. **Immediate** (0-15 min):\n   - Assess severity\n   - Activate incident team\n   - Begin communication\n\n2. **Short-term** (15-60 min):\n   - Implement fixes\n   - Update stakeholders\n   - Monitor systems\n\n3. **Resolution** (1-24 hours):\n   - Verify fix\n   - Document timeline\n   - Customer communication\n\n4. **Post-mortem** (48-72 hours):\n   - Root cause analysis\n   - Action items\n   - Process improvements\n\n### Types of Crises\n\n#### Security Breach\n- Isolate affected systems\n- Engage security team\n- Legal\u002Fcompliance notification\n- Customer communication plan\n\n#### Major Outage\n- All-hands response\n- Status page updates\n- Executive briefings\n- Customer outreach\n\n#### Data Loss\n- Stop writes immediately\n- Assess recovery options\n- Begin restoration\n- Impact analysis\n\n## Stakeholder Management\n\n### Board\u002FExecutive Reporting\n**Monthly**:\n- KPI dashboard\n- Risk register\n- Major initiatives status\n\n**Quarterly**:\n- Technology strategy update\n- Team growth and health\n- Innovation highlights\n- Budget review\n\n### Cross-functional Partners\n\n#### Product Team\n- Weekly roadmap sync\n- Sprint planning participation\n- Technical feasibility reviews\n- Feature estimation\n\n#### Sales\u002FMarketing\n- Technical sales support\n- Product capability briefings\n- Customer reference calls\n- Competitive analysis\n\n#### Finance\n- Budget management\n- Cost optimization\n- Vendor negotiations\n- Capex planning\n\n## Strategic Initiatives\n\n### Digital Transformation\n1. Assess current state\n2. Define target architecture\n3. Create migration plan\n4. Execute in phases\n5. Measure and adjust\n\n### Cloud Migration\n1. Application assessment\n2. Migration strategy (7Rs)\n3. Pilot applications\n4. Full migration\n5. Optimization\n\n### Platform Engineering\n1. Define platform vision\n2. Build core services\n3. Create self-service tools\n4. Enable team adoption\n5. Measure efficiency\n\n### AI\u002FML Integration\n1. Identify use cases\n2. Build data infrastructure\n3. Develop models\n4. Deploy and monitor\n5. Scale adoption\n\n## Communication Templates\n\n### Technology Strategy Presentation\n```\n1. Executive Summary (1 slide)\n2. Current State Assessment (2 slides)\n3. Vision & Strategy (2 slides)\n4. Roadmap & Milestones (3 slides)\n5. Investment Required (1 slide)\n6. Risks & Mitigation (1 slide)\n7. Success Metrics (1 slide)\n```\n\n### Team All-hands\n```\n1. Wins & Recognition (5 min)\n2. Metrics Review (5 min)\n3. Strategic Updates (10 min)\n4. Demo\u002FDeep Dive (15 min)\n5. Q&A (10 min)\n```\n\n### Board Update Email\n```\nSubject: Engineering Update - [Month]\n\nHighlights:\n• [Major achievement]\n• [Key metric improvement]\n• [Strategic progress]\n\nChallenges:\n• [Issue and mitigation]\n\nNext Month:\n• [Priority 1]\n• [Priority 2]\n\nDetailed metrics attached.\n```\n\n## Tools & Resources\n\n### Essential Tools\n- **Architecture**: Draw.io, Lucidchart, C4 Model\n- **Metrics**: DataDog, Grafana, LinearB\n- **Planning**: Jira, Confluence, Notion\n- **Communication**: Slack, Zoom, Loom\n- **Development**: GitHub, GitLab, Bitbucket\n\n### Key Resources\n- **Books**: \n  - \"The Manager's Path\" - Camille Fournier\n  - \"Accelerate\" - Nicole Forsgren\n  - \"Team Topologies\" - Skelton & Pais\n  \n- **Frameworks**:\n  - DORA metrics\n  - SPACE framework\n  - Team Topologies\n  \n- **Communities**:\n  - CTO Craft\n  - Engineering Leadership Slack\n  - LeadDev community\n\n## Success Indicators\n\n✅ **Technical Excellence**\n- System uptime >99.9%\n- Deploy multiple times daily\n- Technical debt \u003C10% capacity\n- Security incidents = 0\n\n✅ **Team Success**\n- Team satisfaction >8\u002F10\n- Attrition \u003C10%\n- Filled positions >90%\n- Diversity improving\n\n✅ **Business Impact**\n- Features on-time >80%\n- Engineering enables revenue\n- Cost per transaction decreasing\n- Innovation driving growth\n\n## Red Flags to Watch\n\n⚠️ Increasing technical debt  \n⚠️ Rising attrition rate  \n⚠️ Slowing velocity  \n⚠️ Growing incidents  \n⚠️ Team morale declining  \n⚠️ Budget overruns  \n⚠️ Vendor dependencies  \n⚠️ Security vulnerabilities\n",{"name":5,"license":15,"metadata":47,"description":7},{"author":48,"domain":49,"updated":50,"version":51,"category":52,"frameworks":53,"tech-stack":54,"python-tools":55},"Alireza Rezvani","cto-leadership",1760918400000,"1.0.0","c-level","DORA-metrics, architecture-decision-records, engineering-metrics","engineering-management, team-organization","tech_debt_analyzer.py, team_scaling_calculator.py","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add davila7\u002Fclaude-code-templates --skill cto-advisor",{"tool":72,"command":73},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill cto-advisor",{"tool":75,"command":76},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill cto-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002FSKILL.md",true,[80,86,90,94,100],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Farchitecture_decision_records.md","REFERENCE","参考文档",8716,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002Freferences\u002Farchitecture_decision_records.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fengineering_metrics.md",12365,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002Freferences\u002Fengineering_metrics.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Ftechnology_evaluation_framework.md",9875,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002Freferences\u002Ftechnology_evaluation_framework.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fteam_scaling_calculator.py","SCRIPT","脚本",19950,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Ftech_debt_analyzer.py",17297,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py",[105,135,161,194,229,253],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":116,"publishedAt":42},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[117,118,119,120,121,24,122,123,30,124,125,126,127,128,129,130,131,132,133,134],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":42},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[141],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},[143,23,144,145,146,147,148,149,150,151,152,124,153,154,155,156,157,158,159,160],"technical debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":176,"publishedAt":42},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[167,170,171],{"categoryNo":168,"categoryName":169,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},{"categoryNo":172,"categoryName":173,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[177,178,179,180,181,182,183,24,184,185,186,187,188,189,190,30,191,192,124,193],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":205,"publishedAt":42},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[202],{"categoryNo":203,"categoryName":204,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000009","前端开发",[206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,24,228],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":240,"publishedAt":42},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[236,239],{"categoryNo":237,"categoryName":238,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":203,"categoryName":204,"taxonomyType":114,"taxonomyTypeDesc":115},[241,242,243,244,245,207,246,216,217,247,248,249,250,24,251,126,252],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":257,"sourceHtmlUrl":258,"categories":259,"keywords":267,"publishedAt":42},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[260,263,264],{"categoryNo":261,"categoryName":262,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},{"categoryNo":265,"categoryName":266,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000036","内容创作者",[268,269,270,271,272,273,274,275,209,276,219,153,277,278,279,280,281,189,282,124,283,284,285,286,287,132,288],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]