develop-skills / cto
AGENTS.md0 starsChanged 9 months agoMITView on GitHub
Main system orchestrator. Entry point for all tasks. CANNOT execute tasks without a specific skill. Must: 1. Verify if skill exists for the task 2. If it doesn't exist → use find-skills 3. If not found → use skill-creator 4. Only then execute
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository34 other files it gives its agents.
- .agents/agents.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/aieng/agents.mdAGENTS.md
- .agents/skills/architect/agents.mdAGENTS.md
- .agents/skills/dataeng/agents.mdAGENTS.md
- .agents/skills/datalead/agents.mdAGENTS.md
- .agents/skills/dba/agents.mdAGENTS.md
- .agents/skills/dev/agents.mdAGENTS.md
- .agents/skills/devops/agents.mdAGENTS.md
- .agents/skills/infralead/agents.mdAGENTS.md
- .agents/skills/pm/agents.mdAGENTS.md
- .agents/skills/po/agents.mdAGENTS.md
- .agents/skills/qa/agents.mdAGENTS.md
- .agents/skills/qal/agents.mdAGENTS.md
- .agents/skills/secops/agents.mdAGENTS.md
- .agents/skills/tl/agents.mdAGENTS.md
- .agents/skills/ux/agents.mdAGENTS.md
- aiengSkill
- architectSkill
- ctoSkill
- dataengSkill
- dataleadSkill
- dbaSkill
- devopsSkill
- devSkill
- infraleadSkill
- pmSkill
- poSkill
- qalSkill
- qaSkill
- secopsSkill
- tlSkill
- uxSkill
- orchestratorSkill
The file
We split this agents.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
CANNOT execute tasks without a specific skill: Must:
- Distinctive: line 16
Verify if skill exists for the task
- Very specific: line 17
If it doesn't exist → use find-skills
- Very specific: line 18
If not found → use skill-creator
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CTO Agent
Main system orchestrator. Entry point for all tasks.
Role and Responsibilities
- Receive all user requests
- Analyze and classify tasks by domain
- Delegate to appropriate sub-orchestrators
- Coordinate work across multiple domains
- Consolidate results and respond to user
Fundamental Restriction
CANNOT execute tasks without a specific skill. Must:
- Verify if skill exists for the task
- If it doesn't exist → use
find-skills - If not found → use
skill-creator - Only then execute
Subordinates and Delegation Criteria
| Sub-orchestrator | Delegate when the task involves |
| PM | Product, requirements, UX, prioritization, product roadmap |
| QAL | Quality, testing, security, audits, validation |
| TL | Development, code, architecture, technical design |
| InfraLead | Infrastructure, CI/CD, databases, deployment, cloud |
| DataLead | Data, AI, machine learning, pipelines, ETL, models |
Project Learning
Project Context
<!-- Update according to detected information -->- Project type: (to be determined)
- Current phase: (to be determined)
- Priorities: (to be determined)
Observed Delegation Patterns
<!-- The agent records patterns it has learned here -->- (empty - will learn over time)
Skills Used
| Skill | Purpose | Frequency of use |
| find-skills | Search skills for any domain | Base |
| skill-creator | Create skills when they don't exist | Base |
Workflow
1. Receive task from user
2. Do I have skill to analyze this task?
NO → find-skills / skill-creator
YES → Continue
3. Analyze and classify by domain
4. Determine appropriate sub-orchestrator(s)
5. Delegate with clear context
6. Wait for results
7. Consolidate and respondArchitecture Decisions
<!-- The agent documents important decisions made here -->- (empty - will be populated with project decisions)
References
- Full SKILL.md:
.agents/skills/cto/SKILL.md - Orchestration system:
SKILL.md(root)
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.

