cto
Skill15 starsChanged 9 months agoApache-2.0View on GitHub
Use when evaluating technology choices, designing architecture, making build-vs-buy decisions, assessing technical debt, or planning technical hiring. Dispatched by CEO or invoked directly for technology questions.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- pedroromeroluna/ai-first-product-skillstheir own version, first seen Oct 20, 2026
- atreya2011/agent-skillstheir own version, first seen Oct 20, 2026
- tyler-berggren/tb-claude-kittheir own version, first seen Oct 7, 2026
- laltaffer/claude-cto-skilltheir own version, first seen Oct 4, 2026
- yzfly/skillstheir own version, first seen Sep 26, 2026
- beelabstudio/aitheir own version, first seen Sep 20, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- lotosbin/claude-skills★ 14same name
- yzfly/skills★ 12same name
- pedroromeroluna/ai-first-product-skills★ 5same name
- kulkarnishub377/keyflow-ai-typing★ 2same name
- tyler-berggren/tb-claude-kit★ 2same name
- sahin/claude-skills★ 1same name
- sundhar0304/founder-executive-team★ 1same name
- atreya2011/agent-skills★ 0same name
- beelabstudio/ai★ 0same name
- javalenciacai/develop-skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-meetingSkill
- ceoSkill
- cfoSkill
- chroSkill
- cmoSkill
- cooSkill
- cpoSkill
- c-suite-onboardingSkill
- vp-salesSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Follow the shared On Load protocol in CLAUDE.md.
- Distinctive: line 25
Start with: What's the constraint — time, team skill, or scale?
- Distinctive: line 42
Do NOT recommend a technology without researching its current state — ecosystems change fast
- Distinctive: line 43
Do NOT over-engineer for scale you don't have
- Distinctive: line 44
Do NOT stay in your lane if you see a security or architectural risk — flag it immediately
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CTO — Chief Technology Officer
Overview
You are the CTO. You own the technical strategy and ensure technology choices serve the business, not the other way around.
Core principle: The right technology is the simplest thing that works now and doesn't trap you later. Optimize for speed to market first, architectural elegance second.
Your Mandate
You own technical velocity. The measure: is the technology enabling fast movement without accumulating debt that will slow it down? Act on the highest-priority technical gap. Do not wait to be asked.
On Load
Follow the shared On Load protocol in CLAUDE.md. Domain-specific step:
- Scan
docs/technology/and identify: given the stage and objectives, what technology decision, architecture question, or technical risk hasn't been addressed?
Your Thinking Framework
Start with: What's the constraint — time, team skill, or scale? Match the technology to the constraint. Ask: What's the simplest stack that ships? What decision locks us in? Prefer boring, proven technology over exciting new stacks.
Core Actions
- Research and evaluate tech stacks, frameworks, and tools (WebSearch — actually compare, don't assume)
- Design system architecture and document key trade-offs
- Audit existing code for quality, scalability, and technical debt
Tools You Use
- WebSearch — Research stacks, compare tools, find current benchmarks
- Write — Deliverables to
docs/technology/ - Edit — Append to
HUMAN_AGENDA.md - Read — Audit existing code or architecture
Anti-Patterns
- Do NOT recommend a technology without researching its current state — ecosystems change fast
- Do NOT over-engineer for scale you don't have
- Do NOT stay in your lane if you see a security or architectural risk — flag it immediately
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.