[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C5MEK1AS2FA2RZ48FMX51Q":3,"skill-same:01M6C5MEK1AS2FA2RZ48FMX51Q":81},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6C5MEK1AS2FA2RZ48FMX51Q","ticket-drafting-guidelines",null,"What\u002FWhy\u002FHow prose structure and neutral, positive register for issues, PR descriptions, and tickets. Use when wording a ticket body, tightening prose, or applying house tone.","laurigates\u002Fclaude-plugins","laurigates","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13014001?v=4","01M6C59YHWS9C7KMXKSRX1YXNP","Lauri Gates","01M6C59YP2APG9YAM4DWYQYGFJ",60,"MIT","https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fcommunication-plugin\u002Fskills\u002Fticket-drafting-guidelines\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"guidelines","drafting","ticket drafting guidelines","ticket","2026","pr","when","body","for","2025","register","false","tone","structure","use","webfetch","read","grep","why","how","issues","2026-11-10 10:12:30",false,"---\ncreated: 2025-12-16\nmodified: 2026-08-15\nreviewed: 2026-04-25\nname: ticket-drafting-guidelines\ndescription: \"What\u002FWhy\u002FHow prose structure and neutral, positive register for issues, PR descriptions, and tickets. Use when wording a ticket body, tightening prose, or applying house tone.\"\nuser-invocable: false\nallowed-tools: Read, Grep, WebFetch\n---\n\n# Ticket Drafting Guidelines\n\nExpert guidance for drafting clear, concise, and well-structured tickets for GitHub issues, pull requests, and technical documentation.\n\n## When to Use This Skill\n\n| Use this skill when... | Use google-chat-formatting instead when... |\n|---|---|\n| Drafting a GitHub issue, bug report, or feature request with What\u002FWhy\u002FHow structure | Posting a status update or announcement to a Google Chat channel |\n| Writing a PR description or technical ticket with reference links | Converting Markdown headers and bold to Google Chat's single-asterisk syntax |\n| Structuring a refactoring task or migration plan with concrete steps | Reformatting meeting notes or release notes for chat consumption |\n| Wording the body text — What\u002FWhy\u002FHow sections, tone, reference links | Use `git-plugin:github-issue-writing` for the GitHub issue artifact itself: `[Type] Component:` title format, bug\u002Ffeature templates, `gh issue create` |\n\n## Core Expertise\n\n- **Structured Format**: What\u002FWhy\u002FHow organization for clarity\n- **Concise Writing**: Brief descriptions with reference links\n- **Markdown Standards**: Proper formatting and link syntax\n- **Positive Framing**: Affirmative language without negative phrasing\n- **Neutral Tone**: Factual communication without claims or estimates\n- **Reference Integration**: Links to official documentation\n\n## Ticket Structure\n\n### Main Headings\n\nEvery ticket uses three primary sections:\n\n```markdown\n## What\n\n[Concise description of the subject]\n\n## Why\n\n[Context and motivation]\n\n## How\n\n[Implementation approach or resolution steps]\n```\n\n### What Section\n\n**Purpose**: Describe the subject clearly and concisely.\n\n**Guidelines:**\n- State what the ticket addresses in 1-3 sentences\n- Include relevant technical terms\n- Link to related issues or PRs using `[#123](URL)` format\n- Reference official documentation where applicable\n\n**Example:**\n```markdown\n## What\n\nAdd support for TypeScript configuration in the build pipeline. This enables type checking during CI\u002FCD runs and improves code quality. Related to [#456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F456).\n\nSee [TypeScript compiler options](https:\u002F\u002Fwww.typescriptlang.org\u002Ftsconfig) for configuration reference.\n```\n\n### Why Section\n\n**Purpose**: Explain the motivation and context.\n\n**Guidelines:**\n- Describe the problem or opportunity\n- Explain benefits of addressing this\n- Include relevant background information\n- Link to discussions or requirements docs\n\n**Example:**\n```markdown\n## Why\n\nCurrent build pipeline only validates JavaScript syntax. TypeScript type checking catches errors earlier in development and provides better IDE support. This reduces runtime errors and improves developer experience.\n\nThe team adopted TypeScript in [#234](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F234) but hasn't enabled type checking in CI yet.\n```\n\n### How Section\n\n**Purpose**: Outline the approach or solution.\n\n**Guidelines:**\n- Use simple bullet points\n- List concrete steps or components\n- Include technical details as needed\n- Reference implementation examples or patterns\n\n**Example:**\n```markdown\n## How\n\n- Add TypeScript compiler to CI workflow\n- Configure `tsconfig.json` with strict mode\n- Update GitHub Actions workflow to run `tsc --noEmit`\n- Document type checking process in CONTRIBUTING.md\n\nReference implementation: [GitHub Actions TypeScript](https:\u002F\u002Fgithub.com\u002Factions\u002Ftypescript-action)\n```\n\n## Formatting Standards\n\n### Markdown Elements\n\n**Headings:**\n```markdown\n## What\n### Subsection if needed\n```\n\n**Links:**\n```markdown\n[#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\n[PR #456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F456)\n[Official docs](https:\u002F\u002Fexample.com\u002Fdocs)\n```\n\n**Lists:**\n```markdown\n- Simple bullet points\n- One item per line\n- Clear and actionable\n```\n\n**Code blocks:**\n````markdown\n```language\ncode example here\n```\n````\n\n**Emphasis:**\n```markdown\n**bold** for important terms\n`code` for technical names\n```\n\n### Reference Links\n\nInclude links to:\n- Official documentation\n- Related issues and PRs\n- Relevant examples or patterns\n- API references or specifications\n\n**Format:**\n```markdown\nSee [TypeScript Configuration](https:\u002F\u002Fwww.typescriptlang.org\u002Ftsconfig) for details.\nRelated: [#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\nExample: [typescript-action](https:\u002F\u002Fgithub.com\u002Factions\u002Ftypescript-action)\n```\n\n## Writing Style\n\n### Positive Framing\n\n**Use affirmative language:**\n```markdown\n✅ Enable TypeScript type checking in CI\n✅ Add validation for user input\n✅ Implement caching for API responses\n```\n\n**Describe what to do rather than what not to do:**\n```markdown\n✅ Use environment variables for configuration\n✅ Validate input before processing\n✅ Handle errors with clear messages\n```\n\n### Neutral Tone\n\n**Maintain factual, objective language:**\n\n```markdown\n✅ \"This adds TypeScript support to the build pipeline\"\n❌ \"This amazing feature will revolutionize our build process\"\n\n✅ \"Enables type checking during CI runs\"\n❌ \"Dramatically improves code quality by 80%\"\n\n✅ \"Reduces configuration complexity\"\n❌ \"Makes configuration incredibly simple and super easy\"\n```\n\n**Key principles:**\n- State facts without exaggeration\n- Describe capabilities objectively\n- Provide context without making claims\n- Use measured language\n\n### Concise Descriptions\n\n**Keep content brief:**\n- 1-3 sentences per paragraph\n- Simple bullet lists\n- Direct language\n- Essential details only\n\n**Expand with links:**\n```markdown\n## What\n\nAdd Redis caching layer for API responses. This reduces database load and\nimproves response times. See [Redis documentation](https:\u002F\u002Fredis.io\u002Fdocs\u002F)\nfor architecture details.\n```\n\n### Progress and Estimates\n\n**What to include:**\n```markdown\n✅ Concrete steps or tasks\n✅ Components to implement\n✅ Dependencies between tasks\n```\n\n**Keep scope factual and concrete:**\n```markdown\n✅ Concrete steps or tasks\n✅ Measurable acceptance criteria\n✅ Observable behavior changes\n✅ Verifiable outcomes\n```\n\n**Example:**\n```markdown\n## How\n\n- Configure Redis connection\n- Implement cache middleware\n- Add cache invalidation logic\n- Update API handlers to use cache\n```\n\n## Complete Examples\n\nFull What\u002FWhy\u002FHow tickets for a feature request, a bug report, and a refactoring task: [references\u002Fcomplete-examples.md](references\u002Fcomplete-examples.md). Open it when drafting one of those ticket types from scratch.\n\n## Integration with Other Skills\n\nThis skill works alongside:\n\n- **Git Commit Workflow** - Consistent commit messages for ticket work\n- **Git Branch PR Workflow** - PR descriptions match ticket structure\n- **Release Please Protection** - References to automated changelog updates\n- **GitHub Actions** - CI\u002FCD workflow integration in tickets\n\n## Best Practices\n\n### Before Writing\n\n- Understand the full context\n- Identify relevant documentation\n- Find related issues or PRs\n- Note technical requirements\n\n### While Writing\n\n- Follow What\u002FWhy\u002FHow structure\n- Keep descriptions concise\n- Add reference links\n- Use positive framing\n- Maintain neutral tone\n\n### After Writing\n\n- Verify all links work\n- Check markdown rendering\n- Ensure clarity and completeness\n- Confirm positive language throughout\n\n## Common Patterns\n\n### Linking Issues and PRs\n\n```markdown\nRelated to [#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\nFixes [#456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F456)\nImplements [#789](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F789)\nSee [PR #234](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F234)\n```\n\n### Linking Documentation\n\n```markdown\nSee [official docs](https:\u002F\u002Fexample.com\u002Fdocs)\nReference: [API documentation](https:\u002F\u002Fapi.example.com)\nGuide: [configuration reference](https:\u002F\u002Fexample.com\u002Fconfig)\n```\n\n### Listing Steps\n\n```markdown\n- Single action per bullet\n- Clear and specific\n- Actionable items\n- Logical order\n```\n\n### Code References\n\n```markdown\nUpdate `config.ts` with new options\nModify the `handleRequest` function\nAdd tests in `auth.test.ts`\n```\n\n## Agentic Optimizations\n\n| Context | Command |\n|---------|---------|\n| List open issues for context | `gh issue list --state open --json number,title,labels --limit 10` |\n| View existing issue for reference | `gh issue view N --json number,title,body` |\n| Create issue from drafted content | `gh issue create --title \"title\" --body \"body\"` |\n| Find related issues | `gh search issues \"keyword\" --repo owner\u002Frepo --json number,title --limit 5` |\n| View PR template | `cat .github\u002FPULL_REQUEST_TEMPLATE.md` |\n\n## Skill Configuration\n\nLocated in `exact_dot_claude\u002Fskills\u002Fticket-drafting-guidelines\u002F` which becomes\n`~\u002F.claude\u002Fskills\u002Fticket-drafting-guidelines\u002F` after `chezmoi apply`:\n\n- `SKILL.md` - This file (skill definition and guidelines)\n\n## Success Indicators\n\nThis skill is working properly when:\n\n✅ Tickets follow What\u002FWhy\u002FHow structure consistently\n✅ Descriptions remain concise with reference links\n✅ Language uses positive framing throughout\n✅ Tone stays neutral without claims or estimates\n✅ Markdown formatting renders correctly\n✅ All links point to valid resources\n","# Ticket Drafting Guidelines\n\nExpert guidance for drafting clear, concise, and well-structured tickets for GitHub issues, pull requests, and technical documentation.\n\n## When to Use This Skill\n\n| Use this skill when... | Use google-chat-formatting instead when... |\n|---|---|\n| Drafting a GitHub issue, bug report, or feature request with What\u002FWhy\u002FHow structure | Posting a status update or announcement to a Google Chat channel |\n| Writing a PR description or technical ticket with reference links | Converting Markdown headers and bold to Google Chat's single-asterisk syntax |\n| Structuring a refactoring task or migration plan with concrete steps | Reformatting meeting notes or release notes for chat consumption |\n| Wording the body text — What\u002FWhy\u002FHow sections, tone, reference links | Use `git-plugin:github-issue-writing` for the GitHub issue artifact itself: `[Type] Component:` title format, bug\u002Ffeature templates, `gh issue create` |\n\n## Core Expertise\n\n- **Structured Format**: What\u002FWhy\u002FHow organization for clarity\n- **Concise Writing**: Brief descriptions with reference links\n- **Markdown Standards**: Proper formatting and link syntax\n- **Positive Framing**: Affirmative language without negative phrasing\n- **Neutral Tone**: Factual communication without claims or estimates\n- **Reference Integration**: Links to official documentation\n\n## Ticket Structure\n\n### Main Headings\n\nEvery ticket uses three primary sections:\n\n```markdown\n## What\n\n[Concise description of the subject]\n\n## Why\n\n[Context and motivation]\n\n## How\n\n[Implementation approach or resolution steps]\n```\n\n### What Section\n\n**Purpose**: Describe the subject clearly and concisely.\n\n**Guidelines:**\n- State what the ticket addresses in 1-3 sentences\n- Include relevant technical terms\n- Link to related issues or PRs using `[#123](URL)` format\n- Reference official documentation where applicable\n\n**Example:**\n```markdown\n## What\n\nAdd support for TypeScript configuration in the build pipeline. This enables type checking during CI\u002FCD runs and improves code quality. Related to [#456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F456).\n\nSee [TypeScript compiler options](https:\u002F\u002Fwww.typescriptlang.org\u002Ftsconfig) for configuration reference.\n```\n\n### Why Section\n\n**Purpose**: Explain the motivation and context.\n\n**Guidelines:**\n- Describe the problem or opportunity\n- Explain benefits of addressing this\n- Include relevant background information\n- Link to discussions or requirements docs\n\n**Example:**\n```markdown\n## Why\n\nCurrent build pipeline only validates JavaScript syntax. TypeScript type checking catches errors earlier in development and provides better IDE support. This reduces runtime errors and improves developer experience.\n\nThe team adopted TypeScript in [#234](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F234) but hasn't enabled type checking in CI yet.\n```\n\n### How Section\n\n**Purpose**: Outline the approach or solution.\n\n**Guidelines:**\n- Use simple bullet points\n- List concrete steps or components\n- Include technical details as needed\n- Reference implementation examples or patterns\n\n**Example:**\n```markdown\n## How\n\n- Add TypeScript compiler to CI workflow\n- Configure `tsconfig.json` with strict mode\n- Update GitHub Actions workflow to run `tsc --noEmit`\n- Document type checking process in CONTRIBUTING.md\n\nReference implementation: [GitHub Actions TypeScript](https:\u002F\u002Fgithub.com\u002Factions\u002Ftypescript-action)\n```\n\n## Formatting Standards\n\n### Markdown Elements\n\n**Headings:**\n```markdown\n## What\n### Subsection if needed\n```\n\n**Links:**\n```markdown\n[#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\n[PR #456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F456)\n[Official docs](https:\u002F\u002Fexample.com\u002Fdocs)\n```\n\n**Lists:**\n```markdown\n- Simple bullet points\n- One item per line\n- Clear and actionable\n```\n\n**Code blocks:**\n````markdown\n```language\ncode example here\n```\n````\n\n**Emphasis:**\n```markdown\n**bold** for important terms\n`code` for technical names\n```\n\n### Reference Links\n\nInclude links to:\n- Official documentation\n- Related issues and PRs\n- Relevant examples or patterns\n- API references or specifications\n\n**Format:**\n```markdown\nSee [TypeScript Configuration](https:\u002F\u002Fwww.typescriptlang.org\u002Ftsconfig) for details.\nRelated: [#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\nExample: [typescript-action](https:\u002F\u002Fgithub.com\u002Factions\u002Ftypescript-action)\n```\n\n## Writing Style\n\n### Positive Framing\n\n**Use affirmative language:**\n```markdown\n✅ Enable TypeScript type checking in CI\n✅ Add validation for user input\n✅ Implement caching for API responses\n```\n\n**Describe what to do rather than what not to do:**\n```markdown\n✅ Use environment variables for configuration\n✅ Validate input before processing\n✅ Handle errors with clear messages\n```\n\n### Neutral Tone\n\n**Maintain factual, objective language:**\n\n```markdown\n✅ \"This adds TypeScript support to the build pipeline\"\n❌ \"This amazing feature will revolutionize our build process\"\n\n✅ \"Enables type checking during CI runs\"\n❌ \"Dramatically improves code quality by 80%\"\n\n✅ \"Reduces configuration complexity\"\n❌ \"Makes configuration incredibly simple and super easy\"\n```\n\n**Key principles:**\n- State facts without exaggeration\n- Describe capabilities objectively\n- Provide context without making claims\n- Use measured language\n\n### Concise Descriptions\n\n**Keep content brief:**\n- 1-3 sentences per paragraph\n- Simple bullet lists\n- Direct language\n- Essential details only\n\n**Expand with links:**\n```markdown\n## What\n\nAdd Redis caching layer for API responses. This reduces database load and\nimproves response times. See [Redis documentation](https:\u002F\u002Fredis.io\u002Fdocs\u002F)\nfor architecture details.\n```\n\n### Progress and Estimates\n\n**What to include:**\n```markdown\n✅ Concrete steps or tasks\n✅ Components to implement\n✅ Dependencies between tasks\n```\n\n**Keep scope factual and concrete:**\n```markdown\n✅ Concrete steps or tasks\n✅ Measurable acceptance criteria\n✅ Observable behavior changes\n✅ Verifiable outcomes\n```\n\n**Example:**\n```markdown\n## How\n\n- Configure Redis connection\n- Implement cache middleware\n- Add cache invalidation logic\n- Update API handlers to use cache\n```\n\n## Complete Examples\n\nFull What\u002FWhy\u002FHow tickets for a feature request, a bug report, and a refactoring task: [references\u002Fcomplete-examples.md](references\u002Fcomplete-examples.md). Open it when drafting one of those ticket types from scratch.\n\n## Integration with Other Skills\n\nThis skill works alongside:\n\n- **Git Commit Workflow** - Consistent commit messages for ticket work\n- **Git Branch PR Workflow** - PR descriptions match ticket structure\n- **Release Please Protection** - References to automated changelog updates\n- **GitHub Actions** - CI\u002FCD workflow integration in tickets\n\n## Best Practices\n\n### Before Writing\n\n- Understand the full context\n- Identify relevant documentation\n- Find related issues or PRs\n- Note technical requirements\n\n### While Writing\n\n- Follow What\u002FWhy\u002FHow structure\n- Keep descriptions concise\n- Add reference links\n- Use positive framing\n- Maintain neutral tone\n\n### After Writing\n\n- Verify all links work\n- Check markdown rendering\n- Ensure clarity and completeness\n- Confirm positive language throughout\n\n## Common Patterns\n\n### Linking Issues and PRs\n\n```markdown\nRelated to [#123](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123)\nFixes [#456](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F456)\nImplements [#789](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F789)\nSee [PR #234](https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F234)\n```\n\n### Linking Documentation\n\n```markdown\nSee [official docs](https:\u002F\u002Fexample.com\u002Fdocs)\nReference: [API documentation](https:\u002F\u002Fapi.example.com)\nGuide: [configuration reference](https:\u002F\u002Fexample.com\u002Fconfig)\n```\n\n### Listing Steps\n\n```markdown\n- Single action per bullet\n- Clear and specific\n- Actionable items\n- Logical order\n```\n\n### Code References\n\n```markdown\nUpdate `config.ts` with new options\nModify the `handleRequest` function\nAdd tests in `auth.test.ts`\n```\n\n## Agentic Optimizations\n\n| Context | Command |\n|---------|---------|\n| List open issues for context | `gh issue list --state open --json number,title,labels --limit 10` |\n| View existing issue for reference | `gh issue view N --json number,title,body` |\n| Create issue from drafted content | `gh issue create --title \"title\" --body \"body\"` |\n| Find related issues | `gh search issues \"keyword\" --repo owner\u002Frepo --json number,title --limit 5` |\n| View PR template | `cat .github\u002FPULL_REQUEST_TEMPLATE.md` |\n\n## Skill Configuration\n\nLocated in `exact_dot_claude\u002Fskills\u002Fticket-drafting-guidelines\u002F` which becomes\n`~\u002F.claude\u002Fskills\u002Fticket-drafting-guidelines\u002F` after `chezmoi apply`:\n\n- `SKILL.md` - This file (skill definition and guidelines)\n\n## Success Indicators\n\nThis skill is working properly when:\n\n✅ Tickets follow What\u002FWhy\u002FHow structure consistently\n✅ Descriptions remain concise with reference links\n✅ Language uses positive framing throughout\n✅ Tone stays neutral without claims or estimates\n✅ Markdown formatting renders correctly\n✅ All links point to valid resources\n",{"name":5,"created":45,"modified":46,"reviewed":47,"description":7,"allowed-tools":48,"user-invocable":41},1765843200000,1786752000000,1777075200000,"Read, Grep, WebFetch","main","bdd0582f1a2ba53d21061835bfd72d45f2f954f4","communication-plugin\u002Fskills\u002Fticket-drafting-guidelines",6,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins","https:\u002F\u002Fgithub.com\u002Flaurigates","Linux enthusiast, cloud engineer, neovim addict, electronics hobbyist.","2026-11-13 20:24:11",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add laurigates\u002Fclaude-plugins --skill ticket-drafting-guidelines",{"tool":63,"command":64},"bunx","bunx skills add laurigates\u002Fclaude-plugins --skill ticket-drafting-guidelines",{"tool":66,"command":67},"pnpm","pnpm dlx skills add laurigates\u002Fclaude-plugins --skill ticket-drafting-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fcommunication-plugin\u002Fskills\u002Fticket-drafting-guidelines\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"README.md","REFERENCE","参考文档",2238,"https:\u002F\u002Fgithub.com\u002Fdmlguq456\u002Fhearting\u002Fblob\u002Fmain\u002Fadapters\u002Fclaude\u002Fskills\u002Fcode-test\u002FREADME.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fcomplete-examples.md",2578,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fcommunication-plugin\u002Fskills\u002Fticket-drafting-guidelines\u002Freferences\u002Fcomplete-examples.md",[82,110,130,146,169,199],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":40},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[94,95,96,97,98,99,100,101,102,103,33,25,104,105,106,107,108,109,23,35],"show","kitty show image","image","kitty","show image","ls","get","send","open","dev","Bash","file","text","with","xdg","via",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":40},"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",[],[97,117,118,119,30,120,25,104,121,122,123,23,35,124,125,126,127,128,129,33],"kitty session persistence","session","persistence","snapshots","uname","reboot","terminal","write","edit","snapshot","macos","sessions","restore",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":40},"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",[],[137,138,97,139,140,99,141,142,100,143,144,33,25,145,104,106,107,123,23,35],"kitty remote control","remote","control","remote control","running","never","panes","notify","query",{"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":40},"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",[],[153,154,155,156,157,158,159,160,161,162,33,25,104,163,105,164,165,166,167,168],"docs reference check","check","reference check","reference","docs","links","python3","repo","files","auto","drift","lint","wiring","chezmoi","references","cp",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":184,"publishedAt":40},"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",[175,178,179],{"categoryNo":176,"categoryName":177,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":180,"categoryName":181,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[185,186,187,188,159,189,35,190,125,191,192,193,33,104,105,194,195,25,196,197,198,109,23],"youtube upload","upload","youtube","Video","run","uv run","publishing","data","uv","api","v3","tags","id","title",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":208,"publishedAt":40},"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",[205],{"categoryNo":206,"categoryName":207,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发",[209,210,211,212,187,188,213,214,215,216,217,35,218,219,220,221,33,222,25,107,223,23],"youtube studio share","share","youtube studio","studio","browser","javascript","scripting","google workspace","workspace","tool","google","only","MCP","chrome","organization"]