Agent skill · Business & Finance

cto-advisor

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. 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.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill cto-advisor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 12 KB
Bundled scripts: yes
Version: 2.0.0
Declared author: Alireza Rezvani
Path: c-level-advisor/skills/cto-advisor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CTO Advisor Technical leadership frameworks for architecture, engineering teams, technology strategy, and technical decision-making. ## Keywords CTO, chief technology officer, tech debt, technical debt, architecture, engineering metrics, DORA, team scaling, technology evaluation, build vs buy, cloud migration, platform engineering, AI/ML strategy, system design, incident response, engineering culture ## Quick Start ```bash python scripts/tech_debt_analyzer.py # Assess technical debt severity and remediation plan python scripts/team_scaling_calculator.py # Model engineering team growth and cost ``` ## Core Responsibilities ### 1. Technology Strategy Align technology investments with business priorities. **Strategy components:** - Technology vision (3-year: where the platform is going) - Architecture roadmap (what to build, refactor, or replace) - Innovation budget (10-20% of engineering capacity for experimentation) - Build vs buy decisions (default: buy unless it's your core IP) - Technical debt strategy (management, not elimination) See `references/technology_evaluation_framework.md` for the full evaluation framework. ### 2. Engineering Team Leadership Scale the engineering org'

What's inside
Steps it walks through
  1. Keywords
  2. Quick Start
  3. Core Responsibilities
  4. 1. Technology Strategy
  5. 2. Engineering Team Leadership
  6. 3. Architecture Governance
  7. 4. Vendor & Platform Management
  8. 5. Crisis Management
  9. Workflows
  10. Tech Debt Assessment Workflow
  11. ADR Creation Workflow
  12. Build vs Buy Analysis Workflow
  13. Key Questions a CTO Asks
  14. CTO Metrics Dashboard
Ships with 5 files
  • references/architecture_decision_records.md
  • references/engineering_metrics.md
  • references/technology_evaluation_framework.md
  • scripts/team_scaling_calculator.py
  • scripts/tech_debt_analyzer.py
Commands it runs
python scripts/tech_debt_analyzer.py      # Assess technical debt severity and remediation plan
python scripts/team_scaling_calculator.py  # Model engineering team growth and cost
python scripts/tech_debt_analyzer.py --output report.json
More from claude-skills
All skills →
About this skill
What does the cto-advisor skill do?

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. 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.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill cto-advisor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going