[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M7G8VB3PDR3Z7HRF03GYF":3,"skill-same:01M70M7G8VB3PDR3Z7HRF03GYF":89},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":82},"01M70M7G8VB3PDR3Z7HRF03GYF","frontmatter-guard",null,"Validate and auto-repair YAML frontmatter on brain pages. Catches malformed\npages before they enter the brain (missing closing ---, nested quotes, slug\nmismatches, null bytes, empty frontmatter, YAML parse failures). Wraps the\n`gbrain frontmatter` CLI for agent-driven workflows.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-frontmatter-guard\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"frontmatter guard","frontmatter","guard","brain","parse","for","true","closing","quotes","missing","pages","cli","repair","malformed","auto","fix","check","audit","lint","workflows","2026-11-10 10:12:30",false,"---\nname: frontmatter-guard\nversion: 1.0.0\ndescription: |\n  Validate and auto-repair YAML frontmatter on brain pages. Catches malformed\n  pages before they enter the brain (missing closing ---, nested quotes, slug\n  mismatches, null bytes, empty frontmatter, YAML parse failures). Wraps the\n  `gbrain frontmatter` CLI for agent-driven workflows.\ntriggers:\n  - \"validate frontmatter\"\n  - \"check frontmatter\"\n  - \"fix frontmatter\"\n  - \"frontmatter audit\"\n  - \"brain lint\"\ntools:\n  - exec\nmutating: true\n---\n\n# Frontmatter Guard Skill\n\n> **Convention:** see `skills\u002Fconventions\u002Fquality.md` for citation rules; this skill is structural validation, not citation auditing.\n\n## Contract\n\nThis skill guarantees:\n- Every brain page is scanned against the seven canonical frontmatter validation classes\n- Mechanical errors (nested quotes, missing closing `---`, null bytes, slug mismatch) are auto-repairable on demand with `.bak` backups\n- Validation logic is shared with `gbrain doctor`'s `frontmatter_integrity` subcheck — single source of truth\n- Reports per source (gbrain is multi-source since v0.18.0); never silently audits the wrong root\n\n## Why This Exists\n\nBrain pages pile up over months. Agents write them with malformed frontmatter:\n- Missing closing `---` (entity detector bugs)\n- Unstructured YAML in meeting pages (ingestion bugs)\n- Slug mismatches (path renames not propagated)\n- Null bytes (binary corruption from copy-paste accidents)\n- Nested double quotes in titles (`title: \"Phil \"Nick\" Last\"`)\n\nWithout a guard, these accumulate silently until `gbrain sync` chokes or search returns garbage. The guard makes the failure visible at audit time and trivially fixable.\n\n## Validation classes\n\n| Code | Meaning | Auto-fixable? |\n|------|---------|---------------|\n| `MISSING_OPEN` | File doesn't start with `---` | No (needs human) |\n| `MISSING_CLOSE` | No closing `---` before first heading | Yes |\n| `YAML_PARSE` | YAML failed to parse | Sometimes (depends on cause) |\n| `SLUG_MISMATCH` | Frontmatter `slug:` differs from path-derived slug | Yes (removes the field) |\n| `NULL_BYTES` | Binary corruption (`\\x00`) | Yes |\n| `NESTED_QUOTES` | `title: \"outer \"inner\" outer\"` shape | Yes |\n| `EMPTY_FRONTMATTER` | Open + close present but nothing between | No (needs human) |\n\n## Phases\n\n### Phase 1: Audit\n\nRun a read-only scan across all registered sources (or one with `--source \u003Cid>`).\n\n```bash\ngbrain frontmatter audit --json\n```\n\nReports:\n- Per-source counts grouped by error code\n- Sample of up to 20 affected pages per source\n- Total count\n- Scan timestamp\n\nOutput is JSON; agents parse `errors_by_code` and `per_source` to decide next steps.\n\n### Phase 2: Validate one path\n\nValidate a single file or directory (does not require source registration):\n\n```bash\ngbrain frontmatter validate \u003Cpath> --json\n```\n\nExit code 0 = clean; 1 = errors found. Use this in CI pipelines or pre-commit hooks.\n\n### Phase 3: Fix\n\nWhen issues are found:\n\n```bash\ngbrain frontmatter validate \u003Cpath> --fix\n```\n\n`--fix` writes `\u003Cfile>.bak` for every modified file before mutating. The backup is the safety contract — works whether the brain is a git repo or a plain directory.\n\n`--dry-run` previews without writing. Use this before applying fixes in batch.\n\n### Phase 4: Pre-commit hook (optional)\n\nFor brain repos that ARE git repos, install the pre-commit hook to block malformed pages from being committed in the first place:\n\n```bash\ngbrain frontmatter install-hook [--source \u003Cid>]\n```\n\nThe hook runs `gbrain frontmatter validate` against staged `.md`\u002F`.mdx` files. Bypass with `git commit --no-verify`.\n\n## Trigger words\n\nWhen the user says any of these, route here:\n- \"validate frontmatter\"\n- \"check frontmatter\"\n- \"fix frontmatter\"\n- \"frontmatter audit\"\n- \"brain lint\"\n\n## Output rules\n\n- Always run `gbrain frontmatter audit --json` first; never assume a brain is clean.\n- Surface counts to the user in plain language; do not dump raw JSON.\n- For `--fix` operations: state how many files will be modified BEFORE running, then confirm.\n- `SLUG_MISMATCH` fixes remove the frontmatter `slug:` field — gbrain derives slug from path. Mention this when the user's title is intentionally renamed.\n- Never auto-fix `MISSING_OPEN` or `EMPTY_FRONTMATTER` without explicit user input — these usually mean a human author started a page and didn't finish.\n\n## Chains with\n\n- `gbrain doctor` — the `frontmatter_integrity` subcheck reports the same counts as `audit`.\n- `skills\u002Fmaintain\u002FSKILL.md` — broader brain health audit; chain after this skill if other classes of issue are suspected.\n- `skills\u002Flint\u002FSKILL.md` (via `gbrain lint`) — overlapping rules for skill-file lint; the `frontmatter-*` rule names in lint output come from this skill's validation surface.\n\n## Output Format\n\nAudit summary (terse, agent-friendly):\n\n```\nFrontmatter audit — 17 issue(s) across 1 source(s)\n\n[default] \u002FUsers\u002Fme\u002Fbrain\n  17 issue(s)\n    MISSING_CLOSE: 8\n    NESTED_QUOTES: 5\n    NULL_BYTES: 4\n  sample:\n    people\u002Fjane.md — MISSING_CLOSE\n    companies\u002Facme.md — NESTED_QUOTES\n    (+ 12 more)\n\nFix with: gbrain frontmatter validate \u002FUsers\u002Fme\u002Fbrain --fix\n```\n\nJSON envelope (when `--json` is passed):\n\n```json\n{\n  \"ok\": false,\n  \"total\": 17,\n  \"errors_by_code\": { \"MISSING_CLOSE\": 8, \"NESTED_QUOTES\": 5, \"NULL_BYTES\": 4 },\n  \"per_source\": [\n    {\n      \"source_id\": \"default\",\n      \"source_path\": \"\u002FUsers\u002Fme\u002Fbrain\",\n      \"total\": 17,\n      \"errors_by_code\": { \"MISSING_CLOSE\": 8, \"NESTED_QUOTES\": 5, \"NULL_BYTES\": 4 },\n      \"sample\": [{ \"path\": \"people\u002Fjane.md\", \"codes\": [\"MISSING_CLOSE\"] }]\n    }\n  ],\n  \"scanned_at\": \"2026-04-25T22:30:00.000Z\"\n}\n```\n\n`gbrain frontmatter validate \u003Cpath> --json` returns a similar envelope keyed on per-file results instead of per-source.\n\n## Anti-Patterns\n\n**Don't auto-fix `MISSING_OPEN` or `EMPTY_FRONTMATTER` without user input.** These usually mean a human author started a page and didn't finish — silently inserting `---` markers around an unfinished draft is wrong.\n\n**Don't use `--fix` to \"make doctor green\" without reading the audit first.** SLUG_MISMATCH cases are surfaced for manual review specifically because gbrain derives the slug from path. A mismatch usually means the user renamed a file intentionally; auto-removing the slug field is the right outcome only when you've confirmed the rename was deliberate.\n\n**Don't skip the `.bak` backups.** The `.bak` is the safety contract for non-git brain repos. If `.bak` files accumulate after a fix run, that's a feature, not a bug — the user can review the diffs and delete the backups when satisfied.\n\n**Don't run `audit` on a brain where sources aren't registered.** The CLI returns \"no registered sources to audit\" gracefully, but the migration emits a `skipped: no_sources` phase result. Don't paper over this with a manual path-walk; the right fix is to register the source via `gbrain sources add`.\n\n**Don't install the pre-commit hook on non-git brain dirs.** The install-hook command skips them automatically with a one-line note. If you see \"skipped — not a git repo\" and want validation at write time anyway, use the `audit` command on a cron schedule.\n","# Frontmatter Guard Skill\n\n> **Convention:** see `skills\u002Fconventions\u002Fquality.md` for citation rules; this skill is structural validation, not citation auditing.\n\n## Contract\n\nThis skill guarantees:\n- Every brain page is scanned against the seven canonical frontmatter validation classes\n- Mechanical errors (nested quotes, missing closing `---`, null bytes, slug mismatch) are auto-repairable on demand with `.bak` backups\n- Validation logic is shared with `gbrain doctor`'s `frontmatter_integrity` subcheck — single source of truth\n- Reports per source (gbrain is multi-source since v0.18.0); never silently audits the wrong root\n\n## Why This Exists\n\nBrain pages pile up over months. Agents write them with malformed frontmatter:\n- Missing closing `---` (entity detector bugs)\n- Unstructured YAML in meeting pages (ingestion bugs)\n- Slug mismatches (path renames not propagated)\n- Null bytes (binary corruption from copy-paste accidents)\n- Nested double quotes in titles (`title: \"Phil \"Nick\" Last\"`)\n\nWithout a guard, these accumulate silently until `gbrain sync` chokes or search returns garbage. The guard makes the failure visible at audit time and trivially fixable.\n\n## Validation classes\n\n| Code | Meaning | Auto-fixable? |\n|------|---------|---------------|\n| `MISSING_OPEN` | File doesn't start with `---` | No (needs human) |\n| `MISSING_CLOSE` | No closing `---` before first heading | Yes |\n| `YAML_PARSE` | YAML failed to parse | Sometimes (depends on cause) |\n| `SLUG_MISMATCH` | Frontmatter `slug:` differs from path-derived slug | Yes (removes the field) |\n| `NULL_BYTES` | Binary corruption (`\\x00`) | Yes |\n| `NESTED_QUOTES` | `title: \"outer \"inner\" outer\"` shape | Yes |\n| `EMPTY_FRONTMATTER` | Open + close present but nothing between | No (needs human) |\n\n## Phases\n\n### Phase 1: Audit\n\nRun a read-only scan across all registered sources (or one with `--source \u003Cid>`).\n\n```bash\ngbrain frontmatter audit --json\n```\n\nReports:\n- Per-source counts grouped by error code\n- Sample of up to 20 affected pages per source\n- Total count\n- Scan timestamp\n\nOutput is JSON; agents parse `errors_by_code` and `per_source` to decide next steps.\n\n### Phase 2: Validate one path\n\nValidate a single file or directory (does not require source registration):\n\n```bash\ngbrain frontmatter validate \u003Cpath> --json\n```\n\nExit code 0 = clean; 1 = errors found. Use this in CI pipelines or pre-commit hooks.\n\n### Phase 3: Fix\n\nWhen issues are found:\n\n```bash\ngbrain frontmatter validate \u003Cpath> --fix\n```\n\n`--fix` writes `\u003Cfile>.bak` for every modified file before mutating. The backup is the safety contract — works whether the brain is a git repo or a plain directory.\n\n`--dry-run` previews without writing. Use this before applying fixes in batch.\n\n### Phase 4: Pre-commit hook (optional)\n\nFor brain repos that ARE git repos, install the pre-commit hook to block malformed pages from being committed in the first place:\n\n```bash\ngbrain frontmatter install-hook [--source \u003Cid>]\n```\n\nThe hook runs `gbrain frontmatter validate` against staged `.md`\u002F`.mdx` files. Bypass with `git commit --no-verify`.\n\n## Trigger words\n\nWhen the user says any of these, route here:\n- \"validate frontmatter\"\n- \"check frontmatter\"\n- \"fix frontmatter\"\n- \"frontmatter audit\"\n- \"brain lint\"\n\n## Output rules\n\n- Always run `gbrain frontmatter audit --json` first; never assume a brain is clean.\n- Surface counts to the user in plain language; do not dump raw JSON.\n- For `--fix` operations: state how many files will be modified BEFORE running, then confirm.\n- `SLUG_MISMATCH` fixes remove the frontmatter `slug:` field — gbrain derives slug from path. Mention this when the user's title is intentionally renamed.\n- Never auto-fix `MISSING_OPEN` or `EMPTY_FRONTMATTER` without explicit user input — these usually mean a human author started a page and didn't finish.\n\n## Chains with\n\n- `gbrain doctor` — the `frontmatter_integrity` subcheck reports the same counts as `audit`.\n- `skills\u002Fmaintain\u002FSKILL.md` — broader brain health audit; chain after this skill if other classes of issue are suspected.\n- `skills\u002Flint\u002FSKILL.md` (via `gbrain lint`) — overlapping rules for skill-file lint; the `frontmatter-*` rule names in lint output come from this skill's validation surface.\n\n## Output Format\n\nAudit summary (terse, agent-friendly):\n\n```\nFrontmatter audit — 17 issue(s) across 1 source(s)\n\n[default] \u002FUsers\u002Fme\u002Fbrain\n  17 issue(s)\n    MISSING_CLOSE: 8\n    NESTED_QUOTES: 5\n    NULL_BYTES: 4\n  sample:\n    people\u002Fjane.md — MISSING_CLOSE\n    companies\u002Facme.md — NESTED_QUOTES\n    (+ 12 more)\n\nFix with: gbrain frontmatter validate \u002FUsers\u002Fme\u002Fbrain --fix\n```\n\nJSON envelope (when `--json` is passed):\n\n```json\n{\n  \"ok\": false,\n  \"total\": 17,\n  \"errors_by_code\": { \"MISSING_CLOSE\": 8, \"NESTED_QUOTES\": 5, \"NULL_BYTES\": 4 },\n  \"per_source\": [\n    {\n      \"source_id\": \"default\",\n      \"source_path\": \"\u002FUsers\u002Fme\u002Fbrain\",\n      \"total\": 17,\n      \"errors_by_code\": { \"MISSING_CLOSE\": 8, \"NESTED_QUOTES\": 5, \"NULL_BYTES\": 4 },\n      \"sample\": [{ \"path\": \"people\u002Fjane.md\", \"codes\": [\"MISSING_CLOSE\"] }]\n    }\n  ],\n  \"scanned_at\": \"2026-04-25T22:30:00.000Z\"\n}\n```\n\n`gbrain frontmatter validate \u003Cpath> --json` returns a similar envelope keyed on per-file results instead of per-source.\n\n## Anti-Patterns\n\n**Don't auto-fix `MISSING_OPEN` or `EMPTY_FRONTMATTER` without user input.** These usually mean a human author started a page and didn't finish — silently inserting `---` markers around an unfinished draft is wrong.\n\n**Don't use `--fix` to \"make doctor green\" without reading the audit first.** SLUG_MISMATCH cases are surfaced for manual review specifically because gbrain derives the slug from path. A mismatch usually means the user renamed a file intentionally; auto-removing the slug field is the right outcome only when you've confirmed the rename was deliberate.\n\n**Don't skip the `.bak` backups.** The `.bak` is the safety contract for non-git brain repos. If `.bak` files accumulate after a fix run, that's a feature, not a bug — the user can review the diffs and delete the backups when satisfied.\n\n**Don't run `audit` on a brain where sources aren't registered.** The CLI returns \"no registered sources to audit\" gracefully, but the migration emits a `skipped: no_sources` phase result. Don't paper over this with a manual path-walk; the right fix is to register the source via `gbrain sources add`.\n\n**Don't install the pre-commit hook on non-git brain dirs.** The install-hook command skips them automatically with a one-line note. If you see \"skipped — not a git repo\" and want validation at write time anyway, use the `audit` command on a cron schedule.\n",{"name":5,"tools":49,"version":51,"mutating":52,"triggers":53,"description":59},[50],"exec","1.0.0",true,[54,55,56,57,58],"validate frontmatter","check frontmatter","fix frontmatter","frontmatter audit","brain lint","Validate and auto-repair YAML frontmatter on brain pages. Catches malformed\npages before they enter the brain (missing closing ---, nested quotes, slug\nmismatches, null bytes, empty frontmatter, YAML parse failures). Wraps the\n`gbrain frontmatter` CLI for agent-driven workflows.\n","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fgbrain-frontmatter-guard",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":52},[72,75,78],{"tool":73,"command":74},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill frontmatter-guard",{"tool":76,"command":77},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill frontmatter-guard",{"tool":79,"command":80},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill frontmatter-guard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-frontmatter-guard\u002FSKILL.md",[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"routing-eval.jsonl","OTHER","其他",673,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgbrain-frontmatter-guard\u002Frouting-eval.jsonl",[90,107,138,164,186,206],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":99,"publishedAt":44},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[100,101,102,103,104,105,106],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":119,"publishedAt":44},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[113,114],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[109,120,121,122,123,124,125,126,127,128,129,35,130,131,132,133,134,135,136,137],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":148,"publishedAt":44},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[144,145],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":146,"categoryName":147,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000036","内容创作者",[140,149,150,151,152,153,154,155,128,156,157,158,159,160,38,161,162,163],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","when","use","types","Video","创作",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":44},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,140,174,175,162,176,177,178,179,180,181,182,183,126,184,159,160,120,185],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":44},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[192,193,194,195],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},{"categoryNo":146,"categoryName":147,"taxonomyType":117,"taxonomyTypeDesc":118},[197,105,198,199,200,201,135,159,160,202,203,204,205],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":214,"publishedAt":44},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[212,213],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":146,"categoryName":147,"taxonomyType":117,"taxonomyTypeDesc":118},[215,105,216,124,217,203,159,198,201,160,204],"Rules","writing rules","project rules"]