SkillAgentSearch skills...

cto-advisor

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy

Install / Use

npx skills add borghei/Claude-Skills --skill cto-advisor

Installs into whichever agent you are using.

About this skill
šŸ“„

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of cto-advisor

cto-advisor scores 89/100 on our quality scale, 1710th of 4,702 Development & Engineering skills we index (top 37%).

Its SKILL.md is 14 KB long, well organised into 74 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so cto-advisor is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

cto-advisor compared with similar skills

All 4 of these similar skills score higher than cto-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
cto-advisor (this skill)by borghei8981757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md

Frequently asked questions

How do I install cto-advisor?
Run npx skills add borghei/Claude-Skills --skill cto-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does cto-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is cto-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is cto-advisor still maintained?
The repository was last updated about 2 months ago, so cto-advisor is actively maintained.

name: cto-advisor description: > Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: c-level domain: cto-leadership updated: 2025-10-20 python-tools: tech_debt_analyzer.py, team_scaling_calculator.py tech-stack: engineering-management, team-organization frameworks: DORA-metrics, architecture-decision-records, engineering-metrics

CTO Advisor

Strategic frameworks and tools for technology leadership, team scaling, and engineering excellence.

Keywords

CTO, 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

Quick Start

For Technical Debt Assessment

python scripts/tech_debt_analyzer.py

Analyzes system architecture and provides prioritized debt reduction plan.

For Team Scaling Planning

python scripts/team_scaling_calculator.py

Calculates optimal hiring plan and team structure for growth.

For Architecture Decisions

Review references/architecture_decision_records.md for ADR templates and examples.

For Technology Evaluation

Use framework in references/technology_evaluation_framework.md for vendor selection.

For Engineering Metrics

Implement KPIs from references/engineering_metrics.md for team performance tracking.

Core Responsibilities

1. Technology Strategy

Vision & Roadmap

  • Define 3-5 year technology vision
  • Create quarterly roadmaps
  • Align with business strategy
  • Communicate to stakeholders

Innovation Management

  • Allocate 20% time for innovation
  • Run hackathons quarterly
  • Evaluate emerging technologies
  • Build proof of concepts

Technical Debt Strategy

# Assess current debt
python scripts/tech_debt_analyzer.py

# Allocate capacity
- Critical debt: 40% capacity
- High debt: 25% capacity  
- Medium debt: 15% capacity
- Low debt: Ongoing maintenance

2. Team Leadership

Scaling Engineering

# Calculate scaling needs
python scripts/team_scaling_calculator.py

# Key ratios to maintain:
- Manager:Engineer = 1:8
- Senior:Mid:Junior = 3:4:2
- Product:Engineering = 1:10
- QA:Engineering = 1.5:10

Performance Management

  • Set clear OKRs quarterly
  • Conduct 1:1s weekly
  • Review performance quarterly
  • Provide growth opportunities

Culture Building

  • Define engineering values
  • Establish coding standards
  • Create learning programs
  • Foster collaboration

3. Architecture Governance

Decision Making

Use ADR template from references/architecture_decision_records.md:

  1. Document context and problem
  2. List all options considered
  3. Record decision and rationale
  4. Track consequences

Technology Standards

  • Language choices
  • Framework selection
  • Database standards
  • Security requirements
  • API design guidelines

System Design Review

  • Weekly architecture reviews
  • Design documentation standards
  • Prototype requirements
  • Performance criteria

4. Vendor Management

Evaluation Process

Follow framework in references/technology_evaluation_framework.md:

  1. Gather requirements (Week 1)
  2. Market research (Week 1-2)
  3. Deep evaluation (Week 2-4)
  4. Decision and documentation (Week 4)

Vendor Relationships

  • Quarterly business reviews
  • SLA monitoring
  • Cost optimization
  • Strategic partnerships

5. Engineering Excellence

Metrics Implementation

From references/engineering_metrics.md:

DORA Metrics (Deploy to production targets):

  • Deployment Frequency: >1/day
  • Lead Time: <1 day
  • MTTR: <1 hour
  • Change Failure Rate: <15%

Quality Metrics:

  • Test Coverage: >80%
  • Code Review: 100%
  • Technical Debt: <10%

Team Health:

  • Sprint Velocity: ±10% variance
  • Unplanned Work: <20%
  • On-call Incidents: <5/week

Weekly Cadence

Monday

  • Leadership team sync
  • Review metrics dashboard
  • Address escalations

Tuesday

  • Architecture review
  • Technical interviews
  • 1:1s with directs

Wednesday

  • Cross-functional meetings
  • Vendor meetings
  • Strategy work

Thursday

  • Team all-hands (monthly)
  • Sprint reviews (bi-weekly)
  • Technical deep dives

Friday

  • Strategic planning
  • Innovation time
  • Week recap and planning

Quarterly Planning

Q1 Focus: Foundation

  • Annual planning
  • Budget allocation
  • Team goal setting
  • Technology assessment

Q2 Focus: Execution

  • Major initiatives launch
  • Mid-year hiring push
  • Performance reviews
  • Architecture evolution

Q3 Focus: Innovation

  • Hackathon
  • Technology exploration
  • Team development
  • Process optimization

Q4 Focus: Planning

  • Next year strategy
  • Budget planning
  • Promotion cycles
  • Debt reduction sprint

Crisis Management

Incident Response

  1. Immediate (0-15 min):

    • Assess severity
    • Activate incident team
    • Begin communication
  2. Short-term (15-60 min):

    • Implement fixes
    • Update stakeholders
    • Monitor systems
  3. Resolution (1-24 hours):

    • Verify fix
    • Document timeline
    • Customer communication
  4. Post-mortem (48-72 hours):

    • Root cause analysis
    • Action items
    • Process improvements

Types of Crises

Security Breach

  • Isolate affected systems
  • Engage security team
  • Legal/compliance notification
  • Customer communication plan

Major Outage

  • All-hands response
  • Status page updates
  • Executive briefings
  • Customer outreach

Data Loss

  • Stop writes immediately
  • Assess recovery options
  • Begin restoration
  • Impact analysis

Stakeholder Management

Board/Executive Reporting

Monthly:

  • KPI dashboard
  • Risk register
  • Major initiatives status

Quarterly:

  • Technology strategy update
  • Team growth and health
  • Innovation highlights
  • Budget review

Cross-functional Partners

Product Team

  • Weekly roadmap sync
  • Sprint planning participation
  • Technical feasibility reviews
  • Feature estimation

Sales/Marketing

  • Technical sales support
  • Product capability briefings
  • Customer reference calls
  • Competitive analysis

Finance

  • Budget management
  • Cost optimization
  • Vendor negotiations
  • Capex planning

Strategic Initiatives

Digital Transformation

  1. Assess current state
  2. Define target architecture
  3. Create migration plan
  4. Execute in phases
  5. Measure and adjust

Cloud Migration

  1. Application assessment
  2. Migration strategy (7Rs)
  3. Pilot applications
  4. Full migration
  5. Optimization

Platform Engineering

  1. Define platform vision
  2. Build core services
  3. Create self-service tools
  4. Enable team adoption
  5. Measure efficiency

AI/ML Integration

  1. Identify use cases
  2. Build data infrastructure
  3. Develop models
  4. Deploy and monitor
  5. Scale adoption

Communication Templates

Technology Strategy Presentation

1. Executive Summary (1 slide)
2. Current State Assessment (2 slides)
3. Vision & Strategy (2 slides)
4. Roadmap & Milestones (3 slides)
5. Investment Required (1 slide)
6. Risks & Mitigation (1 slide)
7. Success Metrics (1 slide)

Team All-hands

1. Wins & Recognition (5 min)
2. Metrics Review (5 min)
3. Strategic Updates (10 min)
4. Demo/Deep Dive (15 min)
5. Q&A (10 min)

Board Update Email

Subject: Engineering Update - [Month]

Highlights:
• [Major achievement]
• [Key metric improvement]
• [Strategic progress]

Challenges:
• [Issue and mitigation]

Next Month:
• [Priority 1]
• [Priority 2]

Detailed metrics attached.

Tools & Resources

Essential Tools

  • Architecture: Draw.io, Lucidchart, C4 Model
  • Metrics: DataDog, Grafana, LinearB
  • Planning: Jira, Confluence, Notion
  • Communication: Slack, Zoom, Loom
  • Development: GitHub, GitLab, Bitbucket

Key Resources

  • Books:

    • "The Manager's Path" - Camille Fournier
    • "Accelerate" - Nicole Forsgren
    • "Team Topologies" - Skelton & Pais
  • Frameworks:

    • DORA metrics
    • SPACE framework
    • Team Topologies
  • Communities:

    • CTO Craft
    • Engineering Leadership Slack
    • LeadDev community

Success Indicators

āœ… Technical Excellence

  • System uptime >99.9%
  • Deploy multiple times daily
  • Technical debt <10% capacity
  • Security incidents = 0

āœ… Team Success

  • Team satisfaction >8/10
  • Attrition <10%
  • Filled positions >90%
  • Diversity improving

āœ… Business Impact

  • Features on-time >80%
  • Engineering enables revenue
  • Cost per transaction decreasing
  • Innovation driving growth

Red Flags to Watch

āš ļø Increasing technical debt
āš ļø Rising attrition rate
āš ļø Slowing velocity
āš ļø Growing incidents
āš ļø Team morale declining
āš ļø Budget overruns
āš ļø Vendor dependencies āš ļø Security vulnerabilities


Tool Reference

1. tech_debt_analyzer.py

Analyzes system architecture for technical debt across 5 categories (architecture, code quality, infrastructure, security, performance). Calculates weighted debt scores, prioritizes reduction actions, estimates effort, and assesses risk levels.

python scripts/tech_debt_analyzer.py --input system_config.json --json
python scripts/tech_debt_analyzer.py --input system_config.json

| Flag | Type | Description | |------|------|-------------| | --input | optional | Path to JSON file with system configuration (category indicators scored 0-100, team size, criticality, business context). Uses built-in example if omitted | | --json | optional | Output in JSON format instead of human-readable text |

2. team_scaling_calculator.py

Calculates optimal engineering team scaling plans including hiring timeline, role distribution, team structure design, budget projections, and risk assessment. Applies Brooks' Law and Conway's Law factors.

python scripts/team_scaling_calculator.py --input team_data.json --json
python scripts/team_scaling_calculator.py --input team_data.json

| Flag | Type | Description | |------|------|-------------| | --input | optional | Path to JSON file with current state (headcount, roles, velocity) and growth targets (target headcount, timeline). Uses built-in example if omitted | | --json | optional | Output in JSON format instead of human-readable text |


Troubleshooting

| Problem | Likely Cause | Resolution | |---------|-------------|------------| | Tech debt score increasing despite dedicated sprints | Debt reduction not keeping pace with new debt creation | Implement debt prevention gates (code review, architecture review); track debt creation rate alongside reduction rate | | DORA metrics improving but customer satisfaction declining | Shipping faster but not shipping the right things | Add customer-impact metrics alongside DORA; review feature adoption rates; reconnect with product team on priorities | | Team scaling plan keeps missing hiring targets | Unrealistic timeline, insufficient recruiting capacity, or poor employer brand | Adjust timeline using 25% max quarterly growth rate; add recruiting resources (1 per 50 annual hires); invest in employer brand | | Architecture decisions not documented or followed | No ADR process or ADRs created but not referenced | Implement lightweight ADR template; make ADR review part of design review; link ADRs to relevant code | | Engineering team morale declining during rapid growth | Culture dilution, unclear expectations, or insufficient onboarding | Implement structured onboarding; maintain 1:8 manager ratio; run quarterly team health surveys | | Vendor lock-in creating strategic risk | No evaluation framework or over-reliance on single vendor | Run technology evaluation for critical vendo

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
cto-advisor — Universal Skill: Install & Safety Check | SkillAgent