[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77H4TWVX9DFEENP34R4MPCD":3,"skill-same:01M77H4TWVX9DFEENP34R4MPCD":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M77H4TWVX9DFEENP34R4MPCD","refresh-readme",null,"One repeatable pass over README.md — the front door — that keeps ONLY the most important points current and honestly framed. Runs the freshness auditor (tools\u002Freadme_freshness_audit.py), turns each FAIL into a required edit and each WARN into a judgment call, applies the three front-page laws (SOTA-vs-us-never-naive, 6th-grade\u002FFeynman-but-accurate, wide-audience), re-stamps the readme-verified marker, and commits ONLY README.md (+ the tool) by explicit path. Use after a release \u002F version bump, after a headline number changes, when a link dies, or on a \u002Floop cadence.","anthony-chaudhary\u002Ffak","anthony-chaudhary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F18080164?v=4","01M77GSKCAEKV3JS07J40B94DY","Anthony Chaudhary","01M77GSKD26Z7F4FQQD4VA30VX",48,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefresh-readme\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: refresh-readme\ndescription: One repeatable pass over README.md — the front door — that keeps ONLY the most important points current and honestly framed. Runs the freshness auditor (tools\u002Freadme_freshness_audit.py), turns each FAIL into a required edit and each WARN into a judgment call, applies the three front-page laws (SOTA-vs-us-never-naive, 6th-grade\u002FFeynman-but-accurate, wide-audience), re-stamps the readme-verified marker, and commits ONLY README.md (+ the tool) by explicit path. Use after a release \u002F version bump, after a headline number changes, when a link dies, or on a \u002Floop cadence.\nmetadata:\n  generated-by: fak project-assets sync\n  canonical: ..\u002F..\u002F..\u002F.claude\u002Fskills\u002Frefresh-readme\u002FSKILL.md\n---\n\n# refresh-readme — keep the front door correct, honest, and small\n\n> **What this does.** `README.md` is the one surface read cold by everyone —\n> adopter, reviewer, skeptic — and the one most likely to rot: a link dies, a\n> version pin lags `VERSION`, a headline number drifts from\n> `BENCHMARK-AUTHORITY.md`, a \"we beat naive\" claim creeps back into the lead.\n> Every other claim surface here has a checking layer (a memory-recall audit for\n> memories, a closure audit for issue closes, `BENCHMARK-AUTHORITY` for numbers).\n> This is the README's. It makes \"keep only the most important points on the\n> front page, framed honestly\" a **repeatable pass**, not a one-time edit that\n> decays the moment the person who did it moves on.\n\nThe shape: **run the auditor → fix every FAIL → weigh every WARN → apply the\nthree laws → re-stamp → commit ONLY the README lane.**\n\n---\n\n## The three front-page laws (the durable policy this pass enforces)\n\nThese are not style preferences — they are standing rules for the front page, and\nthe auditor checks each one. Internalize them; the README is graded against them\nevery pass.\n\n1. **SOTA-vs-us, never naive.** Every headline number on the front page compares\n   `fak` against the *best already-shipped* alternative, not a strawman. \"~4×\n   vs a tuned warm-cache stack\" leads; \"~60× vs naive\" does not — beating naive\n   is easy, and leading with it invites the \"you're fighting a strawman\"\n   dismissal. A naive number may appear as an honest aside that *says* it's not\n   the headline; it may never be the bolded lead. → auditor `naive_baseline` FAIL.\n\n2. **6th-grade \u002F Feynman voice, but still accurate.** The front page is the\n   audience-widening surface; the deep-dive links are where the jargon lives.\n   On the first screen, lead with the plain-English idea, then name the term in\n   parens — \"a scratchpad of the work-so-far (the *KV cache*)\", not \"the KV\n   cache\". Explain by concrete example, the Feynman move, before reaching for the\n   abstraction. **Accuracy is not negotiable** — simplify the words, never the\n   claim. Every acronym gets a parenthetical on first use. → auditor\n   `jargon_density` ADVISORY.\n\n3. **Wide-audience appeal.** The first screen gives each reader a foothold: the\n   skeptic (what's real \u002F what's not), the security lead (the lock, not the\n   screener), the perf engineer (the reuse win + its fences), the casual reader\n   (the 2-minute no-key demo). If a section serves only one audience, ask whether\n   it belongs on the front page or behind a \"Go deeper\" link.\n\nAnd the size law that wraps all three: **the front page holds only the most\nimportant points.** Before adding anything, ask — *would this earn its place if\nthe page could hold only ten things?* If not, it belongs in a linked topic doc,\nnot on the front page. Detail flows OUT to `docs\u002F` and the \"Go deeper\" table; the\nfront page stays small.\n\n**The size law now has teeth (it used to be aspirational).** Five of the six\nsubstance checks reward *adding* an affordance — put `fak guard` up top, add a\nspeed number, add a hero result, add a persona router. Optimized to those alone,\nthe page only ever grows: the git log shows it halved on 2026-07-01 and\nimmediately regrew, one well-meaning \"surface X on the front page\" commit at a\ntime. `front_page_focus` is the counterweight — a line budget, a section-count\nbudget, and a **single-lead** rule (the one-binary\u002Fsyscall pitch stated *once* in\nthe preamble, not restated three times before the reader reaches a section). It\nfeeds the composite score and the `readme_debt` gate, so a bloated page can no\nlonger score an A. The two forces now both live in the tool; concision is checked,\nnot just hoped for.\n\nThe three anti-regrowth rules this pass enforces:\n\n1. **Retire before you add.** The page is at its section budget by design. To add\n   a section, *fold or cut* one first — do not bump `FRONT_PAGE_SECTION_BUDGET` to\n   make room. Bumping a budget to silence the warning is the failure mode; bump it\n   only when the page has genuinely, durably earned the slot, and say why in the\n   commit.\n2. **One lead, not three.** The pitch is derived from\n   [`docs\u002Fadoption\u002Fpitch-ladder.md`](..\u002F..\u002F..\u002Fdocs\u002Fadoption\u002Fpitch-ladder.md) rung 1\n   and appears *once* above the first `## `. A second \"and also, fak is a binary\n   you put in front of your agent\" paragraph is the confusion `single_lead`\n   catches — collapse it into the one lead.\n3. **Detail flows OUT, never back IN.** The overflow sink is\n   [`docs\u002FREADME-legacy.md`](..\u002F..\u002F..\u002Fdocs\u002FREADME-legacy.md). Narrower-audience or\n   deep-dive material moves there and earns a link; it does not migrate back onto\n   the front page. If a section keeps wanting to come home, that is a signal to\n   write a topic doc, not to re-inline it.\n\n---\n\n## Step 1 — Run the auditor (it builds your work-list)\n\nFrom the repo root:\n\n```bash\npython tools\u002Freadme_freshness_audit.py --json > readme-before.json\npython tools\u002Freadme_freshness_audit.py            # human rendering of the same evidence\n```\n\n`readme-before.json` is the mandatory first artifact. Quote every binding `FAIL` check name and\nits evidence before editing. Retire all binding FAIL rows before advisory prose polish; an\nadvisory unglossed term such as `KV cache` must not displace a red `guard_prominence` check. The\ncurrent README product defect belongs in its dedicated README issue, not in this skill-only\nadjudication.\n\nIt checks, and exits non-zero on any **FAIL**:\n\n| check | fires on | severity |\n|---|---|---|\n| `links` | a local Markdown link whose target is missing on disk | **FAIL** |\n| `version_pins` | a `vX.Y.Z` string behind the `VERSION` file | **FAIL** |\n| `naive_baseline` | a bolded headline that LEADS with a \"naive\" baseline (law 1) | **FAIL** |\n| `headline_authority` | a bolded multiplier not mirrored in `BENCHMARK-AUTHORITY` | WARN |\n| `freshness_stamp` | the `readme-verified` marker absent or older than 14d | WARN |\n| `jargon_density` | first-screen expert terms with no plain gloss nearby (law 2) | advisory |\n| `front_page_focus` | the page busts the line\u002Fsection budget or restates the lead ≥3× (the size law) | debt |\n\n**FAIL = a required edit. WARN = a judgment call. ADVISORY = a nudge.** Voice\n(jargon) is never a hard gate — plain-language is writing judgment, not a\nmechanical rule.\n\n## Step 2 — Fix every FAIL\n\nWork in the exact binding order quoted from `readme-before.json`; do not start WARN\u002FADVISORY\npolish or the separately issue-tracked README product fix while any FAIL remains.\n\n- **dead link** — the target moved or was deleted. Repoint it to the current\n  path, or drop the link if the doc is gone. (Don't invent a path; verify it\n  exists.)\n- **stale version pin** — bump it to match `VERSION`. A deliberate forward range\n  (`v0.31.x`) on the current minor is fine and passes.\n- **naive-lead headline (law 1)** — invert it. Put the SOTA comparison in the\n  bold lead; demote the naive number to a plain-prose aside that names itself as\n  not-the-headline, or cut it.\n\n## Step 3 — Weigh every WARN, apply laws 2 & 3\n\nEnter this step only after all binding FAIL rows are green.\n\n- **headline_authority WARN** — a front-page number isn't traceable to\n  `BENCHMARK-AUTHORITY`. Either it's stale (fix it to the authority figure) or\n  it's a number that shouldn't be on the front page at all (an untraced claim).\n  Reconcile against the authority doc; never invent a number to match.\n- **jargon ADVISORY** — for each flagged first-screen term, add a one-clause\n  plain gloss the first time it appears (law 2). Don't touch the deep-dive links.\n- **read the first screen as each audience** (law 3) — does the skeptic, the\n  security lead, the perf engineer, and the casual reader each get a foothold in\n  the first screen? If a point serves none of them, it's a candidate to move\n  behind a link (the size law).\n\n## Step 4 — Re-stamp the freshness marker\n\nAfter the page is correct, update the stamp near the top of `README.md` to\n**today's date and the current `VERSION`**:\n\n```\n\u003C!-- readme-verified: YYYY-MM-DD vs VERSION X.Y.Z + BENCHMARK-AUTHORITY · process: tools\u002Freadme_freshness_audit.py + \u002Frefresh-readme -->\n```\n\nThis is the freshness contract: it's how the next reader (and the next audit)\nknows the page was checked against reality, and when. Re-run the auditor — it\nshould now be **green (exit 0)**.\n\n## Step 5 — Commit ONLY the README lane, by explicit path\n\nOn a shared tree, HEAD can move under you and peers may have dirty paths. The\ncommit discipline:\n\n- **Stage by explicit path, never `git add -A`** — commit *your* README, not a\n  peer's half-written code:\n  ```bash\n  fak sync reconcile --apply\n  fak commit --path README.md -F \u003Cmsgfile> [--push]\n  fak sync push\n  ```\n- **Doc-only diff → `docs(readme): …` subject**, NOT `fix(`\u002F`feat(`. A\n  code-effect prefix on a docs-only diff overclaims — keep the prefix honest to\n  what changed.\n- **On Windows, pass the message via a file** (`-F`), not a here-string — native\n  exe arg passing mangles multi-line quotes.\n- **If a peer's `MERGE_HEAD` is set** (`cannot do a partial commit during a\n  merge`): **wait for it to clear** — don't abort or work around it. Markdown\n  self-heals; re-try the pathspec commit once `MERGE_HEAD` is gone.\n- **Stay on the trunk (`main`)** — never branch or worktree to dodge a\n  dirty\u002Fdiverged tree. Push promptly via `fak sync push` (or `--push`).\n\nIf a release just happened, this pass typically only needs Step 4 (re-stamp to\nthe new VERSION) — the auditor catches the bump immediately.\n\n---\n\n## This is already a durable loop — you don't have to remember to run it\n\nThe front page does **not** rely on someone thinking to check it. The checking\nhalf runs on a fixed cadence, and this skill is the acting half it hands work to:\n\n1. **The auditor is a registered gardening loop.** `readme-freshness` is an\n   `enabled` entry in [`tools\u002Fcontrol_pane.loops.json`](..\u002F..\u002F..\u002Ftools\u002Fcontrol_pane.loops.json),\n   wired to `python tools\u002Freadme_freshness_audit.py --json`. It sits alongside the\n   other front-door checking layers (`memory-recall-audit`, `docs-scorecard`, …).\n2. **It runs daily, unattended.** [`.github\u002Fworkflows\u002Fgarden.yml`](..\u002F..\u002F..\u002F.github\u002Fworkflows\u002Fgarden.yml)\n   runs `fak garden` on a daily `cron` (06:23 UTC), and `fak garden` folds the\n   fleet **loop-audit** — which runs every enabled gardening loop once, this one\n   included. So the README is re-checked against the filesystem, `VERSION`, and\n   `BENCHMARK-AUTHORITY` every day, whether or not anyone asked.\n3. **The loop itself is watched.** The `gardening-loops-audit` meta-loop flags\n   `readme-freshness` as BROKEN if its status command ever stops running — the\n   loop can't silently rot into a no-op.\n4. **This skill is the acting half.** When the daily audit returns `ACTION`\n   (`ok:false` — a FAIL), that verdict names `\u002Frefresh-readme` as the runbook.\n   You (or a supervisor turn) run the pass below; the loop closes.\n\nSo \"a durable README loop that routinely gardens the front page\" already exists\nend to end: **daily audit → ACTION verdict → this skill → commit the README lane.**\nThe section below is what you do when the loop hands you an ACTION (or when one of\nthe triggers fires early).\n\n## When to run this\n\n- After a `\u002Frelease` or any `VERSION` bump (the stamp + any pin go stale at once).\n- When a headline number changes in `BENCHMARK-AUTHORITY`.\n- When a doc the README links to moves or is renamed.\n- When the daily `readme-freshness` loop (above) returns `ACTION`, or on a manual\n  `\u002Floop` cadence to garden the front page ahead of the daily tick.\n\nThe auditor is read-only; this skill's only writes are `README.md` and re-running\nthe tool. It never edits a deep-dive doc — the front page is the only surface in\nscope.\n","# refresh-readme — keep the front door correct, honest, and small\n\n> **What this does.** `README.md` is the one surface read cold by everyone —\n> adopter, reviewer, skeptic — and the one most likely to rot: a link dies, a\n> version pin lags `VERSION`, a headline number drifts from\n> `BENCHMARK-AUTHORITY.md`, a \"we beat naive\" claim creeps back into the lead.\n> Every other claim surface here has a checking layer (a memory-recall audit for\n> memories, a closure audit for issue closes, `BENCHMARK-AUTHORITY` for numbers).\n> This is the README's. It makes \"keep only the most important points on the\n> front page, framed honestly\" a **repeatable pass**, not a one-time edit that\n> decays the moment the person who did it moves on.\n\nThe shape: **run the auditor → fix every FAIL → weigh every WARN → apply the\nthree laws → re-stamp → commit ONLY the README lane.**\n\n---\n\n## The three front-page laws (the durable policy this pass enforces)\n\nThese are not style preferences — they are standing rules for the front page, and\nthe auditor checks each one. Internalize them; the README is graded against them\nevery pass.\n\n1. **SOTA-vs-us, never naive.** Every headline number on the front page compares\n   `fak` against the *best already-shipped* alternative, not a strawman. \"~4×\n   vs a tuned warm-cache stack\" leads; \"~60× vs naive\" does not — beating naive\n   is easy, and leading with it invites the \"you're fighting a strawman\"\n   dismissal. A naive number may appear as an honest aside that *says* it's not\n   the headline; it may never be the bolded lead. → auditor `naive_baseline` FAIL.\n\n2. **6th-grade \u002F Feynman voice, but still accurate.** The front page is the\n   audience-widening surface; the deep-dive links are where the jargon lives.\n   On the first screen, lead with the plain-English idea, then name the term in\n   parens — \"a scratchpad of the work-so-far (the *KV cache*)\", not \"the KV\n   cache\". Explain by concrete example, the Feynman move, before reaching for the\n   abstraction. **Accuracy is not negotiable** — simplify the words, never the\n   claim. Every acronym gets a parenthetical on first use. → auditor\n   `jargon_density` ADVISORY.\n\n3. **Wide-audience appeal.** The first screen gives each reader a foothold: the\n   skeptic (what's real \u002F what's not), the security lead (the lock, not the\n   screener), the perf engineer (the reuse win + its fences), the casual reader\n   (the 2-minute no-key demo). If a section serves only one audience, ask whether\n   it belongs on the front page or behind a \"Go deeper\" link.\n\nAnd the size law that wraps all three: **the front page holds only the most\nimportant points.** Before adding anything, ask — *would this earn its place if\nthe page could hold only ten things?* If not, it belongs in a linked topic doc,\nnot on the front page. Detail flows OUT to `docs\u002F` and the \"Go deeper\" table; the\nfront page stays small.\n\n**The size law now has teeth (it used to be aspirational).** Five of the six\nsubstance checks reward *adding* an affordance — put `fak guard` up top, add a\nspeed number, add a hero result, add a persona router. Optimized to those alone,\nthe page only ever grows: the git log shows it halved on 2026-07-01 and\nimmediately regrew, one well-meaning \"surface X on the front page\" commit at a\ntime. `front_page_focus` is the counterweight — a line budget, a section-count\nbudget, and a **single-lead** rule (the one-binary\u002Fsyscall pitch stated *once* in\nthe preamble, not restated three times before the reader reaches a section). It\nfeeds the composite score and the `readme_debt` gate, so a bloated page can no\nlonger score an A. The two forces now both live in the tool; concision is checked,\nnot just hoped for.\n\nThe three anti-regrowth rules this pass enforces:\n\n1. **Retire before you add.** The page is at its section budget by design. To add\n   a section, *fold or cut* one first — do not bump `FRONT_PAGE_SECTION_BUDGET` to\n   make room. Bumping a budget to silence the warning is the failure mode; bump it\n   only when the page has genuinely, durably earned the slot, and say why in the\n   commit.\n2. **One lead, not three.** The pitch is derived from\n   [`docs\u002Fadoption\u002Fpitch-ladder.md`](..\u002F..\u002F..\u002Fdocs\u002Fadoption\u002Fpitch-ladder.md) rung 1\n   and appears *once* above the first `## `. A second \"and also, fak is a binary\n   you put in front of your agent\" paragraph is the confusion `single_lead`\n   catches — collapse it into the one lead.\n3. **Detail flows OUT, never back IN.** The overflow sink is\n   [`docs\u002FREADME-legacy.md`](..\u002F..\u002F..\u002Fdocs\u002FREADME-legacy.md). Narrower-audience or\n   deep-dive material moves there and earns a link; it does not migrate back onto\n   the front page. If a section keeps wanting to come home, that is a signal to\n   write a topic doc, not to re-inline it.\n\n---\n\n## Step 1 — Run the auditor (it builds your work-list)\n\nFrom the repo root:\n\n```bash\npython tools\u002Freadme_freshness_audit.py --json > readme-before.json\npython tools\u002Freadme_freshness_audit.py            # human rendering of the same evidence\n```\n\n`readme-before.json` is the mandatory first artifact. Quote every binding `FAIL` check name and\nits evidence before editing. Retire all binding FAIL rows before advisory prose polish; an\nadvisory unglossed term such as `KV cache` must not displace a red `guard_prominence` check. The\ncurrent README product defect belongs in its dedicated README issue, not in this skill-only\nadjudication.\n\nIt checks, and exits non-zero on any **FAIL**:\n\n| check | fires on | severity |\n|---|---|---|\n| `links` | a local Markdown link whose target is missing on disk | **FAIL** |\n| `version_pins` | a `vX.Y.Z` string behind the `VERSION` file | **FAIL** |\n| `naive_baseline` | a bolded headline that LEADS with a \"naive\" baseline (law 1) | **FAIL** |\n| `headline_authority` | a bolded multiplier not mirrored in `BENCHMARK-AUTHORITY` | WARN |\n| `freshness_stamp` | the `readme-verified` marker absent or older than 14d | WARN |\n| `jargon_density` | first-screen expert terms with no plain gloss nearby (law 2) | advisory |\n| `front_page_focus` | the page busts the line\u002Fsection budget or restates the lead ≥3× (the size law) | debt |\n\n**FAIL = a required edit. WARN = a judgment call. ADVISORY = a nudge.** Voice\n(jargon) is never a hard gate — plain-language is writing judgment, not a\nmechanical rule.\n\n## Step 2 — Fix every FAIL\n\nWork in the exact binding order quoted from `readme-before.json`; do not start WARN\u002FADVISORY\npolish or the separately issue-tracked README product fix while any FAIL remains.\n\n- **dead link** — the target moved or was deleted. Repoint it to the current\n  path, or drop the link if the doc is gone. (Don't invent a path; verify it\n  exists.)\n- **stale version pin** — bump it to match `VERSION`. A deliberate forward range\n  (`v0.31.x`) on the current minor is fine and passes.\n- **naive-lead headline (law 1)** — invert it. Put the SOTA comparison in the\n  bold lead; demote the naive number to a plain-prose aside that names itself as\n  not-the-headline, or cut it.\n\n## Step 3 — Weigh every WARN, apply laws 2 & 3\n\nEnter this step only after all binding FAIL rows are green.\n\n- **headline_authority WARN** — a front-page number isn't traceable to\n  `BENCHMARK-AUTHORITY`. Either it's stale (fix it to the authority figure) or\n  it's a number that shouldn't be on the front page at all (an untraced claim).\n  Reconcile against the authority doc; never invent a number to match.\n- **jargon ADVISORY** — for each flagged first-screen term, add a one-clause\n  plain gloss the first time it appears (law 2). Don't touch the deep-dive links.\n- **read the first screen as each audience** (law 3) — does the skeptic, the\n  security lead, the perf engineer, and the casual reader each get a foothold in\n  the first screen? If a point serves none of them, it's a candidate to move\n  behind a link (the size law).\n\n## Step 4 — Re-stamp the freshness marker\n\nAfter the page is correct, update the stamp near the top of `README.md` to\n**today's date and the current `VERSION`**:\n\n```\n\u003C!-- readme-verified: YYYY-MM-DD vs VERSION X.Y.Z + BENCHMARK-AUTHORITY · process: tools\u002Freadme_freshness_audit.py + \u002Frefresh-readme -->\n```\n\nThis is the freshness contract: it's how the next reader (and the next audit)\nknows the page was checked against reality, and when. Re-run the auditor — it\nshould now be **green (exit 0)**.\n\n## Step 5 — Commit ONLY the README lane, by explicit path\n\nOn a shared tree, HEAD can move under you and peers may have dirty paths. The\ncommit discipline:\n\n- **Stage by explicit path, never `git add -A`** — commit *your* README, not a\n  peer's half-written code:\n  ```bash\n  fak sync reconcile --apply\n  fak commit --path README.md -F \u003Cmsgfile> [--push]\n  fak sync push\n  ```\n- **Doc-only diff → `docs(readme): …` subject**, NOT `fix(`\u002F`feat(`. A\n  code-effect prefix on a docs-only diff overclaims — keep the prefix honest to\n  what changed.\n- **On Windows, pass the message via a file** (`-F`), not a here-string — native\n  exe arg passing mangles multi-line quotes.\n- **If a peer's `MERGE_HEAD` is set** (`cannot do a partial commit during a\n  merge`): **wait for it to clear** — don't abort or work around it. Markdown\n  self-heals; re-try the pathspec commit once `MERGE_HEAD` is gone.\n- **Stay on the trunk (`main`)** — never branch or worktree to dodge a\n  dirty\u002Fdiverged tree. Push promptly via `fak sync push` (or `--push`).\n\nIf a release just happened, this pass typically only needs Step 4 (re-stamp to\nthe new VERSION) — the auditor catches the bump immediately.\n\n---\n\n## This is already a durable loop — you don't have to remember to run it\n\nThe front page does **not** rely on someone thinking to check it. The checking\nhalf runs on a fixed cadence, and this skill is the acting half it hands work to:\n\n1. **The auditor is a registered gardening loop.** `readme-freshness` is an\n   `enabled` entry in [`tools\u002Fcontrol_pane.loops.json`](..\u002F..\u002F..\u002Ftools\u002Fcontrol_pane.loops.json),\n   wired to `python tools\u002Freadme_freshness_audit.py --json`. It sits alongside the\n   other front-door checking layers (`memory-recall-audit`, `docs-scorecard`, …).\n2. **It runs daily, unattended.** [`.github\u002Fworkflows\u002Fgarden.yml`](..\u002F..\u002F..\u002F.github\u002Fworkflows\u002Fgarden.yml)\n   runs `fak garden` on a daily `cron` (06:23 UTC), and `fak garden` folds the\n   fleet **loop-audit** — which runs every enabled gardening loop once, this one\n   included. So the README is re-checked against the filesystem, `VERSION`, and\n   `BENCHMARK-AUTHORITY` every day, whether or not anyone asked.\n3. **The loop itself is watched.** The `gardening-loops-audit` meta-loop flags\n   `readme-freshness` as BROKEN if its status command ever stops running — the\n   loop can't silently rot into a no-op.\n4. **This skill is the acting half.** When the daily audit returns `ACTION`\n   (`ok:false` — a FAIL), that verdict names `\u002Frefresh-readme` as the runbook.\n   You (or a supervisor turn) run the pass below; the loop closes.\n\nSo \"a durable README loop that routinely gardens the front page\" already exists\nend to end: **daily audit → ACTION verdict → this skill → commit the README lane.**\nThe section below is what you do when the loop hands you an ACTION (or when one of\nthe triggers fires early).\n\n## When to run this\n\n- After a `\u002Frelease` or any `VERSION` bump (the stamp + any pin go stale at once).\n- When a headline number changes in `BENCHMARK-AUTHORITY`.\n- When a doc the README links to moves or is renamed.\n- When the daily `readme-freshness` loop (above) returns `ACTION`, or on a manual\n  `\u002Floop` cadence to garden the front page ahead of the daily tick.\n\nThe auditor is read-only; this skill's only writes are `README.md` and re-running\nthe tool. It never edits a deep-dive doc — the front page is the only surface in\nscope.\n",{"name":5,"metadata":24,"description":7},{"canonical":25,"generated-by":26},"..\u002F..\u002F..\u002F.claude\u002Fskills\u002Frefresh-readme\u002FSKILL.md","fak project-assets sync","main","f565b7b7db63e79649f3a02c08108132a86c5d05",".agents\u002Fskills\u002Frefresh-readme",16,"https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak","https:\u002F\u002Fanthony-chaudhary.github.io\u002Ffak\u002Fshowcase.html","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary","https:\u002F\u002Flinkedin.com\u002Fin\u002Fanthonychaudhary","2026-11-15 03:06:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add anthony-chaudhary\u002Ffak --skill refresh-readme",{"tool":42,"command":43},"bunx","bunx skills add anthony-chaudhary\u002Ffak --skill refresh-readme",{"tool":45,"command":46},"pnpm","pnpm dlx skills add anthony-chaudhary\u002Ffak --skill refresh-readme","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefresh-readme\u002FSKILL.md",true,[],[51,58,67,74,81,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M78V4059KRP2T88YR6Z05MJQ","serve-receipt","On-demand research protocol + deterministic receipt for serving a Hugging Face model on a concrete GPU target — fan out research lanes (model facts\u002Ffiles, engine support matrix, serving recipes, KV\u002Fstate memory math), compute the tiered feasibility verdict with `fak serve-receipt` (never narrated math), and emit a witnessed launch receipt. Use when asked for an \"initial config\", \"serving receipt\", or \"how do I serve \u003Cmodel> on \u003CGPUs>\".","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fserve-receipt\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":62,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77HRGKQV2CJ2K6ZFN4YQ32K","caveman","Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman mode\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or invokes \u002Fcaveman. Also auto-triggers when token efficiency is requested.","MIT","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fsyspromptmmu\u002Fthird_party\u002Fcaveman\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fsyspromptmmu\u002Fthird_party\u002Fcaveman\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77HRAY3Y3BE7APN5PVJF7NV","quality-report","Score the repo quality and emit a report card.","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fctxplans\u002Ftestdata\u002Frepo\u002F.claude\u002Fskills\u002Fquality-report\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77HR9807KHAX13DG9PW2K2Q","ctx-overlay","Compact the context window and prune the memory store when a session grows too long.","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fctxplans\u002Ftestdata\u002Frepo\u002F.claude\u002Fskills\u002Fctx-overlay\u002FSKILL.md",[],[],{"skillNo":82,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77HR7XQ9X8F2CY9Z4F2ZEZ3","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fctxplanlint\u002Ftestdata\u002Frepo\u002F.claude\u002Fskills\u002Fquality-report\u002FSKILL.md",[],[],{"skillNo":87,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77HR5BVKCTR1WNJGRBSDNX7","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Ffak\u002Fblob\u002Fmain\u002Finternal\u002Fctxplanlint\u002Ftestdata\u002Frepo\u002F.claude\u002Fskills\u002Fctx-overlay\u002FSKILL.md",[],[]]