CTO / Chief Technology Officer

What This Skill Does

The CTO skill transforms OpenClaw into a strategic technical partner, bridging the gap between business objectives and engineering reality. It provides a structured framework for architecture decisions, team growth, technical debt mitigation, and operational excellence. The skill utilizes a 'Tech-Serves-Business' philosophy, ensuring that engineering efforts remain aligned with company growth stages and market requirements. By implementing clear heuristics like the 'Build vs Buy' matrix and a stage-based focus, this skill helps agents make high-leverage technical decisions while minimizing long-term maintenance costs.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/cto

Use Cases

• Architecture Strategy: Evaluating whether to move from a monolith to microservices based on team size and complexity.
• Hiring & Scaling: Developing hiring rubrics that prioritize growth-slope and values alignment over legacy skill sets.
• Build vs Buy: Providing a data-driven justification for outsourcing non-core infrastructure versus developing proprietary IP.
• Technical Debt Management: Balancing the 80/20 rule to maintain feature velocity while ensuring system stability.
• Non-Technical Translation: Communicating complex technical bottlenecks to CEOs or investors using business-centric metrics.

Example Prompts

1. "We are a Series A startup with 12 engineers. We are struggling with slow deployments. Should we invest in a platform engineering team, or can we solve this with better CI/CD automation? Provide a plan based on our stage."
2. "We need to decide whether to build our own authentication service or buy Auth0. Run a Build vs Buy analysis considering we are pre-PMF but handling sensitive PII data."
3. "Evaluate this technical debt list. Which items can we safely defer to the next quarter, and which represent immediate risks to our scaling efforts?"

Tips & Limitations

• Context is Key: Always provide the company's current stage (e.g., Pre-PMF, Seed, Series B) to receive relevant advice.
• Boring Tech: The skill defaults to stable, battle-tested solutions. If you are a research-driven organization, specify that you prioritize innovation over stability.
• Human Oversight: While the CTO skill provides rigorous architectural frameworks, critical one-way-door decisions should always be reviewed by a human lead to account for edge-case business risks not captured in documentation.