[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C5E0B7PW65YK4635TY13WP":3,"skill-same:01M6C5E0B7PW65YK4635TY13WP":99},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6C5E0B7PW65YK4635TY13WP","blueprint-claude-md",null,"CLAUDE.md and CLAUDE.local.md from blueprint artifacts. Use when editing CLAUDE.md team instructions, converting inline content to @imports, or setting up CLAUDE.local.md.","laurigates\u002Fclaude-plugins","laurigates","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13014001?v=4","01M6C59YHWS9C7KMXKSRX1YXNP","Lauri Gates","01M6C59YP2APG9YAM4DWYQYGFJ",59,"MIT","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"claude md","Blueprint","blueprint claude md","up","2026","when","imports","inline","2025","sep","local","wed","artifacts","use","instructions","edit","write","read","editing","grep","Bash","team","content","2026-11-10 10:12:30",false,"---\ncreated: 2025-12-17\nmodified: 2026-09-23\nreviewed: 2026-02-09\ndescription: CLAUDE.md and CLAUDE.local.md from blueprint artifacts. Use when editing CLAUDE.md team instructions, converting inline content to @imports, or setting up CLAUDE.local.md.\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion\nname: blueprint-claude-md\n---\n\nGenerate or update the project's CLAUDE.md file based on blueprint artifacts, PRDs, and project structure.\n\nBranch-specific detail lives in `references\u002F`, split by the path that needs it — an invocation opens only the file for the branch it takes.\n\n## When to Use This Skill\n\n| Use this skill when... | Use alternative when... |\n|------------------------|-------------------------|\n| Need to create\u002Fupdate CLAUDE.md for team instructions | Use `\u002Fblueprint:rules` for path-specific rules |\n| Want to add @imports to existing CLAUDE.md | Use `\u002Fblueprint:generate-rules` to create rules from PRDs |\n| Need to create CLAUDE.local.md for personal preferences | Editing individual rule files directly |\n| Converting inline content to lean @import structure | Just need to view current memory configuration |\n\n## CLAUDE.md vs Auto Memory\n\nClaude Code has two complementary systems for project context. CLAUDE.md should contain **team-shared instructions** — not patterns Claude learns on its own.\n\n| Belongs in CLAUDE.md | Belongs in Auto Memory (managed by Claude) |\n|----------------------|---------------------------------------------|\n| Team coding standards | Debugging insights and workarounds |\n| Build\u002Ftest\u002Flint commands | Personal workflow preferences |\n| Architecture decisions | Project-specific patterns learned over time |\n| Required conventions | File relationships and navigation shortcuts |\n| CI\u002FCD workflows | Common mistakes and how to fix them |\n\nAuto memory lives at `~\u002F.claude\u002Fprojects\u002F\u003Cproject>\u002Fmemory\u002F` and is managed automatically. Do not duplicate auto memory concerns into CLAUDE.md.\n\n## Memory Hierarchy (precedence low → high)\n\n1. **User-level rules**: `~\u002F.claude\u002Frules\u002F` — personal rules across all projects\n2. **CLAUDE.md (project)**: Team-shared project instructions (checked into git)\n3. **CLAUDE.local.md**: Personal project-specific preferences (gitignored)\n4. **.claude\u002Frules\u002F**: Modular, path-specific rules\n5. **Managed policy**: Organization-wide instructions (enterprise, system paths)\n6. **Auto memory**: Claude's own notes (`~\u002F.claude\u002Fprojects\u002F\u003Cproject>\u002Fmemory\u002F`)\n\n## @import Syntax\n\nCLAUDE.md files support importing other markdown files to stay lean:\n\n```markdown\n# Project: MyApp\n\n@docs\u002Farchitecture.md\n@docs\u002Fconventions.md\n@.claude\u002Frules\u002Ftesting.md\n```\n\n- Paths are relative to the file containing the import\n- Recursive imports supported (max depth 5)\n- Imports are not evaluated inside code spans or code blocks\n- First-time external imports trigger an approval dialog\n\nUse `@import` to reference existing documentation rather than duplicating content into CLAUDE.md.\n\n## CLAUDE.md Best Practices\n\n- Keep it concise (\u003C 500 lines ideally)\n- Focus on team-shared instructions (standards, commands, architecture)\n- Use `@import` to reference existing docs instead of duplicating content\n- Use `CLAUDE.local.md` for personal preferences (auto-gitignored)\n- Reference `.claude\u002Frules\u002F` for detailed, path-specific rules\n- Let auto memory handle \"Current Focus\", \"Key Files\", debugging tips\n- Update when PRDs change significantly\n\n## Execution\n\nExecute this CLAUDE.md workflow:\n\n### Step 1: Check current state\n\n- Look for existing `CLAUDE.md` in project root\n- Look for existing `CLAUDE.local.md` (personal preferences, gitignored)\n- Read `docs\u002Fblueprint\u002Fmanifest.json` for configuration\n- Check for `~\u002F.claude\u002Frules\u002F` (user-level rules)\n- Determine `claude_md_mode` (single, modular, or both)\n\n### Step 2: Determine action\n\nUse AskUserQuestion:\n\n```\n{If CLAUDE.md exists:}\nquestion: \"CLAUDE.md already exists. What would you like to do?\"\noptions:\n  - \"Update with latest project info\" → merge updates\n  - \"Regenerate completely\" → overwrite (backup first)\n  - \"Add missing sections only\" → append new content\n  - \"Add @imports for existing docs\" → replace inline content with imports\n  - \"Convert to modular rules\" → split into .claude\u002Frules\u002F\n  - \"Create CLAUDE.local.md\" → personal preferences (gitignored)\n  - \"View current structure\" → analyze and display\n\n{If CLAUDE.md doesn't exist:}\nquestion: \"No CLAUDE.md found. How would you like to create it?\"\noptions:\n  - \"Generate from project analysis\" → auto-generate\n  - \"Generate from PRDs\" → use blueprint PRDs\n  - \"Generate with @imports (lean)\" → auto-generate using imports for existing docs\n  - \"Start with template\" → use starter template\n  - \"Use modular rules instead\" → skip CLAUDE.md, use rules\u002F\n```\n\n### Step 3: Gather project context\n\n- **Project structure**: Detect language, framework, build tools\n- **PRDs**: Read `docs\u002Fprds\u002F*.md` for requirements\n- **Work overview**: Current phase and progress\n- **Existing rules**: Content from `.claude\u002Frules\u002F` if present\n- **Git history**: Recent patterns and conventions\n- **Dependencies**: Package managers, key libraries\n\n### Step 4: Generate CLAUDE.md sections\n\nBuild the sections from [`references\u002Ftemplate-sections.md`](references\u002Ftemplate-sections.md): the standard skeleton, tailored with the per-project-type additions. Leave out what auto memory handles (see \"CLAUDE.md vs Auto Memory\" above).\n\n### Step 5: Apply the modular rules mode\n\nIf modular rules mode is `both` or `modular`, follow the matching section of [`references\u002Fmodular-rules-split.md`](references\u002Fmodular-rules-split.md). Mode `single` skips this step.\n\n### Step 6: Apply a selected option\n\n- \"Create CLAUDE.local.md\" → [`references\u002Ftemplate-sections.md`](references\u002Ftemplate-sections.md) § CLAUDE.local.md template\n- \"Add @imports for existing docs\" → [`references\u002Fsmart-update.md`](references\u002Fsmart-update.md) § Add @imports\n\n### Step 7: Smart update (existing CLAUDE.md)\n\nWhen CLAUDE.md already exists, follow [`references\u002Fsmart-update.md`](references\u002Fsmart-update.md) § Smart update.\n\n### Step 8: Sync with modular rules\n\nWhen `.claude\u002Frules\u002F` has rules, follow [`references\u002Fmodular-rules-split.md`](references\u002Fmodular-rules-split.md) § Sync with modular rules.\n\n### Step 9: Update manifest and task registry\n\nRecord the run in `docs\u002Fblueprint\u002Fmanifest.json` per [`references\u002Fmanifest-and-registry.md`](references\u002Fmanifest-and-registry.md).\n\n### Step 10: Report\n\n```\n✅ CLAUDE.md updated!\n\n{Created | Updated}: CLAUDE.md\n{If created:} CLAUDE.local.md (personal preferences, gitignored)\n\nSections:\n- Overview ✅\n- Tech Stack ✅\n- Development Workflow ✅\n- Architecture ✅\n- Conventions ✅\n\n@imports used: {count, if any}\n- @docs\u002Fprds\u002Farchitecture.md\n- @.claude\u002Frules\u002Ftesting.md\n\nSources used:\n- PRDs: {list}\n- Rules: {list}\n- Project detection: {what was detected}\n\n{If modular mode:}\nNote: Detailed rules are in .claude\u002Frules\u002F\nCLAUDE.md serves as overview and quick reference.\n\nNote: \"Current Focus\" and \"Key Files\" are managed by Claude's\nauto memory — no need to maintain these in CLAUDE.md.\n\nRun `\u002Fblueprint:status` to see full configuration.\n```\n\n### Step 11: Prompt for next action\n\nUse AskUserQuestion:\n\n```\nquestion: \"CLAUDE.md updated. What would you like to do next?\"\noptions:\n  - label: \"Check blueprint status (Recommended)\"\n    description: \"Run \u002Fblueprint:status to verify configuration\"\n  - label: \"Manage modular rules\"\n    description: \"Add or edit rules in .claude\u002Frules\u002F\"\n  - label: \"Continue development\"\n    description: \"Run \u002Fproject:continue to work on next task\"\n  - label: \"I'm done for now\"\n    description: \"Exit - CLAUDE.md is saved\"\n```\n\n**Based on selection:**\n- \"Check blueprint status\" → Run `\u002Fblueprint:status`\n- \"Manage modular rules\" → Run `\u002Fblueprint:rules`\n- \"Continue development\" → Run `\u002Fproject:continue`\n- \"I'm done\" → Exit\n","Generate or update the project's CLAUDE.md file based on blueprint artifacts, PRDs, and project structure.\n\nBranch-specific detail lives in `references\u002F`, split by the path that needs it — an invocation opens only the file for the branch it takes.\n\n## When to Use This Skill\n\n| Use this skill when... | Use alternative when... |\n|------------------------|-------------------------|\n| Need to create\u002Fupdate CLAUDE.md for team instructions | Use `\u002Fblueprint:rules` for path-specific rules |\n| Want to add @imports to existing CLAUDE.md | Use `\u002Fblueprint:generate-rules` to create rules from PRDs |\n| Need to create CLAUDE.local.md for personal preferences | Editing individual rule files directly |\n| Converting inline content to lean @import structure | Just need to view current memory configuration |\n\n## CLAUDE.md vs Auto Memory\n\nClaude Code has two complementary systems for project context. CLAUDE.md should contain **team-shared instructions** — not patterns Claude learns on its own.\n\n| Belongs in CLAUDE.md | Belongs in Auto Memory (managed by Claude) |\n|----------------------|---------------------------------------------|\n| Team coding standards | Debugging insights and workarounds |\n| Build\u002Ftest\u002Flint commands | Personal workflow preferences |\n| Architecture decisions | Project-specific patterns learned over time |\n| Required conventions | File relationships and navigation shortcuts |\n| CI\u002FCD workflows | Common mistakes and how to fix them |\n\nAuto memory lives at `~\u002F.claude\u002Fprojects\u002F\u003Cproject>\u002Fmemory\u002F` and is managed automatically. Do not duplicate auto memory concerns into CLAUDE.md.\n\n## Memory Hierarchy (precedence low → high)\n\n1. **User-level rules**: `~\u002F.claude\u002Frules\u002F` — personal rules across all projects\n2. **CLAUDE.md (project)**: Team-shared project instructions (checked into git)\n3. **CLAUDE.local.md**: Personal project-specific preferences (gitignored)\n4. **.claude\u002Frules\u002F**: Modular, path-specific rules\n5. **Managed policy**: Organization-wide instructions (enterprise, system paths)\n6. **Auto memory**: Claude's own notes (`~\u002F.claude\u002Fprojects\u002F\u003Cproject>\u002Fmemory\u002F`)\n\n## @import Syntax\n\nCLAUDE.md files support importing other markdown files to stay lean:\n\n```markdown\n# Project: MyApp\n\n@docs\u002Farchitecture.md\n@docs\u002Fconventions.md\n@.claude\u002Frules\u002Ftesting.md\n```\n\n- Paths are relative to the file containing the import\n- Recursive imports supported (max depth 5)\n- Imports are not evaluated inside code spans or code blocks\n- First-time external imports trigger an approval dialog\n\nUse `@import` to reference existing documentation rather than duplicating content into CLAUDE.md.\n\n## CLAUDE.md Best Practices\n\n- Keep it concise (\u003C 500 lines ideally)\n- Focus on team-shared instructions (standards, commands, architecture)\n- Use `@import` to reference existing docs instead of duplicating content\n- Use `CLAUDE.local.md` for personal preferences (auto-gitignored)\n- Reference `.claude\u002Frules\u002F` for detailed, path-specific rules\n- Let auto memory handle \"Current Focus\", \"Key Files\", debugging tips\n- Update when PRDs change significantly\n\n## Execution\n\nExecute this CLAUDE.md workflow:\n\n### Step 1: Check current state\n\n- Look for existing `CLAUDE.md` in project root\n- Look for existing `CLAUDE.local.md` (personal preferences, gitignored)\n- Read `docs\u002Fblueprint\u002Fmanifest.json` for configuration\n- Check for `~\u002F.claude\u002Frules\u002F` (user-level rules)\n- Determine `claude_md_mode` (single, modular, or both)\n\n### Step 2: Determine action\n\nUse AskUserQuestion:\n\n```\n{If CLAUDE.md exists:}\nquestion: \"CLAUDE.md already exists. What would you like to do?\"\noptions:\n  - \"Update with latest project info\" → merge updates\n  - \"Regenerate completely\" → overwrite (backup first)\n  - \"Add missing sections only\" → append new content\n  - \"Add @imports for existing docs\" → replace inline content with imports\n  - \"Convert to modular rules\" → split into .claude\u002Frules\u002F\n  - \"Create CLAUDE.local.md\" → personal preferences (gitignored)\n  - \"View current structure\" → analyze and display\n\n{If CLAUDE.md doesn't exist:}\nquestion: \"No CLAUDE.md found. How would you like to create it?\"\noptions:\n  - \"Generate from project analysis\" → auto-generate\n  - \"Generate from PRDs\" → use blueprint PRDs\n  - \"Generate with @imports (lean)\" → auto-generate using imports for existing docs\n  - \"Start with template\" → use starter template\n  - \"Use modular rules instead\" → skip CLAUDE.md, use rules\u002F\n```\n\n### Step 3: Gather project context\n\n- **Project structure**: Detect language, framework, build tools\n- **PRDs**: Read `docs\u002Fprds\u002F*.md` for requirements\n- **Work overview**: Current phase and progress\n- **Existing rules**: Content from `.claude\u002Frules\u002F` if present\n- **Git history**: Recent patterns and conventions\n- **Dependencies**: Package managers, key libraries\n\n### Step 4: Generate CLAUDE.md sections\n\nBuild the sections from [`references\u002Ftemplate-sections.md`](references\u002Ftemplate-sections.md): the standard skeleton, tailored with the per-project-type additions. Leave out what auto memory handles (see \"CLAUDE.md vs Auto Memory\" above).\n\n### Step 5: Apply the modular rules mode\n\nIf modular rules mode is `both` or `modular`, follow the matching section of [`references\u002Fmodular-rules-split.md`](references\u002Fmodular-rules-split.md). Mode `single` skips this step.\n\n### Step 6: Apply a selected option\n\n- \"Create CLAUDE.local.md\" → [`references\u002Ftemplate-sections.md`](references\u002Ftemplate-sections.md) § CLAUDE.local.md template\n- \"Add @imports for existing docs\" → [`references\u002Fsmart-update.md`](references\u002Fsmart-update.md) § Add @imports\n\n### Step 7: Smart update (existing CLAUDE.md)\n\nWhen CLAUDE.md already exists, follow [`references\u002Fsmart-update.md`](references\u002Fsmart-update.md) § Smart update.\n\n### Step 8: Sync with modular rules\n\nWhen `.claude\u002Frules\u002F` has rules, follow [`references\u002Fmodular-rules-split.md`](references\u002Fmodular-rules-split.md) § Sync with modular rules.\n\n### Step 9: Update manifest and task registry\n\nRecord the run in `docs\u002Fblueprint\u002Fmanifest.json` per [`references\u002Fmanifest-and-registry.md`](references\u002Fmanifest-and-registry.md).\n\n### Step 10: Report\n\n```\n✅ CLAUDE.md updated!\n\n{Created | Updated}: CLAUDE.md\n{If created:} CLAUDE.local.md (personal preferences, gitignored)\n\nSections:\n- Overview ✅\n- Tech Stack ✅\n- Development Workflow ✅\n- Architecture ✅\n- Conventions ✅\n\n@imports used: {count, if any}\n- @docs\u002Fprds\u002Farchitecture.md\n- @.claude\u002Frules\u002Ftesting.md\n\nSources used:\n- PRDs: {list}\n- Rules: {list}\n- Project detection: {what was detected}\n\n{If modular mode:}\nNote: Detailed rules are in .claude\u002Frules\u002F\nCLAUDE.md serves as overview and quick reference.\n\nNote: \"Current Focus\" and \"Key Files\" are managed by Claude's\nauto memory — no need to maintain these in CLAUDE.md.\n\nRun `\u002Fblueprint:status` to see full configuration.\n```\n\n### Step 11: Prompt for next action\n\nUse AskUserQuestion:\n\n```\nquestion: \"CLAUDE.md updated. What would you like to do next?\"\noptions:\n  - label: \"Check blueprint status (Recommended)\"\n    description: \"Run \u002Fblueprint:status to verify configuration\"\n  - label: \"Manage modular rules\"\n    description: \"Add or edit rules in .claude\u002Frules\u002F\"\n  - label: \"Continue development\"\n    description: \"Run \u002Fproject:continue to work on next task\"\n  - label: \"I'm done for now\"\n    description: \"Exit - CLAUDE.md is saved\"\n```\n\n**Based on selection:**\n- \"Check blueprint status\" → Run `\u002Fblueprint:status`\n- \"Manage modular rules\" → Run `\u002Fblueprint:rules`\n- \"Continue development\" → Run `\u002Fproject:continue`\n- \"I'm done\" → Exit\n",{"name":5,"created":47,"modified":48,"reviewed":49,"description":7,"allowed-tools":50},1765929600000,1790121600000,1770595200000,"Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion","main","bdd0582f1a2ba53d21061835bfd72d45f2f954f4","blueprint-plugin\u002Fskills\u002Fblueprint-claude-md",6,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins","https:\u002F\u002Fgithub.com\u002Flaurigates","Linux enthusiast, cloud engineer, neovim addict, electronics hobbyist.","2026-11-12 03:43:32",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add laurigates\u002Fclaude-plugins --skill blueprint-claude-md",{"tool":65,"command":66},"bunx","bunx skills add laurigates\u002Fclaude-plugins --skill blueprint-claude-md",{"tool":68,"command":69},"pnpm","pnpm dlx skills add laurigates\u002Fclaude-plugins --skill blueprint-claude-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002FSKILL.md",true,[73,79,83,87,91,95],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"agents\u002Fopenai.yaml","REFERENCE","参考文档",290,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Funreal-build-mass-entities\u002Fagents\u002Fopenai.yaml",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fentity-processing-lifetimes.md",2702,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Funreal-build-mass-entities\u002Freferences\u002Fentity-processing-lifetimes.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fmanifest-and-registry.md",741,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002Freferences\u002Fmanifest-and-registry.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fmodular-rules-split.md",1361,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002Freferences\u002Fmodular-rules-split.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fsmart-update.md",772,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002Freferences\u002Fsmart-update.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Ftemplate-sections.md",2118,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fblueprint-plugin\u002Fskills\u002Fblueprint-claude-md\u002Freferences\u002Ftemplate-sections.md",[100,127,146,162,185,215],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":42},"01M70PFHMH9ADY0CRE6047Y4B2","kitty-show-image","Show the user an image with a note on what to judge, via a file send or a labelled kitty tab. Use when the user must see an image, or icat fails with no \u002Fdev\u002Ftty.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fkitty-plugin\u002Fskills\u002Fkitty-show-image\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[112,113,114,115,116,117,118,119,120,121,32,24,39,122,123,124,125,126,23,36],"show","kitty show image","image","kitty","show image","ls","get","send","open","dev","file","text","with","xdg","via",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":42},"01M70PFEN18HKQ4RCQ1VPGMPTB","kitty-session-persistence","Snapshot and restore kitty terminal sessions on macOS. Use when surviving WindowServer hangs without losing tabs, configuring snapshots, or restoring after a force-reboot.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fkitty-plugin\u002Fskills\u002Fkitty-session-persistence\u002FSKILL.md",[],[115,134,135,136,137,138,24,39,139,140,141,23,36,35,34,142,143,144,145,32],"kitty session persistence","session","persistence","false","snapshots","uname","reboot","terminal","snapshot","macos","sessions","restore",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":42},"01M70PFC77XGXCVQ1543VGZHYR","kitty-remote-control","Safe kitty remote control from an agent — read panes with kitty @ ls\u002Fget-text, notify, and never mutate the live terminal unasked. Use when running inside kitty.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fkitty-plugin\u002Fskills\u002Fkitty-remote-control\u002FSKILL.md",[],[153,154,115,155,156,117,157,158,118,159,160,32,24,161,39,123,124,141,23,36],"kitty remote control","remote","control","remote control","running","never","panes","notify","query",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":42},"01M70P6WVMCT5JG4SACTM69AF9","docs-reference-check","Dangling doc-reference gate: flag markdown naming repo paths or relative links that no longer exist. Use when docs cite moved\u002Fdeleted files, or wiring a doc-drift lint.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fdocumentation-plugin\u002Fskills\u002Fdocs-reference-check\u002FSKILL.md",[],[169,170,171,172,173,174,175,176,177,178,32,24,39,179,122,180,181,182,183,184],"docs reference check","check","reference check","reference","docs","links","python3","repo","files","auto","drift","lint","wiring","chezmoi","references","cp",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":200,"publishedAt":42},"01M6C6NDE7DAQGNWSF22J5CJ0Z","youtube-upload","Upload a video to YouTube via the Data API v3 and edit its title, description, tags or thumbnail afterwards. Use when publishing or retitling a YouTube video.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fyoutube-plugin\u002Fskills\u002Fyoutube-upload\u002FSKILL.md",[191,194,195],{"categoryNo":192,"categoryName":193,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},{"categoryNo":196,"categoryName":197,"taxonomyType":198,"taxonomyTypeDesc":199},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[201,202,203,204,175,205,36,206,34,207,208,209,32,39,122,210,211,24,212,213,214,126,23],"youtube upload","upload","youtube","Video","run","uv run","publishing","data","uv","api","v3","tags","id","title",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":224,"publishedAt":42},"01M6C6NABWW1X58KJJM4F6GQMQ","youtube-studio-share","Share a private YouTube video with a whole Google Workspace organization by scripting YouTube Studio in the browser. Use when a video must be org-only.","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fyoutube-plugin\u002Fskills\u002Fyoutube-studio-share\u002FSKILL.md",[221],{"categoryNo":222,"categoryName":223,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发",[225,226,227,228,203,204,229,230,231,232,233,36,234,235,236,237,32,238,24,124,239,23],"youtube studio share","share","youtube studio","studio","browser","javascript","scripting","google workspace","workspace","tool","google","only","MCP","chrome","organization"]