[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWBXHBKHME9DBPDMVBZQRT":3,"skill-same:01M7AWBXHBKHME9DBPDMVBZQRT":53},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7AWBXHBKHME9DBPDMVBZQRT","file-todos",null,"This skill should be used when managing the file-based todo tracking system in the todos\u002F directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.","barkleesanders\u002Fclaude-code-starter","barkleesanders","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30680901?v=4","01M7AW019CGBYWDA8MFJEN1JXC","Barklee Sanders","01M7AW01A5H994ASJ2QZPW67AV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Ffile-todos\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: file-todos\nuser-invocable: true\ndescription: This skill should be used when managing the file-based todo tracking system in the todos\u002F directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.\n---\n\n# File-Based Todo Tracking Skill\n\n## Overview\n\nThe `todos\u002F` directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.\n\nThis skill should be used when:\n- Creating new todos from findings or feedback\n- Managing todo lifecycle (pending → ready → complete)\n- Triaging pending items for approval\n- Checking or managing dependencies\n- Converting PR comments or code findings into tracked work\n- Updating work logs during todo execution\n\n## File Naming Convention\n\nTodo files follow this naming pattern:\n\n```\n{issue_id}-{status}-{priority}-{description}.md\n```\n\n**Components:**\n- **issue_id**: Sequential number (001, 002, 003...) - never reused\n- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)\n- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have)\n- **description**: kebab-case, brief description\n\n**Examples:**\n```\n001-pending-p1-mailer-test.md\n002-ready-p1-fix-n-plus-1.md\n005-complete-p2-refactor-csv.md\n```\n\n## File Structure\n\nEach todo is a markdown file with YAML frontmatter and structured sections. Use the template at [todo-template.md](.\u002Fassets\u002Ftodo-template.md) as a starting point when creating new todos.\n\n**Required sections:**\n- **Problem Statement** - What is broken, missing, or needs improvement?\n- **Findings** - Investigation results, root cause, key discoveries\n- **Proposed Solutions** - Multiple options with pros\u002Fcons, effort, risk\n- **Recommended Action** - Clear plan (filled during triage)\n- **Acceptance Criteria** - Testable checklist items\n- **Work Log** - Chronological record with date, actions, learnings\n\n**Optional sections:**\n- **Technical Details** - Affected files, related components, DB changes\n- **Resources** - Links to errors, tests, PRs, documentation\n- **Notes** - Additional context or decisions\n\n**YAML frontmatter fields:**\n```yaml\n---\nstatus: ready              # pending | ready | complete\npriority: p1              # p1 | p2 | p3\nissue_id: \"002\"\ntags: [rails, performance, database]\ndependencies: [\"001\"]     # Issue IDs this is blocked by\n---\n```\n\n## Common Workflows\n\n### Creating a New Todo\n\n**To create a new todo from findings or feedback:**\n\n1. Determine next issue ID: `ls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1`\n2. Copy template: `cp assets\u002Ftodo-template.md todos\u002F{NEXT_ID}-pending-{priority}-{description}.md`\n3. Edit and fill required sections:\n   - Problem Statement\n   - Findings (if from investigation)\n   - Proposed Solutions (multiple options)\n   - Acceptance Criteria\n   - Add initial Work Log entry\n4. Determine status: `pending` (needs triage) or `ready` (pre-approved)\n5. Add relevant tags for filtering\n\n**When to create a todo:**\n- Requires more than 15-20 minutes of work\n- Needs research, planning, or multiple approaches considered\n- Has dependencies on other work\n- Requires manager approval or prioritization\n- Part of larger feature or refactor\n- Technical debt needing documentation\n\n**When to act immediately instead:**\n- Issue is trivial (\u003C 15 minutes)\n- Complete context available now\n- No planning needed\n- User explicitly requests immediate action\n- Simple bug fix with obvious solution\n\n### Triaging Pending Items\n\n**To triage pending todos:**\n\n1. List pending items: `ls todos\u002F*-pending-*.md`\n2. For each todo:\n   - Read Problem Statement and Findings\n   - Review Proposed Solutions\n   - Make decision: approve, defer, or modify priority\n3. Update approved todos:\n   - Rename file: `mv {file}-pending-{pri}-{desc}.md {file}-ready-{pri}-{desc}.md`\n   - Update frontmatter: `status: pending` → `status: ready`\n   - Fill \"Recommended Action\" section with clear plan\n   - Adjust priority if different from initial assessment\n4. Deferred todos stay in `pending` status\n\n**Use slash command:** `\u002Ftriage` for interactive approval workflow\n\n### Managing Dependencies\n\n**To track dependencies:**\n\n```yaml\ndependencies: [\"002\", \"005\"]  # This todo blocked by issues 002 and 005\ndependencies: []               # No blockers - can work immediately\n```\n\n**To check what blocks a todo:**\n```bash\ngrep \"^dependencies:\" todos\u002F003-*.md\n```\n\n**To find what a todo blocks:**\n```bash\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**To verify blockers are complete before starting:**\n```bash\nfor dep in 001 002 003; do\n  [ -f \"todos\u002F${dep}-complete-*.md\" ] || echo \"Issue $dep not complete\"\ndone\n```\n\n### Updating Work Logs\n\n**When working on a todo, always add a work log entry:**\n\n```markdown\n### YYYY-MM-DD - Session Title\n\n**By:** Claude Code \u002F Developer Name\n\n**Actions:**\n- Specific changes made (include file:line references)\n- Commands executed\n- Tests run\n- Results of investigation\n\n**Learnings:**\n- What worked \u002F what didn't\n- Patterns discovered\n- Key insights for future work\n```\n\nWork logs serve as:\n- Historical record of investigation\n- Documentation of approaches attempted\n- Knowledge sharing for team\n- Context for future similar work\n\n### Completing a Todo\n\n**To mark a todo as complete:**\n\n1. Verify all acceptance criteria checked off\n2. Update Work Log with final session and results\n3. Rename file: `mv {file}-ready-{pri}-{desc}.md {file}-complete-{pri}-{desc}.md`\n4. Update frontmatter: `status: ready` → `status: complete`\n5. Check for unblocked work: `grep -l 'dependencies:.*\"002\"' todos\u002F*-ready-*.md`\n6. Commit with issue reference: `feat: resolve issue 002`\n\n## Integration with Development Workflows\n\n| Trigger | Flow | Tool |\n|---------|------|------|\n| Code review | `\u002Fworkflows:review` → Findings → `\u002Ftriage` → Todos | Review agent + skill |\n| PR comments | `\u002Fresolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |\n| Code TODOs | `\u002Fresolve_todo_parallel` → Fixes + Complex todos | Agent + skill |\n| Planning | Brainstorm → Create todo → Work → Complete | Skill |\n| Feedback | Discussion → Create todo → Triage → Work | Skill + slash |\n\n## Quick Reference Commands\n\n**Finding work:**\n```bash\n# List highest priority unblocked work\ngrep -l 'dependencies: \\[\\]' todos\u002F*-ready-p1-*.md\n\n# List all pending items needing triage\nls todos\u002F*-pending-*.md\n\n# Find next issue ID\nls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1 | awk '{printf \"%03d\", \\$1+1}'\n\n# Count by status\nfor status in pending ready complete; do\n  echo \"$status: $(ls -1 todos\u002F*-$status-*.md 2>\u002Fdev\u002Fnull | wc -l)\"\ndone\n```\n\n**Dependency management:**\n```bash\n# What blocks this todo?\ngrep \"^dependencies:\" todos\u002F003-*.md\n\n# What does this todo block?\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**Searching:**\n```bash\n# Search by tag\ngrep -l \"tags:.*rails\" todos\u002F*.md\n\n# Search by priority\nls todos\u002F*-p1-*.md\n\n# Full-text search\ngrep -r \"payment\" todos\u002F\n```\n\n## Key Distinctions\n\n**File-todos system (this skill):**\n- Markdown files in `todos\u002F` directory\n- Development\u002Fproject tracking\n- Standalone markdown files with YAML frontmatter\n- Used by humans and agents\n\n**Rails Todo model:**\n- Database model in `app\u002Fmodels\u002Ftodo.rb`\n- User-facing feature in the application\n- Active Record CRUD operations\n- Different from this file-based system\n\n**TodoWrite tool:**\n- In-memory task tracking during agent sessions\n- Temporary tracking for single conversation\n- Not persisted to disk\n- Different from both systems above\n","# File-Based Todo Tracking Skill\n\n## Overview\n\nThe `todos\u002F` directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.\n\nThis skill should be used when:\n- Creating new todos from findings or feedback\n- Managing todo lifecycle (pending → ready → complete)\n- Triaging pending items for approval\n- Checking or managing dependencies\n- Converting PR comments or code findings into tracked work\n- Updating work logs during todo execution\n\n## File Naming Convention\n\nTodo files follow this naming pattern:\n\n```\n{issue_id}-{status}-{priority}-{description}.md\n```\n\n**Components:**\n- **issue_id**: Sequential number (001, 002, 003...) - never reused\n- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)\n- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have)\n- **description**: kebab-case, brief description\n\n**Examples:**\n```\n001-pending-p1-mailer-test.md\n002-ready-p1-fix-n-plus-1.md\n005-complete-p2-refactor-csv.md\n```\n\n## File Structure\n\nEach todo is a markdown file with YAML frontmatter and structured sections. Use the template at [todo-template.md](.\u002Fassets\u002Ftodo-template.md) as a starting point when creating new todos.\n\n**Required sections:**\n- **Problem Statement** - What is broken, missing, or needs improvement?\n- **Findings** - Investigation results, root cause, key discoveries\n- **Proposed Solutions** - Multiple options with pros\u002Fcons, effort, risk\n- **Recommended Action** - Clear plan (filled during triage)\n- **Acceptance Criteria** - Testable checklist items\n- **Work Log** - Chronological record with date, actions, learnings\n\n**Optional sections:**\n- **Technical Details** - Affected files, related components, DB changes\n- **Resources** - Links to errors, tests, PRs, documentation\n- **Notes** - Additional context or decisions\n\n**YAML frontmatter fields:**\n```yaml\n---\nstatus: ready              # pending | ready | complete\npriority: p1              # p1 | p2 | p3\nissue_id: \"002\"\ntags: [rails, performance, database]\ndependencies: [\"001\"]     # Issue IDs this is blocked by\n---\n```\n\n## Common Workflows\n\n### Creating a New Todo\n\n**To create a new todo from findings or feedback:**\n\n1. Determine next issue ID: `ls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1`\n2. Copy template: `cp assets\u002Ftodo-template.md todos\u002F{NEXT_ID}-pending-{priority}-{description}.md`\n3. Edit and fill required sections:\n   - Problem Statement\n   - Findings (if from investigation)\n   - Proposed Solutions (multiple options)\n   - Acceptance Criteria\n   - Add initial Work Log entry\n4. Determine status: `pending` (needs triage) or `ready` (pre-approved)\n5. Add relevant tags for filtering\n\n**When to create a todo:**\n- Requires more than 15-20 minutes of work\n- Needs research, planning, or multiple approaches considered\n- Has dependencies on other work\n- Requires manager approval or prioritization\n- Part of larger feature or refactor\n- Technical debt needing documentation\n\n**When to act immediately instead:**\n- Issue is trivial (\u003C 15 minutes)\n- Complete context available now\n- No planning needed\n- User explicitly requests immediate action\n- Simple bug fix with obvious solution\n\n### Triaging Pending Items\n\n**To triage pending todos:**\n\n1. List pending items: `ls todos\u002F*-pending-*.md`\n2. For each todo:\n   - Read Problem Statement and Findings\n   - Review Proposed Solutions\n   - Make decision: approve, defer, or modify priority\n3. Update approved todos:\n   - Rename file: `mv {file}-pending-{pri}-{desc}.md {file}-ready-{pri}-{desc}.md`\n   - Update frontmatter: `status: pending` → `status: ready`\n   - Fill \"Recommended Action\" section with clear plan\n   - Adjust priority if different from initial assessment\n4. Deferred todos stay in `pending` status\n\n**Use slash command:** `\u002Ftriage` for interactive approval workflow\n\n### Managing Dependencies\n\n**To track dependencies:**\n\n```yaml\ndependencies: [\"002\", \"005\"]  # This todo blocked by issues 002 and 005\ndependencies: []               # No blockers - can work immediately\n```\n\n**To check what blocks a todo:**\n```bash\ngrep \"^dependencies:\" todos\u002F003-*.md\n```\n\n**To find what a todo blocks:**\n```bash\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**To verify blockers are complete before starting:**\n```bash\nfor dep in 001 002 003; do\n  [ -f \"todos\u002F${dep}-complete-*.md\" ] || echo \"Issue $dep not complete\"\ndone\n```\n\n### Updating Work Logs\n\n**When working on a todo, always add a work log entry:**\n\n```markdown\n### YYYY-MM-DD - Session Title\n\n**By:** Claude Code \u002F Developer Name\n\n**Actions:**\n- Specific changes made (include file:line references)\n- Commands executed\n- Tests run\n- Results of investigation\n\n**Learnings:**\n- What worked \u002F what didn't\n- Patterns discovered\n- Key insights for future work\n```\n\nWork logs serve as:\n- Historical record of investigation\n- Documentation of approaches attempted\n- Knowledge sharing for team\n- Context for future similar work\n\n### Completing a Todo\n\n**To mark a todo as complete:**\n\n1. Verify all acceptance criteria checked off\n2. Update Work Log with final session and results\n3. Rename file: `mv {file}-ready-{pri}-{desc}.md {file}-complete-{pri}-{desc}.md`\n4. Update frontmatter: `status: ready` → `status: complete`\n5. Check for unblocked work: `grep -l 'dependencies:.*\"002\"' todos\u002F*-ready-*.md`\n6. Commit with issue reference: `feat: resolve issue 002`\n\n## Integration with Development Workflows\n\n| Trigger | Flow | Tool |\n|---------|------|------|\n| Code review | `\u002Fworkflows:review` → Findings → `\u002Ftriage` → Todos | Review agent + skill |\n| PR comments | `\u002Fresolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |\n| Code TODOs | `\u002Fresolve_todo_parallel` → Fixes + Complex todos | Agent + skill |\n| Planning | Brainstorm → Create todo → Work → Complete | Skill |\n| Feedback | Discussion → Create todo → Triage → Work | Skill + slash |\n\n## Quick Reference Commands\n\n**Finding work:**\n```bash\n# List highest priority unblocked work\ngrep -l 'dependencies: \\[\\]' todos\u002F*-ready-p1-*.md\n\n# List all pending items needing triage\nls todos\u002F*-pending-*.md\n\n# Find next issue ID\nls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1 | awk '{printf \"%03d\", \\$1+1}'\n\n# Count by status\nfor status in pending ready complete; do\n  echo \"$status: $(ls -1 todos\u002F*-$status-*.md 2>\u002Fdev\u002Fnull | wc -l)\"\ndone\n```\n\n**Dependency management:**\n```bash\n# What blocks this todo?\ngrep \"^dependencies:\" todos\u002F003-*.md\n\n# What does this todo block?\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**Searching:**\n```bash\n# Search by tag\ngrep -l \"tags:.*rails\" todos\u002F*.md\n\n# Search by priority\nls todos\u002F*-p1-*.md\n\n# Full-text search\ngrep -r \"payment\" todos\u002F\n```\n\n## Key Distinctions\n\n**File-todos system (this skill):**\n- Markdown files in `todos\u002F` directory\n- Development\u002Fproject tracking\n- Standalone markdown files with YAML frontmatter\n- Used by humans and agents\n\n**Rails Todo model:**\n- Database model in `app\u002Fmodels\u002Ftodo.rb`\n- User-facing feature in the application\n- Active Record CRUD operations\n- Different from this file-based system\n\n**TodoWrite tool:**\n- In-memory task tracking during agent sessions\n- Temporary tracking for single conversation\n- Not persisted to disk\n- Different from both systems above\n",{"name":5,"description":7,"user-invocable":24},true,"main","e7b39d448c7d905feed2b044d3ccdf60822596ab","skills\u002Ffile-todos",0,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter","https:\u002F\u002Fgithub.com\u002Fbarkleesanders","barkleesanders.com","Stay Hungry, Stay Foolish","2026-11-06 08:47:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add barkleesanders\u002Fclaude-code-starter --skill file-todos",{"tool":40,"command":41},"bunx","bunx skills add barkleesanders\u002Fclaude-code-starter --skill file-todos",{"tool":43,"command":44},"pnpm","pnpm dlx skills add barkleesanders\u002Fclaude-code-starter --skill file-todos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Ffile-todos\u002FSKILL.md",[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Ftodo-template.md","ASSET","资产文件",3735,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Ffile-todos\u002Fassets\u002Ftodo-template.md",[54,60,67,74,81,88],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AWV75B37B6YKG7ZKGZ783F","zi-search","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fzi-search\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AWTZA3JGK1T7V1HS543FG7","visualise","Render inline interactive visuals — SVG diagrams, HTML widgets, charts, and explainers — directly in the conversation. Use this skill whenever the user asks to visualize, diagram, chart, illustrate, or explain something visually, or when an explanation would genuinely benefit from a spatial\u002Finteractive diagram rather than text. Also triggers for: flowcharts, architecture diagrams, data visualizations, interactive explainers, comparison layouts, UI mockups, and any request containing 'show me', 'draw', 'map out', 'visualize', or 'diagram'. Even when the user doesn't explicitly ask for a visual, use this skill proactively when the topic has spatial, sequential, or systemic relationships that a diagram would clarify better than prose.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvisualise\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AWTR056C3P9R3VS8YVM2WX","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AWTHTWBMTYZPMHHEYX3TTG","manim-video","Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric\u002Fmathematical content.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002Fskills\u002Fmanim-video\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AWTCXDJ9NWFQW51ENM8A2Z","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AWTA1D5FP895S33GHSA2G5","ui-improver","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fui-improver\u002FSKILL.md",[],[]]