feature-radar-archive SKILL.md skillA
feature-radar-archive from runkids/feature-radar is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add runkids/feature-radar/feature-radar-archive@git:20260928.dd67ccfPins git:20260928.dd67ccf in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- runkids/feature-radar
- Path
skills/feature-radar-archive/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260928.dd67ccf, committed Sep 28, 2026
- First version recorded
- Mar 5, 2026
- Size
- 3,840 bytes
- Repository stars
- 14
- License
- MIT
Archive a completed, rejected, or covered feature into .feature-radar/archive/ with mandatory learning extraction. MUST use this skill whenever a feature reaches a terminal state — done, rejected, covered, deferred, or N/A — including casual mentions like "we shipped X". The skill extracts learnings, derives new opportunities, and updates refs. Use when the user reports a feature shipped or finished, decides against building one, defers or postpones one, or asks to close or archive an…
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
# Archive Feature
Move a feature to `.feature-radar/archive/` and run the mandatory extraction checklist.
## Deep Read
<HARD-GATE>
Read and follow `../feature-radar/references/DEEP-READ.md` — complete all 6 steps before proceeding.
</HARD-GATE>
## Behavioral Directives
<HARD-GATE>
Read and follow `../feature-radar/references/DIRECTIVES.md`.
</HARD-GATE>
## Workflow
1. **Identify the feature** — ask the user which feature to archive. Check `opportunities/` for an existing file to move.
2. **Determine status**:
- **Done** — fully implemented and working
- **Covered** — existing functionality handles the use case
- **Rejected** — decided against implementing
- **N/A** — not applicable to our architecture
- **Deferred** — valuable but postponed with rationale
3. **Create archive file** — write `.feature-radar/archive/{nn}-{slug}.md`
4. **Checkpoint — Review & Annotate** per `../feature-radar/references/WORKFLOW-PATTERNS.md`
5. **Run extraction checklist**:
### Extraction Checklist
<HARD-GATE>
Complete ALL 5 checks below. For each check, you MUST explicitly state the finding.
Do NOT proceed to step 6 until every check has a written response.
…Read the whole file at its exact version.
How to install
mdr add runkids/feature-radar/feature-radar-archive@sha256:dc449f41ee51e0faThe line at the top of this page pins the label git:20260928.dd67ccf, 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_j5pvp5lzuks7f7dw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 5, 2026 and Sep 28, 2026, about one every 52 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260928.dd67ccf latest | 2026-09-28 | dd67ccf | 3,840 B | A | view · diff |
| git:20260306.f4677d3 | 2026-03-06 | f4677d3 | 4,042 B | A | view · diff |
| git:20260306.f216672 | 2026-03-06 | f216672 | 4,014 B | A | view · diff |
| git:20260306.9fff822 | 2026-03-06 | 9fff822 | 3,687 B | A | view · diff |
| git:20260305.b242d21 | 2026-03-05 | b242d21 | 3,615 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 (3840 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
runkids/feature-radar · 14 stars · license MIT · pushed 2026-09-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j5pvp5lzuks7f7dw GET https://markdownregistry.com/api/v1/resolve?ref=runkids/feature-radar/feature-radar-archive GET https://markdownregistry.com/api/v1/blob/dc449f41ee51e0fad6e5c57f36c0073b637b4e5d6ba03ad45df0074548aee51f
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 runkids/feature-radar
Every file in runkids/feature-radar