[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73RVCY75HJP3GEBJF3F0APA":3,"skill-same:01M73RVCY75HJP3GEBJF3F0APA":63},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M73RVCY75HJP3GEBJF3F0APA","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.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcto-advisor\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30,"tech-stack":31,"python-tools":32},"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","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fcto-advisor",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill cto-advisor",{"tool":49,"command":50},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill cto-advisor",{"tool":52,"command":53},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill cto-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcto-advisor\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"skill-report.json","REFERENCE","参考文档",30354,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcto-advisor\u002Fskill-report.json",[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":71},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":71},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":71},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":71},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":71},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]