[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF1K1YTMR2FGAWTHKE79W7":3,"skill-same:01M6AF1K1YTMR2FGAWTHKE79W7":70},{"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":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6AF1K1YTMR2FGAWTHKE79W7","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.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\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","# 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",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add davila7\u002Fclaude-code-templates --skill email-composer",{"tool":62,"command":63},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill email-composer",{"tool":65,"command":66},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill email-composer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer\u002FSKILL.md",true,[],[71,98,124,157,192,216],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":41},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,85,29,86,87,33,28,88,89,90,91,92,93,94,95,96,97],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":41},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[104],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,36,108,109,110,111,112,113,114,115,28,116,117,118,119,120,121,122,123],"technical debt","debt","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":139,"publishedAt":41},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[130,133,134],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[140,141,142,143,144,145,146,29,147,148,149,150,151,152,153,33,154,155,28,156],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":41},"01M6AFY6F7CC2BBZP1QD6VTNVC","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,29,191],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":203,"publishedAt":41},"01M6AFWF33SFV9Z3SF4PEEE4BF","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[199,202],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},[204,205,206,207,208,170,209,179,180,210,211,212,213,29,214,89,215],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":230,"publishedAt":41},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[223,226,227],{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":228,"categoryName":229,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000036","内容创作者",[231,232,233,39,234,235,236,35,172,237,182,116,238,239,240,241,242,152,243,28,244,245,246,247,248,95,249],"discernment nudge","nudge","interpretation","run","reasoning","data","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]