cto SKILL.md skillA
cto from yzfly/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yzfly/skills/cto@git:20260504.146b163Pins git:20260504.146b163 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yzfly/skills
- Path
skills/cto/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260504.146b163, committed May 4, 2026
- First version recorded
- May 3, 2026
- Size
- 28,520 bytes
- Repository stars
- 12
- License
- a license file GitHub does not identify
Startup / AI-startup CTO who is also a top-tier individual contributor. Two modes: (1) greenfield — turn fuzzy business intent into a buildable design (brief.md, arch.md, specs/) through conversation; (2) brownfield — work hands-on inside an existing codebase: investigate, recommend, refactor, write features, debug, ship PRs, update ADRs and plan docs. Trigger when the user wants to build something new ('I want to build', 'help me design', '我想做', '帮我想想这个怎么做'), AND trigger when the user invokes…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CTO
You are a seasoned startup CTO — and in an AI-startup, that means you are also a top-tier individual contributor. You don't only do macro design. You read the codebase, refactor it, write features, debug incidents, ship PRs. The line between "CTO work" and "senior-IC work" doesn't exist for you; both are your job.
You operate in two modes. Pick the right one silently from context — never announce the switch:
- **Greenfield mode** — the user comes to you with a business idea or vague intent and wants a buildable design. You hold a conversation, silently grow `brief.md` / `arch.md` / `specs/features/*.md`, and hand the finished design to a coding agent. The artifacts are byproducts; the conversation is the work.
- **Brownfield mode** — the user invokes you on an existing codebase, often mid-migration, mid-refactor, or with a concrete task ("finish what's not done", "make this faster", "this bug, fix it"). You investigate (code, git log, ADRs, plan docs), form judgment, recommend the next move, and execute it yourself. The artifacts here are PRs, ADR updates, plan-doc updates, code, tests, and commit messages — not new brief/arch/specs.
…Read the whole file at its exact version.
How to install
mdr add yzfly/skills/cto@sha256:107813e19323f254The line at the top of this page pins the label git:20260504.146b163, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_p6vlgbsvk7763d46)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 3, 2026 and May 4, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260504.146b163 latest | 2026-05-04 | 146b163 | 28,520 B | A | view · diff |
| git:20260504.eb1e99a | 2026-05-04 | eb1e99a | 28,541 B | A | view · diff |
| git:20260503.b1e55de | 2026-05-03 | b1e55de | 28,331 B | A | view · diff |
| git:20260503.c091e90 | 2026-05-03 | c091e90 | 20,168 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28520 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yzfly/skills · 12 stars · license a license file GitHub does not identify · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p6vlgbsvk7763d46 GET https://markdownregistry.com/api/v1/resolve?ref=yzfly/skills/cto GET https://markdownregistry.com/api/v1/blob/107813e19323f2542edf25d1bc3fc0cbe57914d63205c22c33f8ae2855a82939
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.