[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HABQ04DPDPPEAD8W9X6MB":3,"skill-same:01M70HABQ04DPDPPEAD8W9X6MB":101},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70HABQ04DPDPPEAD8W9X6MB","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.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"advisor","cto advisor","cto","management","tech debt","templates","guidance","calculator","decisions","use","strategy","records","frameworks","for","tech","dora metrics","debt","Evaluation","architecture","team","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":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50,"tech-stack":51,"python-tools":52},"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","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill cto-advisor",{"tool":69,"command":70},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill cto-advisor",{"tool":72,"command":73},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill cto-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002FSKILL.md",true,[77,83,87,91,97],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Farchitecture_decision_records.md","REFERENCE","参考文档",8716,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Farchitecture_decision_records.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fengineering_metrics.md",12365,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Fengineering_metrics.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ftechnology_evaluation_framework.md",9875,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Ftechnology_evaluation_framework.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fteam_scaling_calculator.py","SCRIPT","脚本",19950,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Ftech_debt_analyzer.py",17297,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fc-level-advisor\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py",[102,121,154,180,202,222],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":39},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[114,115,116,117,118,119,120],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":39},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[123,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,37,151,152,153],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","code","unknown","generated",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":39},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[160,161],{"categoryNo":128,"categoryName":129,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":162,"categoryName":163,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000036","内容创作者",[156,165,166,167,168,169,170,171,144,172,173,174,175,28,176,177,178,179],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","when","auto","types","Video","创作",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":39},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[186],{"categoryNo":128,"categoryName":129,"taxonomyType":111,"taxonomyTypeDesc":112},[188,189,156,190,191,178,192,193,194,195,196,197,198,199,142,200,175,28,136,201],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":39},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[208,209,210,211],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":128,"categoryName":129,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},{"categoryNo":162,"categoryName":163,"taxonomyType":133,"taxonomyTypeDesc":134},[213,119,214,215,216,217,151,175,28,218,219,220,221],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":230,"publishedAt":39},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[228,229],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},{"categoryNo":162,"categoryName":163,"taxonomyType":133,"taxonomyTypeDesc":134},[231,119,232,140,233,219,175,214,217,28,220],"Rules","writing rules","project rules"]