[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77ZDFWKK9178AQX1FSYBFH8":3,"skill-same:01M77ZDFWKK9178AQX1FSYBFH8":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77ZDFWKK9178AQX1FSYBFH8","okforge-maintain",null,"Maintain the Open Knowledge Format (OKF) knowledge bundle under .okf\u002F. Use whenever the user wants to update, refresh, or regenerate OKF docs, set up an OKF bundle, check OKF conformance, or when source code that the bundle documents (config schemas, web API routes, CLI commands, runtime subsystems, example crews, ADRs) has changed and the docs need to catch up. Three modes: scaffold (create the bundle), refresh (regenerate a folder's docs from current source), and check (conformance and dead-link lint). Prefer this skill over hand-editing .okf\u002F so the format, the folder\u003C->source mapping, and link integrity stay consistent.","jeromeetienne\u002Fvoicebox_cli","jeromeetienne","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252962?v=4","01M75JP4GNBAWHWK7J2DEKE33H","Jerome Etienne","01M77ZDDPA9BX74CTXQ0WXCA01",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fokforge-maintain\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: okforge-maintain\ndescription: >-\n  Maintain the Open Knowledge Format (OKF) knowledge bundle under .okf\u002F. Use\n  whenever the user wants to update, refresh, or regenerate OKF docs, set up an\n  OKF bundle, check OKF conformance, or when source code that the bundle\n  documents (config schemas, web API routes, CLI commands, runtime subsystems,\n  example crews, ADRs) has changed and the docs need to catch up. Three modes:\n  scaffold (create the bundle), refresh (regenerate a folder's docs from current\n  source), and check (conformance and dead-link lint). Prefer this skill over\n  hand-editing .okf\u002F so the format, the folder\u003C->source mapping, and link\n  integrity stay consistent.\n---\n\n# Open Knowledge Format (OKF) maintenance\n\nOKF is an open, human- and agent-friendly format for knowledge — the metadata\nand curated insight that surrounds a system. This repo's bundle lives at `.okf\u002F`.\nSpec: https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fknowledge-catalog\u002Fblob\u002Fmain\u002Fokf\u002FSPEC.md\n\nThe bundle is **derived** from source. Each folder is generated from specific\nfiles; when those files change, the folder's docs drift. This skill keeps three\nthings consistent so you can focus on accurate prose: the OKF format, the\nfolder\u003C->source mapping, and link integrity.\n\nA bundled CLI owns the mechanics; you own the prose. Run it with `npx` from the\nproject root (Node >= 20.12):\n\n```bash\nnpx okforge \u003Ccommand>          # map | folders | sources \u003Cfolder> | stale | check | nudge\n```\n\n## Pick the mode from what the user asked\n\n- **\"refresh okf\", \"update the OKF docs for X\", \"the API changed, update okf\"**\n  → Refresh mode (the common case).\n- **\"set up okf\", \"create an OKF bundle\", bundle missing** → Scaffold mode.\n- **\"check okf\", \"is the bundle conformant\", \"any dead links\"** → Check mode.\n\n## The folder \u003C-> source mapping\n\nThe mapping is **per-repository data**, declared in `.okforge.config.json` at the\nproject root. okforge ships with none of it. The file shape is:\n\n```json\n{\n  \"folders\": {\n    \"runtime_concepts\": [\"packages\u002Ffoo\u002Fsrc\u002Fmodel\u002F\", \"packages\u002Ffoo\u002Fsrc\u002Fevent\u002F\"],\n    \"config_formats\": [\"packages\u002Ffoo\u002Fdata\u002Fschemas\u002Fthing.schema.json\"]\n  }\n}\n```\n\nEach key is an OKF concept folder; each value is the list of source path prefixes\nthat folder is derived from. `npx okforge map` prints the resolved mapping;\n`npx okforge sources \u003Cfolder>` prints one folder's source paths;\n`npx okforge folders` lists the declared folders. Never hardcode the mapping in\ndocs — read it from the config so there is one source of truth (the hook reads it\ntoo). When the codebase moves, edit `.okforge.config.json`.\n\n## Refresh mode\n\n1. Determine which folder(s) to refresh. If the user named one, use it. If they\n   said \"whatever changed\", run `npx okforge stale` — it lists folders whose\n   source changed since HEAD without the folder being edited.\n2. For each folder, run `npx okforge sources \u003Cfolder>` and **READ those real\n   files**.\n3. Regenerate the affected concept docs from what you read, following the OKF\n   authoring rules below. Only rewrite docs whose underlying source actually\n   changed; leave correct docs untouched. Preserve existing filenames unless the\n   source they document was renamed or removed.\n4. If a concept's source was deleted, delete its doc and remove it from the\n   folder `index.md`. If a new source appeared, add a new concept doc and link\n   it from `index.md`.\n5. Update the folder `index.md`, and if folders were added\u002Fremoved update the\n   root `.okf\u002Findex.md`, the `.okforge.config.json` mapping, and prepend a dated\n   entry to `.okf\u002Flog.md`.\n6. Run `npx okforge check` and resolve every problem it reports before finishing.\n\n## Scaffold mode\n\nCreate `.okforge.config.json` at the project root with the folder\u003C->source\nmapping for this repository (ask the user or infer it from the layout). Then\ncreate `.okf\u002Findex.md` (the only file with frontmatter: `okf_version: \"0.1\"` and\n`type: Bundle Index`) and `.okf\u002Flog.md`. Create the folders from the mapping and\nrefresh each. Finish with `npx okforge check`.\n\n## Check mode\n\nRun `npx okforge check`. It verifies snake_case names, that every non-index `.md`\nhas a non-empty frontmatter `type`, that sub-folder `index.md` files carry no\nfrontmatter, and that bundle-relative `.md` links resolve. Report results; fix\nproblems if the user asked you to.\n\n## OKF authoring rules (follow exactly when writing docs)\n\n- **File names**: snake_case only. No kebab-case, no spaces.\n- **Concept docs**: every non-index `.md` starts with a YAML frontmatter block\n  delimited by `---` lines. Required: `type` (non-empty, e.g. `Config Format`,\n  `Concept`, `Data Model`, `API Endpoint`, `CLI Command`, `Crew`, `Package`).\n  Recommended: `title`, `description` (one sentence), `resource` (path\u002FURI of\n  the real underlying asset), `tags`, `timestamp` (ISO 8601 — set to today's\n  date on refresh).\n- **Body**: favor structural markdown — headings, lists, tables, fenced code —\n  over prose. Use conventional sections where they apply: `# Schema` (field\u002F\n  shape), `# Examples` (code), `# Citations` (sources).\n- **Index files** (reserved): `index.md` has NO frontmatter (except the root\n  bundle index). It lists the folder's concepts as bulleted markdown links with\n  one-line descriptions, optionally grouped under `#` headings.\n- **Links**: cross-link concepts with relative markdown paths from the doc, e.g.\n  `[job store](..\u002Fruntime_concepts\u002Fjob_store.md)` or `[sibling](.\u002Fsibling.md)`.\n  Never use bundle-root absolute paths (those beginning with `\u002F`, e.g.\n  `\u002Fruntime_concepts\u002Fjob_store.md`). Link to real repo source files (in\n  `# Citations`) with repo-relative paths from the doc, e.g.\n  `..\u002F..\u002Fpackages\u002Ffoo\u002Fsrc\u002Fmodel\u002Fjob_store.ts`.\n- **Grounding (critical)**: every claim must come from the real source you read.\n  Do not invent field names, routes, flags, states, or behavior. If uncertain,\n  omit. Quote real schema fields and real route paths.\n- **Style**: plain English, no slang, no abbreviations.\n\n## Companion hook\n\nA `Stop` hook (`npx okforge nudge`, registered in `.claude\u002Fsettings.json`) nudges\nat session end when mapped source changed but `.okf\u002F` was not updated. It reads the\nsame `.okforge.config.json` mapping via `npx okforge stale`, so editing the\nmapping updates both the skill and the nudge.\n","# Open Knowledge Format (OKF) maintenance\n\nOKF is an open, human- and agent-friendly format for knowledge — the metadata\nand curated insight that surrounds a system. This repo's bundle lives at `.okf\u002F`.\nSpec: https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fknowledge-catalog\u002Fblob\u002Fmain\u002Fokf\u002FSPEC.md\n\nThe bundle is **derived** from source. Each folder is generated from specific\nfiles; when those files change, the folder's docs drift. This skill keeps three\nthings consistent so you can focus on accurate prose: the OKF format, the\nfolder\u003C->source mapping, and link integrity.\n\nA bundled CLI owns the mechanics; you own the prose. Run it with `npx` from the\nproject root (Node >= 20.12):\n\n```bash\nnpx okforge \u003Ccommand>          # map | folders | sources \u003Cfolder> | stale | check | nudge\n```\n\n## Pick the mode from what the user asked\n\n- **\"refresh okf\", \"update the OKF docs for X\", \"the API changed, update okf\"**\n  → Refresh mode (the common case).\n- **\"set up okf\", \"create an OKF bundle\", bundle missing** → Scaffold mode.\n- **\"check okf\", \"is the bundle conformant\", \"any dead links\"** → Check mode.\n\n## The folder \u003C-> source mapping\n\nThe mapping is **per-repository data**, declared in `.okforge.config.json` at the\nproject root. okforge ships with none of it. The file shape is:\n\n```json\n{\n  \"folders\": {\n    \"runtime_concepts\": [\"packages\u002Ffoo\u002Fsrc\u002Fmodel\u002F\", \"packages\u002Ffoo\u002Fsrc\u002Fevent\u002F\"],\n    \"config_formats\": [\"packages\u002Ffoo\u002Fdata\u002Fschemas\u002Fthing.schema.json\"]\n  }\n}\n```\n\nEach key is an OKF concept folder; each value is the list of source path prefixes\nthat folder is derived from. `npx okforge map` prints the resolved mapping;\n`npx okforge sources \u003Cfolder>` prints one folder's source paths;\n`npx okforge folders` lists the declared folders. Never hardcode the mapping in\ndocs — read it from the config so there is one source of truth (the hook reads it\ntoo). When the codebase moves, edit `.okforge.config.json`.\n\n## Refresh mode\n\n1. Determine which folder(s) to refresh. If the user named one, use it. If they\n   said \"whatever changed\", run `npx okforge stale` — it lists folders whose\n   source changed since HEAD without the folder being edited.\n2. For each folder, run `npx okforge sources \u003Cfolder>` and **READ those real\n   files**.\n3. Regenerate the affected concept docs from what you read, following the OKF\n   authoring rules below. Only rewrite docs whose underlying source actually\n   changed; leave correct docs untouched. Preserve existing filenames unless the\n   source they document was renamed or removed.\n4. If a concept's source was deleted, delete its doc and remove it from the\n   folder `index.md`. If a new source appeared, add a new concept doc and link\n   it from `index.md`.\n5. Update the folder `index.md`, and if folders were added\u002Fremoved update the\n   root `.okf\u002Findex.md`, the `.okforge.config.json` mapping, and prepend a dated\n   entry to `.okf\u002Flog.md`.\n6. Run `npx okforge check` and resolve every problem it reports before finishing.\n\n## Scaffold mode\n\nCreate `.okforge.config.json` at the project root with the folder\u003C->source\nmapping for this repository (ask the user or infer it from the layout). Then\ncreate `.okf\u002Findex.md` (the only file with frontmatter: `okf_version: \"0.1\"` and\n`type: Bundle Index`) and `.okf\u002Flog.md`. Create the folders from the mapping and\nrefresh each. Finish with `npx okforge check`.\n\n## Check mode\n\nRun `npx okforge check`. It verifies snake_case names, that every non-index `.md`\nhas a non-empty frontmatter `type`, that sub-folder `index.md` files carry no\nfrontmatter, and that bundle-relative `.md` links resolve. Report results; fix\nproblems if the user asked you to.\n\n## OKF authoring rules (follow exactly when writing docs)\n\n- **File names**: snake_case only. No kebab-case, no spaces.\n- **Concept docs**: every non-index `.md` starts with a YAML frontmatter block\n  delimited by `---` lines. Required: `type` (non-empty, e.g. `Config Format`,\n  `Concept`, `Data Model`, `API Endpoint`, `CLI Command`, `Crew`, `Package`).\n  Recommended: `title`, `description` (one sentence), `resource` (path\u002FURI of\n  the real underlying asset), `tags`, `timestamp` (ISO 8601 — set to today's\n  date on refresh).\n- **Body**: favor structural markdown — headings, lists, tables, fenced code —\n  over prose. Use conventional sections where they apply: `# Schema` (field\u002F\n  shape), `# Examples` (code), `# Citations` (sources).\n- **Index files** (reserved): `index.md` has NO frontmatter (except the root\n  bundle index). It lists the folder's concepts as bulleted markdown links with\n  one-line descriptions, optionally grouped under `#` headings.\n- **Links**: cross-link concepts with relative markdown paths from the doc, e.g.\n  `[job store](..\u002Fruntime_concepts\u002Fjob_store.md)` or `[sibling](.\u002Fsibling.md)`.\n  Never use bundle-root absolute paths (those beginning with `\u002F`, e.g.\n  `\u002Fruntime_concepts\u002Fjob_store.md`). Link to real repo source files (in\n  `# Citations`) with repo-relative paths from the doc, e.g.\n  `..\u002F..\u002Fpackages\u002Ffoo\u002Fsrc\u002Fmodel\u002Fjob_store.ts`.\n- **Grounding (critical)**: every claim must come from the real source you read.\n  Do not invent field names, routes, flags, states, or behavior. If uncertain,\n  omit. Quote real schema fields and real route paths.\n- **Style**: plain English, no slang, no abbreviations.\n\n## Companion hook\n\nA `Stop` hook (`npx okforge nudge`, registered in `.claude\u002Fsettings.json`) nudges\nat session end when mapped source changed but `.okf\u002F` was not updated. It reads the\nsame `.okforge.config.json` mapping via `npx okforge stale`, so editing the\nmapping updates both the skill and the nudge.\n",{"name":5,"description":7},"main","5f38013b50cc52414756293cf1f055e01651194e",".claude\u002Fskills\u002Fokforge-maintain",0,"https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli","https:\u002F\u002Fgithub.com\u002Fjeromeetienne","http:\u002F\u002Ftwitter.com\u002Fjerome_etienne","I build AI tools that turn ideas into shipped products in days.","2026-07-02 15:31:48",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jeromeetienne\u002Fvoicebox_cli --skill okforge-maintain",{"tool":39,"command":40},"bunx","bunx skills add jeromeetienne\u002Fvoicebox_cli --skill okforge-maintain",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jeromeetienne\u002Fvoicebox_cli --skill okforge-maintain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fokforge-maintain\u002FSKILL.md",true,[],[48,55,60],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M77ZDYRZ6WTTPGDX8DG0MTQD","voicebox","Generate speech from text (text-to-speech \u002F TTS) and transcribe audio to text using the local voicebox API through the `voicebox-cli` command-line tool. Use whenever the user wants to synthesize a voice, read text aloud, turn text into an audio \u002F MP3 \u002F WAV file, pick or clone a voice, manage voice profiles, or transcribe a recording to text. Requires a running voicebox server (default http:\u002F\u002F127.0.0.1:17493).","https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli\u002Fblob\u002Fmain\u002Fdotclaude_folder\u002Fskills\u002Fvoicebox\u002FSKILL.md",[],[],{"skillNo":56,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77ZDW672JZ482VJXJ3J2Z8B","https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvoicebox\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77ZDNFNZ10R5XHK2B8AYEE0","okforge-query","Read-only browser for any Open Knowledge Format (OKF) knowledge bundle — a tree of markdown concept files. Use it whenever the user wants to browse, explore, map, or navigate a knowledge bundle; asks \"what concepts are in \u003Cbundle>\", \"what links to X\" \u002F \"what does X link to\", \"show me the OKF graph\", \"find orphan or broken concepts\", or \"summarize recent changes\"; or points at a directory of markdown docs with frontmatter and `index.md` \u002F `log.md` files — even when they never say \"OKF\". Prefer this skill for any read-only question about such a bundle's structure, concepts, links, or history. It never edits the bundle.","https:\u002F\u002Fgithub.com\u002Fjeromeetienne\u002Fvoicebox_cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fokforge-query\u002FSKILL.md",[],[]]