fable-validate-fableplan SKILL.md skillA
fable-validate-fableplan from richkuo/rk-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add richkuo/rk-skills/fable-validate-fableplan@git:20261006.61bf5e6Pins git:20261006.61bf5e6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- richkuo/rk-skills
- Path
skills/fable-validate-fableplan/SKILL.md- Versions recorded
- 13
- Latest version
- git:20261006.61bf5e6, committed Oct 6, 2026
- First version recorded
- Aug 14, 2026
- Size
- 4,154 bytes
- Repository stars
- 50
- License
- MIT
Use when the user asks to validate a GitHub issue with Fable 5.1 and always plan it with Fable 5.1, stopping once the plan is posted — "fable-validate-fableplan", "fable validate and fable plan #N", "validate and plan #N with fable, don't build it". Runs fable-validate, auto-applies its update-issue edits when the verdict calls for it, then has fableplan produce and post a Fable 5.1 implementation plan for EVERY issue (no score gate), and stops at the posted plan — no worktree, no build, no…
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
# fable-validate-fableplan Chain fable-validate → (conditional) update issue → fableplan into one autonomous run, and stop there. The vetted plan is posted to the issue as a comment. **Nothing is built.** This is **fable-validate-fableplan-loop with the handoff to `work-on-issue-loop` dropped**. When the plan should be built and driven through review in the same run, use `fable-validate-fableplan-loop`. **Do not skip or reorder the chain.** Validation gates planning. There is no sanctioned skip: every step runs, and only the "wait for the user's reply" moments are replaced by the decision rules in the cited steps. ## Input Same as fable-validate-loop, including the optional `targetBranch`. ## Steps Follow **fable-validate-loop steps 1 through 4** with the changes below, then run this skill's step 5 in place of fable-validate-loop's steps 5 and 6: **Step 1 (fable-validate):** also keep the verdict block and the validation report in the scratchpad; step 4 passes them to the planner. **Step 2 (scope gate):** fable-validate-loop step 2's STOP table applies unchanged. An incomplete validation is never approval to plan. …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/fable-validate-fableplan@sha256:d40b867d79d7c071The line at the top of this page pins the label git:20261006.61bf5e6, 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_2s2sepkwluhpiy4c)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 13 versions of this file, between Aug 14, 2026 and Oct 6, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.61bf5e6 latest | 2026-10-06 | 61bf5e6 | 4,154 B | A | view · diff |
| git:20261006.4c6da76 | 2026-10-06 | 4c6da76 | 4,102 B | A | view · diff |
| git:20261002.6c4566e | 2026-10-02 | 6c4566e | 5,171 B | A | view · diff |
| git:20261002.51ca084 | 2026-10-02 | 51ca084 | 5,150 B | A | view · diff |
| git:20260929.665e60a | 2026-09-29 | 665e60a | 5,434 B | A | view · diff |
| git:20260928.2014375 | 2026-09-28 | 2014375 | 5,429 B | A | view · diff |
| git:20260927.55c2280 | 2026-09-27 | 55c2280 | 5,354 B | A | view · diff |
| git:20260923.07468a2 | 2026-09-23 | 07468a2 | 5,346 B | A | view · diff |
| git:20260923.66d4f63 | 2026-09-23 | 66d4f63 | 6,384 B | A | view · diff |
| git:20260903.6fdbab1 | 2026-09-03 | 6fdbab1 | 6,209 B | A | view · diff |
| git:20260901.6c08e4b | 2026-09-01 | 6c08e4b | 6,135 B | A | view · diff |
| git:20260817.1ff4731 | 2026-08-17 | 1ff4731 | 6,125 B | A | view · diff |
| git:20260814.b683395 | 2026-08-14 | b683395 | 8,002 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 (4154 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
richkuo/rk-skills · 50 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2s2sepkwluhpiy4c GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/fable-validate-fableplan GET https://markdownregistry.com/api/v1/blob/d40b867d79d7c0715c408c94f971d5c286e58daa714a0b0ad28d958f7e7263aa
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.