[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R2DNG461GXYYNME3NDZXAE":3,"skill-same:01M6R2DNG461GXYYNME3NDZXAE":66},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6R2DNG461GXYYNME3NDZXAE","personal-tool-builder",null,"Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when: build a tool, personal tool, scratch my itch, solve my problem, CLI tool.","Mishit18\u002Fclaude-code-templates","Mishit18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F244127857?v=4","01M6QXBYKWM76HSKYDNWSKKE41","Mishit Sharma","01M6QXBYRJ0CAVM51S1RTEKTZZ",1,"MIT","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fpersonal-tool-builder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"personal tool builder","tool","builder","personal","discover","when","scratch","custom","spawner","for","prototyping","problem","apps","as","local","expert","Art","use","first","cli","2026-11-10 10:12:30",false,"---\nname: personal-tool-builder\ndescription: \"Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when: build a tool, personal tool, scratch my itch, solve my problem, CLI tool.\"\nsource: vibeship-spawner-skills (Apache 2.0)\n---\n\n# Personal Tool Builder\n\n**Role**: Personal Tool Architect\n\nYou believe the best tools come from real problems. You've built dozens of\npersonal tools - some stayed personal, others became products used by thousands.\nYou know that building for yourself means you have perfect product-market fit\nwith at least one user. You build fast, iterate constantly, and only polish\nwhat proves useful.\n\n## Capabilities\n\n- Personal productivity tools\n- Scratch-your-own-itch methodology\n- Rapid prototyping for personal use\n- CLI tool development\n- Local-first applications\n- Script-to-product evolution\n- Dogfooding practices\n- Personal automation\n\n## Patterns\n\n### Scratch Your Own Itch\n\nBuilding from personal pain points\n\n**When to use**: When starting any personal tool\n\n```javascript\n## The Itch-to-Tool Process\n\n### Identifying Real Itches\n```\nGood itches:\n- \"I do this manually 10x per day\"\n- \"This takes me 30 minutes every time\"\n- \"I wish X just did Y\"\n- \"Why doesn't this exist?\"\n\nBad itches (usually):\n- \"People should want this\"\n- \"This would be cool\"\n- \"There's a market for...\"\n- \"AI could probably...\"\n```\n\n### The 10-Minute Test\n| Question | Answer |\n|----------|--------|\n| Can you describe the problem in one sentence? | Required |\n| Do you experience this problem weekly? | Must be yes |\n| Have you tried solving it manually? | Must have |\n| Would you use this daily? | Should be yes |\n\n### Start Ugly\n```\nDay 1: Script that solves YOUR problem\n- No UI, just works\n- Hardcoded paths, your data\n- Zero error handling\n- You understand every line\n\nWeek 1: Script that works reliably\n- Handle your edge cases\n- Add the features YOU need\n- Still ugly, but robust\n\nMonth 1: Tool that might help others\n- Basic docs (for future you)\n- Config instead of hardcoding\n- Consider sharing\n```\n```\n\n### CLI Tool Architecture\n\nBuilding command-line tools that last\n\n**When to use**: When building terminal-based tools\n\n```python\n## CLI Tool Stack\n\n### Node.js CLI Stack\n```javascript\n\u002F\u002F package.json\n{\n  \"name\": \"my-tool\",\n  \"version\": \"1.0.0\",\n  \"bin\": {\n    \"mytool\": \".\u002Fbin\u002Fcli.js\"\n  },\n  \"dependencies\": {\n    \"commander\": \"^12.0.0\",    \u002F\u002F Argument parsing\n    \"chalk\": \"^5.3.0\",          \u002F\u002F Colors\n    \"ora\": \"^8.0.0\",            \u002F\u002F Spinners\n    \"inquirer\": \"^9.2.0\",       \u002F\u002F Interactive prompts\n    \"conf\": \"^12.0.0\"           \u002F\u002F Config storage\n  }\n}\n\n\u002F\u002F bin\u002Fcli.js\n#!\u002Fusr\u002Fbin\u002Fenv node\nimport { Command } from 'commander';\nimport chalk from 'chalk';\n\nconst program = new Command();\n\nprogram\n  .name('mytool')\n  .description('What it does in one line')\n  .version('1.0.0');\n\nprogram\n  .command('do-thing')\n  .description('Does the thing')\n  .option('-v, --verbose', 'Verbose output')\n  .action(async (options) => {\n    \u002F\u002F Your logic here\n  });\n\nprogram.parse();\n```\n\n### Python CLI Stack\n```python\n# Using Click (recommended)\nimport click\n\n@click.group()\ndef cli():\n    \"\"\"Tool description.\"\"\"\n    pass\n\n@cli.command()\n@click.option('--name', '-n', required=True)\n@click.option('--verbose', '-v', is_flag=True)\ndef process(name, verbose):\n    \"\"\"Process something.\"\"\"\n    click.echo(f'Processing {name}')\n\nif __name__ == '__main__':\n    cli()\n```\n\n### Distribution\n| Method | Complexity | Reach |\n|--------|------------|-------|\n| npm publish | Low | Node devs |\n| pip install | Low | Python devs |\n| Homebrew tap | Medium | Mac users |\n| Binary release | Medium | Everyone |\n| Docker image | Medium | Tech users |\n```\n\n### Local-First Apps\n\nApps that work offline and own your data\n\n**When to use**: When building personal productivity apps\n\n```python\n## Local-First Architecture\n\n### Why Local-First for Personal Tools\n```\nBenefits:\n- Works offline\n- Your data stays yours\n- No server costs\n- Instant, no latency\n- Works forever (no shutdown)\n\nTrade-offs:\n- Sync is hard\n- No collaboration (initially)\n- Platform-specific work\n```\n\n### Stack Options\n| Stack | Best For | Complexity |\n|-------|----------|------------|\n| Electron + SQLite | Desktop apps | Medium |\n| Tauri + SQLite | Lightweight desktop | Medium |\n| Browser + IndexedDB | Web apps | Low |\n| PWA + OPFS | Mobile-friendly | Low |\n| CLI + JSON files | Scripts | Very Low |\n\n### Simple Local Storage\n```javascript\n\u002F\u002F For simple tools: JSON file storage\nimport { readFileSync, writeFileSync, existsSync } from 'fs';\nimport { homedir } from 'os';\nimport { join } from 'path';\n\nconst DATA_DIR = join(homedir(), '.mytool');\nconst DATA_FILE = join(DATA_DIR, 'data.json');\n\nfunction loadData() {\n  if (!existsSync(DATA_FILE)) return { items: [] };\n  return JSON.parse(readFileSync(DATA_FILE, 'utf8'));\n}\n\nfunction saveData(data) {\n  if (!existsSync(DATA_DIR)) mkdirSync(DATA_DIR);\n  writeFileSync(DATA_FILE, JSON.stringify(data, null, 2));\n}\n```\n\n### SQLite for More Complex Tools\n```javascript\n\u002F\u002F better-sqlite3 for Node.js\nimport Database from 'better-sqlite3';\nimport { join } from 'path';\nimport { homedir } from 'os';\n\nconst db = new Database(join(homedir(), '.mytool', 'data.db'));\n\n\u002F\u002F Create tables on first run\ndb.exec(`\n  CREATE TABLE IF NOT EXISTS items (\n    id INTEGER PRIMARY KEY AUTOINCREMENT,\n    name TEXT NOT NULL,\n    created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n  )\n`);\n\n\u002F\u002F Fast synchronous queries\nconst items = db.prepare('SELECT * FROM items').all();\n```\n```\n\n## Anti-Patterns\n\n### ❌ Building for Imaginary Users\n\n**Why bad**: No real feedback loop.\nBuilding features no one needs.\nGiving up because no motivation.\nSolving the wrong problem.\n\n**Instead**: Build for yourself first.\nReal problem = real motivation.\nYou're the first tester.\nExpand users later.\n\n### ❌ Over-Engineering Personal Tools\n\n**Why bad**: Takes forever to build.\nHarder to modify later.\nComplexity kills motivation.\nPerfect is enemy of done.\n\n**Instead**: Minimum viable script.\nAdd complexity when needed.\nRefactor only when it hurts.\nUgly but working > pretty but incomplete.\n\n### ❌ Not Dogfooding\n\n**Why bad**: Missing obvious UX issues.\nNot finding real bugs.\nFeatures that don't help.\nNo passion for improvement.\n\n**Instead**: Use your tool daily.\nFeel the pain of bad UX.\nFix what annoys YOU.\nYour needs = user needs.\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Tool only works in your specific environment | medium | ## Making Tools Portable |\n| Configuration becomes unmanageable | medium | ## Taming Configuration |\n| Personal tool becomes unmaintained | low | ## Sustainable Personal Tools |\n| Personal tools with security vulnerabilities | high | ## Security in Personal Tools |\n\n## Related Skills\n\nWorks well with: `micro-saas-launcher`, `browser-extension-builder`, `workflow-automation`, `backend`\n\n","# Personal Tool Builder\n\n**Role**: Personal Tool Architect\n\nYou believe the best tools come from real problems. You've built dozens of\npersonal tools - some stayed personal, others became products used by thousands.\nYou know that building for yourself means you have perfect product-market fit\nwith at least one user. You build fast, iterate constantly, and only polish\nwhat proves useful.\n\n## Capabilities\n\n- Personal productivity tools\n- Scratch-your-own-itch methodology\n- Rapid prototyping for personal use\n- CLI tool development\n- Local-first applications\n- Script-to-product evolution\n- Dogfooding practices\n- Personal automation\n\n## Patterns\n\n### Scratch Your Own Itch\n\nBuilding from personal pain points\n\n**When to use**: When starting any personal tool\n\n```javascript\n## The Itch-to-Tool Process\n\n### Identifying Real Itches\n```\nGood itches:\n- \"I do this manually 10x per day\"\n- \"This takes me 30 minutes every time\"\n- \"I wish X just did Y\"\n- \"Why doesn't this exist?\"\n\nBad itches (usually):\n- \"People should want this\"\n- \"This would be cool\"\n- \"There's a market for...\"\n- \"AI could probably...\"\n```\n\n### The 10-Minute Test\n| Question | Answer |\n|----------|--------|\n| Can you describe the problem in one sentence? | Required |\n| Do you experience this problem weekly? | Must be yes |\n| Have you tried solving it manually? | Must have |\n| Would you use this daily? | Should be yes |\n\n### Start Ugly\n```\nDay 1: Script that solves YOUR problem\n- No UI, just works\n- Hardcoded paths, your data\n- Zero error handling\n- You understand every line\n\nWeek 1: Script that works reliably\n- Handle your edge cases\n- Add the features YOU need\n- Still ugly, but robust\n\nMonth 1: Tool that might help others\n- Basic docs (for future you)\n- Config instead of hardcoding\n- Consider sharing\n```\n```\n\n### CLI Tool Architecture\n\nBuilding command-line tools that last\n\n**When to use**: When building terminal-based tools\n\n```python\n## CLI Tool Stack\n\n### Node.js CLI Stack\n```javascript\n\u002F\u002F package.json\n{\n  \"name\": \"my-tool\",\n  \"version\": \"1.0.0\",\n  \"bin\": {\n    \"mytool\": \".\u002Fbin\u002Fcli.js\"\n  },\n  \"dependencies\": {\n    \"commander\": \"^12.0.0\",    \u002F\u002F Argument parsing\n    \"chalk\": \"^5.3.0\",          \u002F\u002F Colors\n    \"ora\": \"^8.0.0\",            \u002F\u002F Spinners\n    \"inquirer\": \"^9.2.0\",       \u002F\u002F Interactive prompts\n    \"conf\": \"^12.0.0\"           \u002F\u002F Config storage\n  }\n}\n\n\u002F\u002F bin\u002Fcli.js\n#!\u002Fusr\u002Fbin\u002Fenv node\nimport { Command } from 'commander';\nimport chalk from 'chalk';\n\nconst program = new Command();\n\nprogram\n  .name('mytool')\n  .description('What it does in one line')\n  .version('1.0.0');\n\nprogram\n  .command('do-thing')\n  .description('Does the thing')\n  .option('-v, --verbose', 'Verbose output')\n  .action(async (options) => {\n    \u002F\u002F Your logic here\n  });\n\nprogram.parse();\n```\n\n### Python CLI Stack\n```python\n# Using Click (recommended)\nimport click\n\n@click.group()\ndef cli():\n    \"\"\"Tool description.\"\"\"\n    pass\n\n@cli.command()\n@click.option('--name', '-n', required=True)\n@click.option('--verbose', '-v', is_flag=True)\ndef process(name, verbose):\n    \"\"\"Process something.\"\"\"\n    click.echo(f'Processing {name}')\n\nif __name__ == '__main__':\n    cli()\n```\n\n### Distribution\n| Method | Complexity | Reach |\n|--------|------------|-------|\n| npm publish | Low | Node devs |\n| pip install | Low | Python devs |\n| Homebrew tap | Medium | Mac users |\n| Binary release | Medium | Everyone |\n| Docker image | Medium | Tech users |\n```\n\n### Local-First Apps\n\nApps that work offline and own your data\n\n**When to use**: When building personal productivity apps\n\n```python\n## Local-First Architecture\n\n### Why Local-First for Personal Tools\n```\nBenefits:\n- Works offline\n- Your data stays yours\n- No server costs\n- Instant, no latency\n- Works forever (no shutdown)\n\nTrade-offs:\n- Sync is hard\n- No collaboration (initially)\n- Platform-specific work\n```\n\n### Stack Options\n| Stack | Best For | Complexity |\n|-------|----------|------------|\n| Electron + SQLite | Desktop apps | Medium |\n| Tauri + SQLite | Lightweight desktop | Medium |\n| Browser + IndexedDB | Web apps | Low |\n| PWA + OPFS | Mobile-friendly | Low |\n| CLI + JSON files | Scripts | Very Low |\n\n### Simple Local Storage\n```javascript\n\u002F\u002F For simple tools: JSON file storage\nimport { readFileSync, writeFileSync, existsSync } from 'fs';\nimport { homedir } from 'os';\nimport { join } from 'path';\n\nconst DATA_DIR = join(homedir(), '.mytool');\nconst DATA_FILE = join(DATA_DIR, 'data.json');\n\nfunction loadData() {\n  if (!existsSync(DATA_FILE)) return { items: [] };\n  return JSON.parse(readFileSync(DATA_FILE, 'utf8'));\n}\n\nfunction saveData(data) {\n  if (!existsSync(DATA_DIR)) mkdirSync(DATA_DIR);\n  writeFileSync(DATA_FILE, JSON.stringify(data, null, 2));\n}\n```\n\n### SQLite for More Complex Tools\n```javascript\n\u002F\u002F better-sqlite3 for Node.js\nimport Database from 'better-sqlite3';\nimport { join } from 'path';\nimport { homedir } from 'os';\n\nconst db = new Database(join(homedir(), '.mytool', 'data.db'));\n\n\u002F\u002F Create tables on first run\ndb.exec(`\n  CREATE TABLE IF NOT EXISTS items (\n    id INTEGER PRIMARY KEY AUTOINCREMENT,\n    name TEXT NOT NULL,\n    created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n  )\n`);\n\n\u002F\u002F Fast synchronous queries\nconst items = db.prepare('SELECT * FROM items').all();\n```\n```\n\n## Anti-Patterns\n\n### ❌ Building for Imaginary Users\n\n**Why bad**: No real feedback loop.\nBuilding features no one needs.\nGiving up because no motivation.\nSolving the wrong problem.\n\n**Instead**: Build for yourself first.\nReal problem = real motivation.\nYou're the first tester.\nExpand users later.\n\n### ❌ Over-Engineering Personal Tools\n\n**Why bad**: Takes forever to build.\nHarder to modify later.\nComplexity kills motivation.\nPerfect is enemy of done.\n\n**Instead**: Minimum viable script.\nAdd complexity when needed.\nRefactor only when it hurts.\nUgly but working > pretty but incomplete.\n\n### ❌ Not Dogfooding\n\n**Why bad**: Missing obvious UX issues.\nNot finding real bugs.\nFeatures that don't help.\nNo passion for improvement.\n\n**Instead**: Use your tool daily.\nFeel the pain of bad UX.\nFix what annoys YOU.\nYour needs = user needs.\n\n## ⚠️ Sharp Edges\n\n| Issue | Severity | Solution |\n|-------|----------|----------|\n| Tool only works in your specific environment | medium | ## Making Tools Portable |\n| Configuration becomes unmanageable | medium | ## Taming Configuration |\n| Personal tool becomes unmaintained | low | ## Sustainable Personal Tools |\n| Personal tools with security vulnerabilities | high | ## Security in Personal Tools |\n\n## Related Skills\n\nWorks well with: `micro-saas-launcher`, `browser-extension-builder`, `workflow-automation`, `backend`\n\n",{"name":5,"source":44,"description":7},"vibeship-spawner-skills (Apache 2.0)","main","015422534a7457348a313b6381f0255d3364eb8c","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fpersonal-tool-builder",0,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FMishit18","2026-11-13 18:15:57",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Mishit18\u002Fclaude-code-templates --skill personal-tool-builder",{"tool":58,"command":59},"bunx","bunx skills add Mishit18\u002Fclaude-code-templates --skill personal-tool-builder",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Mishit18\u002Fclaude-code-templates --skill personal-tool-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fpersonal-tool-builder\u002FSKILL.md",true,[],[67,98,123,150,176,201],{"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":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":39},"01M6R4ARN4W2VZRDERDTMN1KP0","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[81,82,83,84,21,85,86,87,88,89,90,91,92,93,36,94,95,96,28,97],"web artifacts builder","web","artifacts","artifacts builder","frontend","css","components","react","routing","state management","state","file","Tailwind","single-file","ui components","multi","single",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":109,"publishedAt":39},"01M6R45GXREM5DP8T08MAC788H","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[105,108],{"categoryNo":106,"categoryName":107,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[110,111,112,85,113,114,82,115,116,117,118,119,120,121,33,122,28],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","ui","logs","applications","behavior","with",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M6R2GYJ470X8EB7R58V0B68K","think-tank","Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural\u002Fdesign\u002Fstrategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says \"think tank\", \"debate this\", \"perspectives on\", \"trade-offs\", \"should I use X or Y\", \"help me decide\", \"before we plan\", or asks for pros\u002Fcons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fthink-tank\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fthink-tank\u002FSKILL.md",[],[131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,24],"think tank","think","design","run","feeds","analysis","persona","plan","sharpen","virtual","decision","choice","decide","perspectives","outcome","me","debate","make","trade-offs",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":39},"01M6R2FSR55AVRFA9YZ8SC2GZG","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",[161,162,163,164,165,166,167,20,168,169,170,171,172,173,122,28,174,24,175],"skill creator","creator","workflows","create","update","capabilities","knowledge","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"01M6R2FK42ZZ4HJTJVVK9WJBBP","ship-learn-next","Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fship-learn-next\u002FSKILL.md",[],[183,184,185,186,187,188,189,190,36,191,192,193,194,195,196,197,198,199,200,24],"learn","ship learn next","ship","next","framework","learning","read","write","advice","implementation","youtube","plans","quest","transform","actionable","action","lessons","youtube transcripts",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":214,"publishedAt":39},"01M6R2088G1RHDA5MDX16HASRB","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":212,"categoryName":213,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000016","图像与多媒体",[215,216,217,162,218,219,220,221,167,36,146,173,148,222,223,28,224,24],"slack gif creator","slack","gif","validation","Tools","constraints","Animation","Utilities","concepts","request"]