[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M737PB8BYAW5MMTMEH2VD9J3":3,"skill-same:01M737PB8BYAW5MMTMEH2VD9J3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M737PB8BYAW5MMTMEH2VD9J3","skill-069",null,"PR description templates with format specifications and examples. Use when generating PR descriptions. Provides the complete PR structure and writing guidance.","legendtkl\u002Fagentic-skill-router","legendtkl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2370761?v=4","01M71RR3WRQC40G964Q2GVDMND","01M737GJZQ9TF1VE3VM255EDAK",8,"MIT","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fexperiments\u002Fdci-compare\u002Fskillrouter-skills\u002Fskill-069\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: skill-069\ndescription: \"PR description templates with format specifications and examples. Use when generating PR descriptions. Provides the complete PR structure and writing guidance.\"\n---\n\n# PR Description Template Skill\n\nThis skill provides everything needed to write high-quality PR descriptions: templates, format specifications, and examples.\n\n## Quick Reference\n\n| Command | Description |\n|---------|-------------|\n| `\u002Fpr-description-template` | Show available templates and help |\n| `\u002Fpr-description-template feature` | Example PR for new feature implementations |\n| `\u002Fpr-description-template bugfix` | Example PR for bug fixes |\n| `\u002Fpr-description-template refactor` | Example PR for refactoring\u002Farchitectural changes |\n| `\u002Fpr-description-template format` | Show complete PR description format |\n\n---\n\n## Available Templates\n\n| Template | Use For | Characteristics |\n|----------|---------|-----------------|\n| **feature** | New functionality, APIs, components | Emphasizes scope, design decisions, future work |\n| **bugfix** | Bug fixes, regressions, hotfixes | Emphasizes root cause, testing, before\u002Fafter |\n| **refactor** | Architectural changes, code restructuring | Emphasizes compatibility, migration, incremental changes |\n\n### Template Selection Guide\n\n**Choose `feature` when:**\n- Adding new functionality (greenfield development)\n- Implementing new APIs, services, or components\n- Adding new user-facing features\n- Introducing new capabilities to the codebase\n\n**Choose `bugfix` when:**\n- Fixing a bug of any size\n- Addressing regressions\n- Hotfixes for production issues\n- Correcting unexpected behavior\n\n**Choose `refactor` when:**\n- Making architectural changes\n- Restructuring code without changing behavior\n- Reorganizing modules or file structure\n- Implementing breaking changes with migration\n- Improving code quality without adding features\n\n---\n\n## PR Description Format\n\n**Every PR description MUST follow this structure.** This is the canonical format for all pull requests.\n\n### Required Sections\n\n```markdown\n## Summary\n\n\u003CHigh-level summary of changes and context for why the changes were made.\nShould answer: What does this PR do? Why is it needed?\nKeep to 2-4 sentences. Focus on business value and user impact.>\n\n## What's Included\n\n\u003CCompact list organized by category to help reviewer understand scope at a glance>\n\n**Source Code:**\n- `path\u002Fto\u002Ffile.py` - Brief description of change\n\n**Tests:**\n- `tests\u002Ftest_file.py` - What's being tested\n\n**Documentation:**\n- `docs\u002Ffile.md` - What was documented (or note if missing)\n\n**Configuration:**\n- `pyproject.toml` - Dependencies added\u002Fchanged\n\n## Key Design Decisions\n\n\u003CDesign decisions to document for reviewer context.\nFocus on \"why this approach\" not implementation details.\nNumber each decision for easy reference in review comments.>\n\n1. **Decision Title**: Rationale for why this approach was chosen over alternatives\n\n2. **Convention Deviation** (if any): Any intentional deviations from development-conventions with justification\n\n## Critical Areas for Review\n\n\u003CPrioritized areas deserving careful review.\nHelp reviewer focus their attention on what matters most.\nInclude line numbers when specific ranges need attention.>\n\n1. **`path\u002Fto\u002Fcritical\u002Ffile.py:L10-L50`** - Description of why this needs careful review (e.g., complex logic, security implications, breaking change)\n\n2. **`path\u002Fto\u002Fanother\u002Ffile.py`** - Why this is important to review\n```\n\n### Optional Sections\n\nInclude these when applicable:\n\n```markdown\n## Future Phases\n\n\u003COnly include if this PR is a partial implementation of a larger plan>\n\nThe following phases from the [implementation plan](\u003Cplan-path>) are planned for future PRs:\n- **Phase N**: Brief description of what's coming\n- **Phase M**: Brief description of what's coming\n\n## Breaking Changes\n\n\u003COnly include if there are breaking changes>\n\n- **Change**: Description of what breaks\n- **Migration**: How to update dependent code\n- **Deprecation Timeline**: When old behavior will be removed (if applicable)\n\n## Testing Notes\n\n\u003COnly include if testing requires special setup or has important caveats>\n\n- How to test locally\n- Required environment setup\n- Known edge cases\n```\n\n---\n\n## Writing Guidelines\n\n### Summary Section\n\n**DO:**\n- Start with what the PR accomplishes (the \"what\")\n- Explain why it's needed (the \"why\")\n- Mention user-facing impact if applicable\n- Keep it concise (2-4 sentences)\n\n**DON'T:**\n- List files changed (that's for \"What's Included\")\n- Include implementation details\n- Use vague language like \"various improvements\"\n- Make it longer than a short paragraph\n\n**Good Example:**\n> Adds batch processing support for the data pipeline, enabling processing of up to 10,000 records in a single operation. This addresses the performance bottleneck reported in issue #123 where large datasets caused timeouts.\n\n**Bad Example:**\n> This PR updates processor.py and adds tests. Made some improvements to the code.\n\n### What's Included Section\n\n**DO:**\n- Group by file type (Source, Tests, Documentation, Configuration)\n- Use relative paths from repository root\n- Keep descriptions to one line per file\n- Highlight new files vs modified files if helpful\n\n**DON'T:**\n- Include every file if there are many (summarize: \"15 test files for new validators\")\n- Add excessive detail (save that for design decisions)\n- Forget to mention documentation updates (or note \"Documentation: None\" if appropriate)\n\n### Key Design Decisions Section\n\n**DO:**\n- Number decisions for easy reference in reviews\n- Explain the \"why\" not the \"what\"\n- Mention alternatives considered when relevant\n- Flag any convention deviations with justification\n\n**DON'T:**\n- Repeat implementation details\n- Include decisions that are obvious\n- Skip this section (even simple PRs have at least one decision worth noting)\n\n### Critical Areas for Review Section\n\n**DO:**\n- Prioritize areas by importance\n- Include line numbers for specific ranges\n- Explain WHY each area needs attention\n- Mention security, complexity, or breaking change concerns\n\n**DON'T:**\n- List every file (only truly critical areas)\n- Be vague (\"please review carefully\")\n- Skip this section (helps reviewers use their time effectively)\n\n---\n\n## Title Guidelines\n\nPR titles should be concise and descriptive:\n\n**Format:** `\u003Ctype>: \u003Cbrief description>`\n\n**Types:**\n- `feat:` - New feature\n- `fix:` - Bug fix\n- `refactor:` - Code restructuring\n- `docs:` - Documentation only\n- `test:` - Test additions\u002Fchanges\n- `chore:` - Maintenance tasks\n\n**Good Examples:**\n- `feat: Add batch processing for data pipeline`\n- `fix: Resolve timeout on large dataset uploads`\n- `refactor: Extract validation logic into separate module`\n\n**Bad Examples:**\n- `Update files` (too vague)\n- `Fix bug` (what bug?)\n- `WIP` (not ready for review)\n\n---\n\n## Action Instructions\n\nBased on the argument provided, perform one of these actions:\n\n### `\u002Fpr-description-template` (no args) or `\u002Fpr-description-template help`\nShow this overview with available templates and commands.\n\n### `\u002Fpr-description-template feature`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-feature.md`\n\n### `\u002Fpr-description-template bugfix`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-bugfix.md`\n\n### `\u002Fpr-description-template refactor`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-refactor.md`\n\n### `\u002Fpr-description-template format`\nDisplay the \"PR Description Format\" section from this skill.\n\n---\n\n## Template File Locations\n\nAll example templates are in this skill directory:\n\n- `example-feature.md` - Complete example for new feature PRs\n- `example-bugfix.md` - Complete example for bug fix PRs\n- `example-refactor.md` - Complete example for refactoring PRs","# PR Description Template Skill\n\nThis skill provides everything needed to write high-quality PR descriptions: templates, format specifications, and examples.\n\n## Quick Reference\n\n| Command | Description |\n|---------|-------------|\n| `\u002Fpr-description-template` | Show available templates and help |\n| `\u002Fpr-description-template feature` | Example PR for new feature implementations |\n| `\u002Fpr-description-template bugfix` | Example PR for bug fixes |\n| `\u002Fpr-description-template refactor` | Example PR for refactoring\u002Farchitectural changes |\n| `\u002Fpr-description-template format` | Show complete PR description format |\n\n---\n\n## Available Templates\n\n| Template | Use For | Characteristics |\n|----------|---------|-----------------|\n| **feature** | New functionality, APIs, components | Emphasizes scope, design decisions, future work |\n| **bugfix** | Bug fixes, regressions, hotfixes | Emphasizes root cause, testing, before\u002Fafter |\n| **refactor** | Architectural changes, code restructuring | Emphasizes compatibility, migration, incremental changes |\n\n### Template Selection Guide\n\n**Choose `feature` when:**\n- Adding new functionality (greenfield development)\n- Implementing new APIs, services, or components\n- Adding new user-facing features\n- Introducing new capabilities to the codebase\n\n**Choose `bugfix` when:**\n- Fixing a bug of any size\n- Addressing regressions\n- Hotfixes for production issues\n- Correcting unexpected behavior\n\n**Choose `refactor` when:**\n- Making architectural changes\n- Restructuring code without changing behavior\n- Reorganizing modules or file structure\n- Implementing breaking changes with migration\n- Improving code quality without adding features\n\n---\n\n## PR Description Format\n\n**Every PR description MUST follow this structure.** This is the canonical format for all pull requests.\n\n### Required Sections\n\n```markdown\n## Summary\n\n\u003CHigh-level summary of changes and context for why the changes were made.\nShould answer: What does this PR do? Why is it needed?\nKeep to 2-4 sentences. Focus on business value and user impact.>\n\n## What's Included\n\n\u003CCompact list organized by category to help reviewer understand scope at a glance>\n\n**Source Code:**\n- `path\u002Fto\u002Ffile.py` - Brief description of change\n\n**Tests:**\n- `tests\u002Ftest_file.py` - What's being tested\n\n**Documentation:**\n- `docs\u002Ffile.md` - What was documented (or note if missing)\n\n**Configuration:**\n- `pyproject.toml` - Dependencies added\u002Fchanged\n\n## Key Design Decisions\n\n\u003CDesign decisions to document for reviewer context.\nFocus on \"why this approach\" not implementation details.\nNumber each decision for easy reference in review comments.>\n\n1. **Decision Title**: Rationale for why this approach was chosen over alternatives\n\n2. **Convention Deviation** (if any): Any intentional deviations from development-conventions with justification\n\n## Critical Areas for Review\n\n\u003CPrioritized areas deserving careful review.\nHelp reviewer focus their attention on what matters most.\nInclude line numbers when specific ranges need attention.>\n\n1. **`path\u002Fto\u002Fcritical\u002Ffile.py:L10-L50`** - Description of why this needs careful review (e.g., complex logic, security implications, breaking change)\n\n2. **`path\u002Fto\u002Fanother\u002Ffile.py`** - Why this is important to review\n```\n\n### Optional Sections\n\nInclude these when applicable:\n\n```markdown\n## Future Phases\n\n\u003COnly include if this PR is a partial implementation of a larger plan>\n\nThe following phases from the [implementation plan](\u003Cplan-path>) are planned for future PRs:\n- **Phase N**: Brief description of what's coming\n- **Phase M**: Brief description of what's coming\n\n## Breaking Changes\n\n\u003COnly include if there are breaking changes>\n\n- **Change**: Description of what breaks\n- **Migration**: How to update dependent code\n- **Deprecation Timeline**: When old behavior will be removed (if applicable)\n\n## Testing Notes\n\n\u003COnly include if testing requires special setup or has important caveats>\n\n- How to test locally\n- Required environment setup\n- Known edge cases\n```\n\n---\n\n## Writing Guidelines\n\n### Summary Section\n\n**DO:**\n- Start with what the PR accomplishes (the \"what\")\n- Explain why it's needed (the \"why\")\n- Mention user-facing impact if applicable\n- Keep it concise (2-4 sentences)\n\n**DON'T:**\n- List files changed (that's for \"What's Included\")\n- Include implementation details\n- Use vague language like \"various improvements\"\n- Make it longer than a short paragraph\n\n**Good Example:**\n> Adds batch processing support for the data pipeline, enabling processing of up to 10,000 records in a single operation. This addresses the performance bottleneck reported in issue #123 where large datasets caused timeouts.\n\n**Bad Example:**\n> This PR updates processor.py and adds tests. Made some improvements to the code.\n\n### What's Included Section\n\n**DO:**\n- Group by file type (Source, Tests, Documentation, Configuration)\n- Use relative paths from repository root\n- Keep descriptions to one line per file\n- Highlight new files vs modified files if helpful\n\n**DON'T:**\n- Include every file if there are many (summarize: \"15 test files for new validators\")\n- Add excessive detail (save that for design decisions)\n- Forget to mention documentation updates (or note \"Documentation: None\" if appropriate)\n\n### Key Design Decisions Section\n\n**DO:**\n- Number decisions for easy reference in reviews\n- Explain the \"why\" not the \"what\"\n- Mention alternatives considered when relevant\n- Flag any convention deviations with justification\n\n**DON'T:**\n- Repeat implementation details\n- Include decisions that are obvious\n- Skip this section (even simple PRs have at least one decision worth noting)\n\n### Critical Areas for Review Section\n\n**DO:**\n- Prioritize areas by importance\n- Include line numbers for specific ranges\n- Explain WHY each area needs attention\n- Mention security, complexity, or breaking change concerns\n\n**DON'T:**\n- List every file (only truly critical areas)\n- Be vague (\"please review carefully\")\n- Skip this section (helps reviewers use their time effectively)\n\n---\n\n## Title Guidelines\n\nPR titles should be concise and descriptive:\n\n**Format:** `\u003Ctype>: \u003Cbrief description>`\n\n**Types:**\n- `feat:` - New feature\n- `fix:` - Bug fix\n- `refactor:` - Code restructuring\n- `docs:` - Documentation only\n- `test:` - Test additions\u002Fchanges\n- `chore:` - Maintenance tasks\n\n**Good Examples:**\n- `feat: Add batch processing for data pipeline`\n- `fix: Resolve timeout on large dataset uploads`\n- `refactor: Extract validation logic into separate module`\n\n**Bad Examples:**\n- `Update files` (too vague)\n- `Fix bug` (what bug?)\n- `WIP` (not ready for review)\n\n---\n\n## Action Instructions\n\nBased on the argument provided, perform one of these actions:\n\n### `\u002Fpr-description-template` (no args) or `\u002Fpr-description-template help`\nShow this overview with available templates and commands.\n\n### `\u002Fpr-description-template feature`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-feature.md`\n\n### `\u002Fpr-description-template bugfix`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-bugfix.md`\n\n### `\u002Fpr-description-template refactor`\nRead and display: `.claude\u002Fskills\u002Fpr-description-template\u002Fexample-refactor.md`\n\n### `\u002Fpr-description-template format`\nDisplay the \"PR Description Format\" section from this skill.\n\n---\n\n## Template File Locations\n\nAll example templates are in this skill directory:\n\n- `example-feature.md` - Complete example for new feature PRs\n- `example-bugfix.md` - Complete example for bug fix PRs\n- `example-refactor.md` - Complete example for refactoring PRs",{"name":5,"description":7},"main","160b30f0b67c923077f886376fdfae1016a70702","experiments\u002Fdci-compare\u002Fskillrouter-skills\u002Fskill-069",2,"https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router","https:\u002F\u002Flegendtkl.github.io\u002Fagentic-skill-router\u002F","https:\u002F\u002Fgithub.com\u002Flegendtkl","http:\u002F\u002Fwww.legendtkl.com","No secret before debugging.\r\n","2026-06-04 14:02:56",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add legendtkl\u002Fagentic-skill-router --skill skill-069",{"tool":39,"command":40},"bunx","bunx skills add legendtkl\u002Fagentic-skill-router --skill skill-069",{"tool":42,"command":43},"pnpm","pnpm dlx skills add legendtkl\u002Fagentic-skill-router --skill skill-069","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fexperiments\u002Fdci-compare\u002Fskillrouter-skills\u002Fskill-069\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M7384EP28XVSR2R0YGRS0GK9","foo","A test skill named foo","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ffoo\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7384DECF306RRRC16PZJTQ5","bar","飞书 — bar with quoted Chinese","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fbar\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M738491441AQ85E7GD7VVDTA","agentic-skill-router","First use any clearly matching enabled local\u002Fuser Agent Skill. If none matches, prefer this router for skill-shaped requests involving a named tool, API, service, CLI, platform, file format, dataset, or domain workflow, including when a generic built-in skill such as browser, Chrome, or web search also seems applicable; use built-ins directly only when explicitly requested or when the task is primarily live browsing, logged-in page operation, clicking, screenshotting, or current webpage inspection. Also use directly to audit, slim, disable, restore, or route locally installed Agent Skills across supported hosts. Examples include Vercel, Netlify, Cloudflare, Render, Playwright, Sentry, Linear, GitHub, OpenAI APIs, PDF, DOCX, PPTX, and spreadsheets.","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fskills\u002Fagentic-skill-router\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M738475HF7SXTP4HCPZJVZ8E","syn-video-trim","Skill for trimming and cutting clips in the context of video files. Use when the user's task is specifically about trimming and cutting clips.","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fexperiments\u002Fdci-compare\u002Fsynthetic-skills\u002Fsyn-video-trim\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M73845F4RD2AA6YHS1E3VQRB","syn-video-transcode","Skill for transcoding codecs and resolutions in the context of video files. Use when the user's task is specifically about transcoding codecs and resolutions.","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fexperiments\u002Fdci-compare\u002Fsynthetic-skills\u002Fsyn-video-transcode\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M73842YN17QSJETPZX6Z9DAG","syn-video-thumbnail","Skill for extracting thumbnails and frames in the context of video files. Use when the user's task is specifically about extracting thumbnails and frames.","https:\u002F\u002Fgithub.com\u002Flegendtkl\u002Fagentic-skill-router\u002Fblob\u002Fmain\u002Fexperiments\u002Fdci-compare\u002Fsynthetic-skills\u002Fsyn-video-thumbnail\u002FSKILL.md",[],[]]