fable-validate-fableplan-loop SKILL.md skillA
fable-validate-fableplan-loop 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-loop@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-loop/SKILL.md- Versions recorded
- 13
- Latest version
- git:20261006.61bf5e6, committed Oct 6, 2026
- First version recorded
- Aug 28, 2026
- Size
- 3,236 bytes
- Repository stars
- 50
- License
- MIT
Use when the user asks to validate a GitHub issue with Fable 5.1, always plan it with Fable 5.1, and autonomously drive it to a reviewed PR in one shot — "fable-validate-fableplan-loop", "fable validate, fable plan, and work on #N", "fully automate #N with fable validation and an unconditional fable plan". Runs fable-validate, auto-applies its update-issue edits when the verdict calls for it, has fableplan produce and post a Fable 5.1 implementation plan for EVERY issue…
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-loop Chain fable-validate → (conditional) update issue → fableplan → work-on-issue-loop into one autonomous run. This is **fable-validate-loop with the score gate removed**: fableplan **always runs**, whatever the validated complexity score, and there is no "skip when the score is below 75" rule. When skipping the plan for lower-band issues is fine, use `fable-validate-loop`. **Do not skip or reorder the chain.** Validation gates planning, and the plan gates implementation. This variant has 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 6** with these changes: **Step 1 (fable-validate)** applies unchanged. **Step 2 (scope gate)** applies unchanged, with fable-validate-loop step 2's STOP table. **Step 3 (update-issue edits):** apply them per fable-validate step 5 / validate-issue step 11; the stacked `Validated with LLM: …` attribution line uses the harness suffix `fable-validate-fableplan-loop`. …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/fable-validate-fableplan-loop@sha256:80b4b4a7d0c4170bThe 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_nstpzei45bxx4rqj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 13 versions of this file, between Aug 28, 2026 and Oct 6, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.61bf5e6 latest | 2026-10-06 | 61bf5e6 | 3,236 B | A | view · diff |
| git:20261006.4c6da76 | 2026-10-06 | 4c6da76 | 3,184 B | A | view · diff |
| git:20261004.47b4d96 | 2026-10-04 | 47b4d96 | 3,846 B | A | view · diff |
| git:20261002.6c4566e | 2026-10-02 | 6c4566e | 3,846 B | A | view · diff |
| git:20261002.51ca084 | 2026-10-02 | 51ca084 | 3,698 B | A | view · diff |
| git:20260929.665e60a | 2026-09-29 | 665e60a | 3,830 B | A | view · diff |
| git:20260927.55c2280 | 2026-09-27 | 55c2280 | 3,825 B | A | view · diff |
| git:20260923.07468a2 | 2026-09-23 | 07468a2 | 3,817 B | A | view · diff |
| git:20260923.66d4f63 | 2026-09-23 | 66d4f63 | 5,208 B | A | view · diff |
| git:20260903.6fdbab1 | 2026-09-03 | 6fdbab1 | 5,041 B | A | view · diff |
| git:20260903.9f8defc | 2026-09-03 | 9f8defc | 4,967 B | A | view · diff |
| git:20260901.6c08e4b | 2026-09-01 | 6c08e4b | 4,657 B | A | view · diff |
| git:20260828.1a9574f | 2026-08-28 | 1a9574f | 4,647 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 (3236 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_nstpzei45bxx4rqj GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/fable-validate-fableplan-loop GET https://markdownregistry.com/api/v1/blob/80b4b4a7d0c4170b6f6ee09408553ea9543c1c98d4d5b4d2924c1a9df0cbcbf5
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.