[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R1SNQTREY7KT51ZKBWHCFJ":3,"skill-same:01M6R1SNQTREY7KT51ZKBWHCFJ":67},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6R1SNQTREY7KT51ZKBWHCFJ","Email Composer",null,"Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.","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\u002Fenterprise-communication\u002Femail-composer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"composer","email","email composer","user","when","for","professional","emails","draft","use","business","writing","technical","messages","communication","help","customer","2026-11-10 10:12:30",false,"---\nname: Email Composer\ndescription: Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.\n---\n\n# Email Composer\n\n## Quick start\n\nProvide context and purpose, and I'll draft an appropriate email.\n\n**What I need:**\n- Purpose of email (request, follow-up, announcement, etc.)\n- Recipient relationship (colleague, customer, manager, vendor)\n- Key points to include\n- Desired tone (formal, casual, urgent, friendly)\n\n## Email structure\n\nStandard professional email format:\n\n```\nSubject: [Clear, specific subject line]\n\n[Greeting],\n\n[Opening - context\u002Fpurpose]\n\n[Body - main points]\n\n[Closing - call to action]\n\n[Sign-off]\n[Your name]\n```\n\n## Common email types\n\n### Request for information\n\n```\nSubject: Question about Q4 project timeline\n\nHi [Name],\n\nI hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.\n\nCould you provide an update on:\n- Current progress on feature development\n- Expected completion date for testing phase\n- Any blockers or dependencies we should be aware of\n\nThis will help us coordinate with the marketing team for the launch materials.\n\nThanks in advance for your help!\n\nBest regards,\n[Your name]\n```\n\n### Follow-up email\n\n```\nSubject: Following up: Proposal for new payment system\n\nHi [Name],\n\nI wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.\n\nTo recap, the proposed system would:\n- Reduce transaction fees by 30%\n- Integrate with existing accounting software\n- Improve customer checkout experience\n\nI'd be happy to schedule a brief call to discuss any questions you might have.\n\nLooking forward to hearing from you.\n\nBest,\n[Your name]\n```\n\n### Technical update\n\n```\nSubject: API Maintenance Window - [Date]\n\nTeam,\n\nThis is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].\n\nDuring this window:\n- API endpoints will be unavailable\n- Database will be upgraded to v14\n- SSL certificates will be renewed\n\nExpected downtime: 2 hours\n\nWhat you need to do:\n- Notify your users of the planned downtime\n- Ensure retry logic is in place for API calls\n- Monitor your application after maintenance completes\n\nIf you have any concerns or conflicts with this schedule, please let me know by [Date].\n\nTechnical details available in our status page: [link]\n\nThanks,\n[Your name]\n```\n\n### Customer support\n\n```\nSubject: Re: Issue with order #12345\n\nHi [Customer name],\n\nThank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.\n\nI've looked into your order (#12345) and found the following:\n\n[Explanation of the issue]\n\nTo resolve this, I've:\n- [Action taken 1]\n- [Action taken 2]\n\nYou should see [expected outcome] within [timeframe].\n\nIf you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].\n\nWe appreciate your patience and understanding.\n\nBest regards,\n[Your name]\nCustomer Support Team\n```\n\n### Meeting request\n\n```\nSubject: Meeting request: Discuss database migration strategy\n\nHi [Name],\n\nI'd like to schedule a meeting to discuss our approach for the upcoming database migration.\n\nAgenda items:\n- Review migration timeline and milestones\n- Discuss rollback strategy\n- Identify potential risks and mitigation plans\n- Assign team responsibilities\n\nEstimated duration: 45 minutes\n\nI'm available:\n- Monday 2-4 PM\n- Wednesday 10 AM - 12 PM\n- Friday 1-3 PM\n\nPlease let me know what works best for you, or feel free to suggest alternative times.\n\nBest,\n[Your name]\n```\n\n## Tone guidelines\n\n### Formal tone\n- Use complete sentences\n- Avoid contractions\n- Professional language\n- Proper titles (Dr., Mr., Ms.)\n\n### Casual tone\n- Contractions acceptable\n- Conversational language\n- Still professional\n- First names\n\n### Urgent tone\n- Clear subject line with [URGENT] or [ACTION REQUIRED]\n- Bold key points\n- Explicit deadline\n- Direct call to action\n\n## Subject line best practices\n\n**Good subject lines:**\n- \"Action required: Submit timesheet by Friday\"\n- \"Q4 Sales Report - Review needed\"\n- \"Meeting rescheduled: Project kickoff now Thursday\"\n- \"Quick question about deployment process\"\n\n**Bad subject lines:**\n- \"Update\"\n- \"Question\"\n- \"Hello\"\n- \"Following up\"\n\n## Email etiquette\n\n**DO:**\n- Respond within 24 hours (even if just to acknowledge)\n- Use clear, specific subject lines\n- Keep it concise\n- Proofread before sending\n- Include relevant context\n- Use bullet points for multiple items\n- End with clear call to action\n\n**DON'T:**\n- Use ALL CAPS\n- Over-use exclamation marks!!!\n- Mark everything as urgent\n- Reply all unless necessary\n- Send when emotional\n- Include unnecessary recipients\n- Forget attachments mentioned in email\n\n## Templates by scenario\n\n### Decline request politely\n\n```\nSubject: Re: [Original subject]\n\nHi [Name],\n\nThank you for thinking of me for [request\u002Fopportunity].\n\nUnfortunately, I won't be able to [participate\u002Fhelp\u002Fattend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].\n\nI appreciate your understanding, and I hope we can collaborate on future opportunities.\n\nBest regards,\n[Your name]\n```\n\n### Apologize for mistake\n\n```\nSubject: Apology and correction: [Issue]\n\nHi [Name],\n\nI'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.\n\nTo correct this:\n- [Action 1 already taken]\n- [Action 2 in progress]\n- [Preventive measure for future]\n\nI understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.\n\nIf you have any concerns or questions, please don't hesitate to reach out.\n\nSincerely,\n[Your name]\n```\n\n### Share good news\n\n```\nSubject: Great news: [Achievement\u002Fmilestone]\n\nTeam,\n\nI'm excited to share that we've [accomplished goal]!\n\nThis success is thanks to:\n- [Team\u002Fperson contribution 1]\n- [Team\u002Fperson contribution 2]\n\nImpact:\n- [Metric improvement]\n- [Business benefit]\n\nThank you all for your hard work and dedication. Let's keep up the momentum!\n\nCheers,\n[Your name]\n```\n\n## Closing phrases by context\n\n**Formal:**\n- Sincerely\n- Best regards\n- Respectfully\n- Cordially\n\n**Professional:**\n- Best\n- Thanks\n- Kind regards\n- Regards\n\n**Casual:**\n- Cheers\n- Thanks!\n- Talk soon\n- Best\n\n## Email composition checklist\n\n- [ ] Clear, specific subject line\n- [ ] Appropriate greeting\n- [ ] Purpose stated upfront\n- [ ] Key points organized with bullets\u002Fnumbers\n- [ ] Clear call to action or next steps\n- [ ] Appropriate tone for audience\n- [ ] Proofread for typos\n- [ ] Attachments included (if mentioned)\n- [ ] Recipients correct (To, CC, BCC)\n- [ ] Professional signature\n\n","# Email Composer\n\n## Quick start\n\nProvide context and purpose, and I'll draft an appropriate email.\n\n**What I need:**\n- Purpose of email (request, follow-up, announcement, etc.)\n- Recipient relationship (colleague, customer, manager, vendor)\n- Key points to include\n- Desired tone (formal, casual, urgent, friendly)\n\n## Email structure\n\nStandard professional email format:\n\n```\nSubject: [Clear, specific subject line]\n\n[Greeting],\n\n[Opening - context\u002Fpurpose]\n\n[Body - main points]\n\n[Closing - call to action]\n\n[Sign-off]\n[Your name]\n```\n\n## Common email types\n\n### Request for information\n\n```\nSubject: Question about Q4 project timeline\n\nHi [Name],\n\nI hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.\n\nCould you provide an update on:\n- Current progress on feature development\n- Expected completion date for testing phase\n- Any blockers or dependencies we should be aware of\n\nThis will help us coordinate with the marketing team for the launch materials.\n\nThanks in advance for your help!\n\nBest regards,\n[Your name]\n```\n\n### Follow-up email\n\n```\nSubject: Following up: Proposal for new payment system\n\nHi [Name],\n\nI wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.\n\nTo recap, the proposed system would:\n- Reduce transaction fees by 30%\n- Integrate with existing accounting software\n- Improve customer checkout experience\n\nI'd be happy to schedule a brief call to discuss any questions you might have.\n\nLooking forward to hearing from you.\n\nBest,\n[Your name]\n```\n\n### Technical update\n\n```\nSubject: API Maintenance Window - [Date]\n\nTeam,\n\nThis is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].\n\nDuring this window:\n- API endpoints will be unavailable\n- Database will be upgraded to v14\n- SSL certificates will be renewed\n\nExpected downtime: 2 hours\n\nWhat you need to do:\n- Notify your users of the planned downtime\n- Ensure retry logic is in place for API calls\n- Monitor your application after maintenance completes\n\nIf you have any concerns or conflicts with this schedule, please let me know by [Date].\n\nTechnical details available in our status page: [link]\n\nThanks,\n[Your name]\n```\n\n### Customer support\n\n```\nSubject: Re: Issue with order #12345\n\nHi [Customer name],\n\nThank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.\n\nI've looked into your order (#12345) and found the following:\n\n[Explanation of the issue]\n\nTo resolve this, I've:\n- [Action taken 1]\n- [Action taken 2]\n\nYou should see [expected outcome] within [timeframe].\n\nIf you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].\n\nWe appreciate your patience and understanding.\n\nBest regards,\n[Your name]\nCustomer Support Team\n```\n\n### Meeting request\n\n```\nSubject: Meeting request: Discuss database migration strategy\n\nHi [Name],\n\nI'd like to schedule a meeting to discuss our approach for the upcoming database migration.\n\nAgenda items:\n- Review migration timeline and milestones\n- Discuss rollback strategy\n- Identify potential risks and mitigation plans\n- Assign team responsibilities\n\nEstimated duration: 45 minutes\n\nI'm available:\n- Monday 2-4 PM\n- Wednesday 10 AM - 12 PM\n- Friday 1-3 PM\n\nPlease let me know what works best for you, or feel free to suggest alternative times.\n\nBest,\n[Your name]\n```\n\n## Tone guidelines\n\n### Formal tone\n- Use complete sentences\n- Avoid contractions\n- Professional language\n- Proper titles (Dr., Mr., Ms.)\n\n### Casual tone\n- Contractions acceptable\n- Conversational language\n- Still professional\n- First names\n\n### Urgent tone\n- Clear subject line with [URGENT] or [ACTION REQUIRED]\n- Bold key points\n- Explicit deadline\n- Direct call to action\n\n## Subject line best practices\n\n**Good subject lines:**\n- \"Action required: Submit timesheet by Friday\"\n- \"Q4 Sales Report - Review needed\"\n- \"Meeting rescheduled: Project kickoff now Thursday\"\n- \"Quick question about deployment process\"\n\n**Bad subject lines:**\n- \"Update\"\n- \"Question\"\n- \"Hello\"\n- \"Following up\"\n\n## Email etiquette\n\n**DO:**\n- Respond within 24 hours (even if just to acknowledge)\n- Use clear, specific subject lines\n- Keep it concise\n- Proofread before sending\n- Include relevant context\n- Use bullet points for multiple items\n- End with clear call to action\n\n**DON'T:**\n- Use ALL CAPS\n- Over-use exclamation marks!!!\n- Mark everything as urgent\n- Reply all unless necessary\n- Send when emotional\n- Include unnecessary recipients\n- Forget attachments mentioned in email\n\n## Templates by scenario\n\n### Decline request politely\n\n```\nSubject: Re: [Original subject]\n\nHi [Name],\n\nThank you for thinking of me for [request\u002Fopportunity].\n\nUnfortunately, I won't be able to [participate\u002Fhelp\u002Fattend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].\n\nI appreciate your understanding, and I hope we can collaborate on future opportunities.\n\nBest regards,\n[Your name]\n```\n\n### Apologize for mistake\n\n```\nSubject: Apology and correction: [Issue]\n\nHi [Name],\n\nI'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.\n\nTo correct this:\n- [Action 1 already taken]\n- [Action 2 in progress]\n- [Preventive measure for future]\n\nI understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.\n\nIf you have any concerns or questions, please don't hesitate to reach out.\n\nSincerely,\n[Your name]\n```\n\n### Share good news\n\n```\nSubject: Great news: [Achievement\u002Fmilestone]\n\nTeam,\n\nI'm excited to share that we've [accomplished goal]!\n\nThis success is thanks to:\n- [Team\u002Fperson contribution 1]\n- [Team\u002Fperson contribution 2]\n\nImpact:\n- [Metric improvement]\n- [Business benefit]\n\nThank you all for your hard work and dedication. Let's keep up the momentum!\n\nCheers,\n[Your name]\n```\n\n## Closing phrases by context\n\n**Formal:**\n- Sincerely\n- Best regards\n- Respectfully\n- Cordially\n\n**Professional:**\n- Best\n- Thanks\n- Kind regards\n- Regards\n\n**Casual:**\n- Cheers\n- Thanks!\n- Talk soon\n- Best\n\n## Email composition checklist\n\n- [ ] Clear, specific subject line\n- [ ] Appropriate greeting\n- [ ] Purpose stated upfront\n- [ ] Key points organized with bullets\u002Fnumbers\n- [ ] Clear call to action or next steps\n- [ ] Appropriate tone for audience\n- [ ] Proofread for typos\n- [ ] Attachments included (if mentioned)\n- [ ] Recipients correct (To, CC, BCC)\n- [ ] Professional signature\n\n",{"name":5,"description":7},"main","015422534a7457348a313b6381f0255d3364eb8c","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer",0,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FMishit18","2026-11-14 17:36:32",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Mishit18\u002Fclaude-code-templates --skill \"Email Composer\"",{"tool":59,"command":60},"bunx","bunx skills add Mishit18\u002Fclaude-code-templates --skill \"Email Composer\"",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Mishit18\u002Fclaude-code-templates --skill \"Email Composer\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer\u002FSKILL.md",true,[],[68,98,127,152,179,190],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":79,"publishedAt":97},"01M6R194Y2CS39V9VPAVRVW1ZV","skill-creation-guide","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fskill-creation-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fskill-creation-guide\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,29,96,28],"skill creation guide","guide","creation","skill creation","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","new skill","existing skill","users","with","Existing","2026-11-11 15:11:14",{"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":72,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":41},"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.","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",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[109,110,111,112,113,114,115,116,117,118,119,120,121,122,33,123,124,125,29,126],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","routing","state management","state","file","Tailwind","single-file","ui components","multi","single",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":138,"publishedAt":41},"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",[134,137],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[139,140,141,114,142,143,110,144,145,146,147,148,149,150,151,95,29],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","ui","logs","applications","behavior","local",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":41},"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",[],[160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,28],"think tank","think","design","run","feeds","analysis","persona","plan","sharpen","virtual","decision","choice","decide","perspectives","outcome","me","debate","make","trade-offs",{"skillNo":180,"name":181,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":41},"01M6R2FSR55AVRFA9YZ8SC2GZG","skill-creator","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",[185],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},[187,188,84,85,86,87,88,89,90,91,81,92,93,94,95,29,96,28,189],"skill creator","creator","new",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":41},"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",[],[197,198,199,200,201,202,203,204,33,205,206,207,208,209,210,211,212,213,214,28],"learn","ship learn next","ship","next","framework","learning","read","write","advice","implementation","youtube","plans","quest","transform","actionable","action","lessons","youtube transcripts"]