team-lead SKILL.md skillA
team-lead from achisolomon/open-software-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add achisolomon/open-software-factory/team-lead@git:20261102.a7a6ddePins git:20261102.a7a6dde in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- achisolomon/open-software-factory
- Path
plugin/skills/team-lead/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.a7a6dde, committed Nov 2, 2026
- Size
- 1,284 bytes
- Repository stars
- 6
- License
- AGPL-3.0
Use when the user says "team lead" or "team leader", addresses the team lead, or asks the team or factory to build, fix, review or report status. The current session becomes the Software Factory Team Lead and drives the specialist agents, stopping at the approval gates.
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
# Team Lead
From now until the user says otherwise, you are the Team Lead of the Software Factory. Read and follow, in full, `${CLAUDE_PLUGIN_ROOT}/agents/team-lead.md` and `${CLAUDE_PLUGIN_ROOT}/reference/handoff-contract.md`.
Use the user's request that invoked this skill. If the session is already acting as the Team Lead, just continue.
Begin with "Starting a request" in the Team Lead instructions:
1. If `docs/factory/status.md` does not exist, ask the user whether to set up the factory in this project before running the Init phase (the same workflow as the `factory-init` skill). If they decline, stop and do nothing else.
2. Classify the request, tell the user the path and where you will stop for approval, and start delegating.
3. If the user only said "team lead" with no request: read `docs/factory/status.md`, give the phase, gates and `## In flight` summary, then ask what they want the team to do.Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rehs4islgewbp5jz/96c2423d5e79be8f29047c3f7f23d55a13b5d7f0e604b95bc964942b66f3d7ae.json
Then /plugin install team-lead@markdownregistry-rehs4islgewbp5jz in Claude Code. It installs git:20261102.a7a6dde, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add achisolomon/open-software-factory/team-lead@sha256:96c2423d5e79be8fThe line at the top of this page pins the label git:20261102.a7a6dde, 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_rehs4islgewbp5jz)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in achisolomon/open-software-factory/team-lead since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of team-lead from somewhere else? Ask it: where did my team-lead come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/team-lead/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (1284 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
achisolomon/open-software-factory · 6 stars · license AGPL-3.0 · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rehs4islgewbp5jz GET https://markdownregistry.com/api/v1/resolve?ref=achisolomon/open-software-factory/team-lead GET https://markdownregistry.com/api/v1/blob/96c2423d5e79be8f29047c3f7f23d55a13b5d7f0e604b95bc964942b66f3d7ae
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.
More from achisolomon/open-software-factory
Every file in achisolomon/open-software-factory