tlc-implement SKILL.md skillA
tlc-implement from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/tlc-implement@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(development)/tlc-implement/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.0, committed Oct 26, 2026
- First version recorded
- Sep 9, 2026
- Size
- 10,081 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
Implements work already planned - a plan.md from tlc-plan, or a small ticket - by freezing it into checks with proofs, building, and proving every check with a script and an independent Verifier before declaring done. Use when the user says "implement this plan", "build this ticket", "implement this spec", "write the checks", "verify work", or "tlc-implement". Do NOT use when nobody has decided what to build, or to plan a feature that needs one (that is tlc-plan).
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
# TLC Implement Freeze the obligations. Free the build. Prove it with someone who did not build it. ``` ┌────────┐ ┌───────┐ ┌────────┐ │ CHECKS │ → │ BUILD │ → │ VERIFY │ └────────┘ └───────┘ └────────┘ obligations yours always ``` The common failure of a coding agent is a requirement that never became an active obligation, followed by a completion claim. What works against it is a small, frozen, external obligation set and a verifier that is not the author, so the budget goes there and not into choreographing the model. How you build is yours. The input is an approved `.specs/features/<feature>/plan.md` from **tlc-plan** - approved means its `**Approved**: <date> - user: "<their words>"` line, which `validate_checks.py` requires - and it is the whole brief: you may have none of the conversation that produced it. A change under roughly three files with no one-way door needs no plan: write `checks.md` with an `## Intent` paragraph instead. Anything larger with no plan, or a plan with an open `blocks` question, goes back to **tlc-plan**. ## Rules These hold even if no reference file is read. Each one lives here; the references point back. …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/tlc-implement@sha256:8d16cc73f9d161d7The line at the top of this page pins the label v1.1.0, 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_hhluzezpjfy6g4ub)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 9, 2026 and Oct 26, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-26 | eec0410 | 10,081 B | A | view · diff |
| v1.0.0 | 2026-10-25 | 3be478b | 9,127 B | A | view · diff |
| v0.1.0 | 2026-09-09 | 3033393 | 17,408 B | A | view · diff |
| v0.1.0 | 2026-09-09 | 39b1b95 | 17,393 B | A | view · diff |
| v0.1.0 | 2026-09-09 | a319da7 | 17,409 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 (10081 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
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hhluzezpjfy6g4ub GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/tlc-implement GET https://markdownregistry.com/api/v1/blob/8d16cc73f9d161d7c94c1a7feff1d9c54056c7797733a75f9034775e4eb46130
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.