[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JK0GXAXBNFT51KXHMDHRFD":3,"skill-same:01M6JK0GXAXBNFT51KXHMDHRFD":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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6JK0GXAXBNFT51KXHMDHRFD","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.","transaurus\u002Fstaging-davila7-claude-code-templates","transaurus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F210882017?v=4","01M6JH1R6ZCRXGJCTDP5ZKZBE6","Page Turner Agent","01M6JH1RBBR2P6Y0XWDGM4B0G7",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-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],"email","email composer","composer","writing","customer","help","communication","messages","technical","user","business","use","draft","emails","professional","for","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","34fa6acf794b9a6310d298cbb8fb8c9420a5edcf","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer",2,"https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates","https:\u002F\u002Fgithub.com\u002Ftransaurus","Automated works of Page Turner","2026-03-28 10:12:59",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill \"Email Composer\"",{"tool":59,"command":60},"bunx","bunx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill \"Email Composer\"",{"tool":62,"command":63},"pnpm","pnpm dlx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill \"Email Composer\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Femail-composer\u002FSKILL.md",true,[],[68,94,114,138,158,184],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":77,"publishedAt":40},"01M6JMRJR3BE0HGWFWDZSB853S","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[78,79,80,81,27,82,83,84,85,34,35,86,87,88,89,90,91,92,39,93],"zapier make patterns","patterns","make","zapier","workflow","automation","code","integrations","power","complexity","platform","apps","how to","No-Code","which","spawner",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":40},"01M6JMR8YK6SWPCTG1MCQTMN9S","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[96,101,102,103,104,105,106,107,108,109,110,33,35,111,112,113],"cli","github","commit","pull request","openai","pull","push","flow","open","gh","only","stage","github cli",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":40},"01M6JMQNFE64ZASQK90HARRXW8","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[120],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,39,93],"Workflow Automation","ai agents","accessibility","workflows","apache","execution","inngest","parallel","orchestrator","resume","n8n","payment","worker","scripts","temporal","with",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":40},"01M6JMQDYJ0XETERPHGDR3EVGN","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[145,146,147,148,149,125,150,126,127,151,35,152,153,154,155,156,157,137,39,93],"dev","trigger dev","trigger","design","typescript","async execution","first","async","developer experience","expert","task","background jobs","long",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":40},"01M6JMQ5J6KK3GSX9FJCWWK6G6","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[168,169,170,137,171,82,172,173,174,175,176,177,35,178,179,180,181,182,183,39],"planning with files","planning","files","with files","storage","tasks","markdown","knowledge","projects","work","manus","structured output","progress","transforms","multi","output",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":194,"publishedAt":40},"01M6JMPWAT60RXXNEC4V9TRBRS","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},[82,195,132,196,79,197,198,125,199,173,169,200,201,202,203,204,205,206,207,208],"n8n workflow patterns","workflow patterns","n8n workflow","ai agent","architecture","database","api","planning workflow","structure","database operations","webhook","processing","http api","scheduled"]