[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JKX28FGQ2P52KJ305ZB0EP":3,"skill-same:01M6JKX28FGQ2P52KJ305ZB0EP":80},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6JKX28FGQ2P52KJ305ZB0EP","issue-creation",null,"Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fagent_teams_lite\u002Fpayload\u002Fskills\u002Fissue_creation\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],"issue creation","creation","issue","github issue","Agent Teams Lite","for","trigger","feature","bug","github","enforcement","agent teams","programming","system","first","reporting","teams","workflow","2026-11-10 10:12:30",false,"---\nname: issue-creation\ndescription: >\n  Issue creation workflow for Agent Teams Lite following the issue-first enforcement system.\n  Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n","## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n",{"name":5,"license":15,"metadata":47,"description":50},{"author":48,"version":49},"gentleman-programming","1.0","Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.\n","main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Fagent_teams_lite\u002Fpayload\u002Fskills\u002Fissue_creation",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-11-14 08:48:28",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add LongLeo287\u002FOmniClaw --skill issue-creation",{"tool":66,"command":67},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill issue-creation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill issue-creation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fagent_teams_lite\u002Fpayload\u002Fskills\u002Fissue_creation\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"_DIR_IDENTITY.md","REFERENCE","参考文档",357,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fagent_teams_lite\u002Fpayload\u002Fskills\u002Fissue_creation\u002F_DIR_IDENTITY.md",[81,121,142,170,186,213],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":100,"publishedAt":42},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[88,91,92,97],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000033","数据分析师",[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"ux","ui","ui ux pro max","max","pro","ui ux","design","component","search","analysis","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":42},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[127],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[129,102,130,131,108,132,133,134,135,111,136,137,138,114,139,140,141,29],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":151,"publishedAt":42},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,141,168,169],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":171,"name":153,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":42},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[153,176,159,177,160,178,179,162,180,164,181,182,183,154,141,184,185,168,169],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"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":85,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":42},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":42},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[197,220,221,203,222,223,224,225,226,227,228,229,230,231,232,233,234],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]