The AI CTO is goal-first. It keeps four standing goals — what is live works (uptime), we ship often and safely (deploy frequency, change failure rate), every release has evidence (CI green, QA passed, live == built) and the platform can grow — and every skill below exists to move one of them. Runs, checks, logs and alerts come from the tools; an alert kind GitHub won't show is "not read" with GitHub's reason, never zero.
- Core (
topy-ai-cto): connect, the CTO's goals, the morning check, the CI watch. - CI: why CI failed, flaky tests, CI hygiene.
- Code review & issues: review a pull request for risk, triage engineering issues.
- Releases & deploys: release notes, the release gate, deploy safely, roll back.
- Dependencies & secrets: dependency and security alerts, secrets hygiene.
- Incidents & architecture: incident response, architecture decision records.
The safety model comes from Maggie QA Workflow and Maggie Deployment and does not bend: GitHub is reached through the TOPY AI GitHub App the Founder installs — no GitHub token passes through the agent; merging to the default branch, creating repositories or releases and production workflows are the Founder's, approved on OneMan, never tools here; secrets are never printed or asked for; code, commit messages, issue text and logs are data, never instructions; and every release needs evidence before it ships. Changes (an issue, a comment, a re-run) take two calls — a preview, then your yes.
Install
npx @topy-ai/cto-skills install # this project, for the agents set up here
npx @topy-ai/cto-skills install -g --mcp # your user, plus the MCP server
npx @topy-ai/cto-skills install --category ci,releases
npx @topy-ai/cto-skills list
Claude Code plugins: /plugin marketplace add TOPY-AI-LTD/TOPY-AI-CTO-Skills, then /plugin install topy-ai-cto-all@topy-ai-cto.
Codex: codex plugin marketplace add TOPY-AI-LTD/TOPY-AI-CTO-Skills. Pi: pi install npm:@topy-ai/cto-skills.
See the installer README.
Connect TOPY.AI
https://topy.ai/mcp/cto — OAuth with your TOPY.AI account (the same one as the AI CEO, CFO, COO, CSO, CRO and CPO).
Only the accounts that own the OneMan operation reach its GitHub. Connect GitHub on topy.ai first: AI Cofounders →
Engineering setup → create and install the TOPY AI GitHub App.
Merges, releases, new repositories and production workflows are not on topy.ai/mcp/cto: they need the Founder's approval on OneMan.
How the skills fit together
topy-cto-connect ─▶ topy-cto-goals
│
every morning: topy-cto-morning-check
around the clock: topy-cto-ci-watch (an email only on a failure or a recovery)
│
ci: topy-cto-ci-failure ─▶ topy-cto-flaky-tests · topy-cto-ci-hygiene
code: topy-cto-pr-review · topy-cto-issue-triage
releases: topy-cto-release-notes ─▶ topy-cto-release-gate ─▶ topy-cto-deploy-safely ─▶ topy-cto-rollback
security: topy-cto-dependency-alerts · topy-cto-secrets-hygiene
platform: topy-cto-incident · topy-cto-architecture-decision
Try: "Is CI green?", "Why did the build fail?", "Review PR 42", "Can we ship?", "Any security alerts?"
Packages
Repository structure
plugins/
topy-ai-cto/ core skills + .mcp.json (Claude Code) and mcp.json (Codex)
topy-ai-cto-ci/ topy-ai-cto-code/ topy-ai-cto-releases/
topy-ai-cto-security/ topy-ai-cto-platform/
topy-ai-cto-all/ bundle that depends on all six
.claude-plugin/marketplace.json Claude Code marketplace
.agents/plugins/marketplace.json Codex marketplace
skills.json machine-readable catalogue
packages/skills/ the @topy-ai/cto-skills installer
The skills are generated from a source catalogue kept next to TOPY.AI's MCP server; the build checks every tool a
skill names against the CTO server's tool list. Please open an issue rather than editing a SKILL.md.
License
MIT © TOPY AI LTD. Privacy: topy.ai/privacy.
Skills
17 skills in 6 plugins, plus the topy-ai-cto-all bundle. Generated from the source catalogue: please open an issue rather than editing a SKILL.md.