[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VDH71BRXE4NV9PHSS3BZX":3,"skill-same:01M79VDH71BRXE4NV9PHSS3BZX":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79VDH71BRXE4NV9PHSS3BZX","reference-list-builder",null,"Format professional references properly and prepare reference materials. Use when the user mentions references, reference list, references page, or preparing referees for a job application.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Freference-list-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reference-list-builder\ndescription: Format professional references properly and prepare reference materials. Use when the user mentions references, reference list, references page, or preparing referees for a job application.\n---\n\n# Reference List Builder\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs to create a professional reference list\n- Wants help choosing the right references\n- Needs to format references properly\n- Is preparing references for job applications\n- Mentions: \"references\", \"reference list\", \"professional references\", \"reference check\"\n\n## Core Capabilities\n\n- Format professional reference lists\n- Guide reference selection strategy\n- Prepare reference briefing materials\n- Anticipate reference check questions\n- Handle difficult reference situations\n- Coordinate reference outreach\n\n## Reference Strategy\n\n### Who Makes a Good Reference?\n\n**Ideal References:**\n- Former direct managers (most important)\n- Senior colleagues who observed your work\n- Cross-functional partners\n- Clients or customers\n- Direct reports (for leadership roles)\n- Professors or advisors (for recent graduates)\n\n**Reference Hierarchy:**\n1. **Most Valuable:** Recent direct supervisor\n2. **Very Valuable:** Senior leaders who know your work\n3. **Valuable:** Peers and cross-functional partners\n4. **Acceptable:** Clients, vendors, professors\n5. **Avoid:** Friends, family, HR contacts only\n\n### Who to Avoid\n\n- ❌ Current employer (without permission)\n- ❌ People who barely know you\n- ❌ References from 10+ years ago only\n- ❌ Personal friends (unless specified)\n- ❌ People who might give lukewarm feedback\n- ❌ Anyone you haven't contacted in advance\n\n## Reference List Format\n\n### Standard Format\n\n```\nPROFESSIONAL REFERENCES\n\nJane Smith\nSenior Director of Product\nTechCorp Inc.\nPhone: (555) 123-4567\nEmail: jane.smith@techcorp.com\nRelationship: Direct supervisor for 3 years (2020-2023)\n\nJohn Doe\nVP of Engineering\nPrevious Company\nPhone: (555) 234-5678\nEmail: john.doe@previous.com\nRelationship: Cross-functional partner on 5 major projects\n```\n\n### Information to Include\n\n**Required:**\n- Full name\n- Current job title\n- Current company\n- Phone number\n- Professional email\n- Your relationship to them\n\n**Optional:**\n- LinkedIn URL\n- Best time to reach\n- Preferred contact method\n\n### Formatting Guidelines\n\n- Match the style of your resume (fonts, formatting)\n- 3-5 references (more only if requested)\n- Separate page from resume\n- Header should match resume header\n- Include \"References\" or \"Professional References\" as title\n\n## Reference Preparation\n\n### Step 1: Ask Permission\n\n**Before listing anyone:**\n- Call or email to ask permission\n- Confirm their contact information\n- Explain the role you're applying for\n- Gauge their willingness and enthusiasm\n\n**Script:**\n```\n\"Hi [Name], I hope you're doing well! I'm applying for a [Role] position at [Company] and was wondering if you'd be comfortable serving as a reference for me. The role involves [brief description], and I think your perspective on [specific project\u002Fskill] would be particularly valuable. Would you be willing to speak with them if they reach out?\"\n```\n\n### Step 2: Brief Your References\n\n**Send them:**\n- Copy of your resume\n- Job description\n- Key points you want highlighted\n- Specific projects to mention\n- Timeline for when they might be contacted\n\n**Briefing Email Template:**\n```\nSubject: Reference Preparation - [Role] at [Company]\n\nHi [Name],\n\nThank you so much for agreeing to be a reference! Here's some context to help:\n\n**The Role:** [Job title] at [Company]\n**What they're looking for:** [Key requirements]\n\n**Points I'm emphasizing:**\n- [Achievement 1]\n- [Achievement 2]\n- [Skill they should mention]\n\n**Our work together they might ask about:**\n- [Project 1]\n- [Project 2]\n\nI've attached my resume and the job description for reference. They may reach out in the next [timeframe].\n\nPlease let me know if you have any questions, and thank you again!\n\nBest,\n[Your name]\n```\n\n### Step 3: Follow Up\n\nAfter references are checked:\n- Thank your references regardless of outcome\n- Let them know the result\n- Offer to reciprocate\n\n## Handling Special Situations\n\n### Current Employer Doesn't Know\n\n**Options:**\n- Ask if reference check can wait until later stage\n- Use colleagues who've left the company\n- Be upfront: \"My current employer doesn't know I'm looking\"\n- Use other professional references\n\n### Manager Left the Company\n\n**Options:**\n- Track them down on LinkedIn\n- Use their personal email\u002Fphone\n- Include their new company in reference list\n- Explain \"Former manager, now at [New Company]\"\n\n### Bad Relationship with Past Manager\n\n**Options:**\n- Use another supervisor from that role\n- Use senior colleagues instead\n- Choose references from different roles\n- Be prepared to explain if asked\n\n### Limited Professional Experience\n\n**Options:**\n- Professors or academic advisors\n- Internship supervisors\n- Volunteer organization leaders\n- Coaches or mentors\n- Client contacts\n\n### Reference Won't Give Positive Review\n\n**Don't use them.** It's better to have fewer references than a lukewarm or negative one.\n\n## What Reference Checkers Ask\n\n### Common Questions\n\n**Performance:**\n- \"How would you describe [name]'s work?\"\n- \"What were their primary responsibilities?\"\n- \"How did they perform against expectations?\"\n\n**Skills:**\n- \"What are their greatest strengths?\"\n- \"What areas could they improve?\"\n- \"How would you rate their [specific skill]?\"\n\n**Work Style:**\n- \"How did they handle pressure\u002Fdeadlines?\"\n- \"How did they work with the team?\"\n- \"How did they handle conflict?\"\n\n**Character:**\n- \"Would you rehire them?\"\n- \"Is there anything else I should know?\"\n- \"How do they compare to peers?\"\n\n### The \"Would You Rehire?\" Question\n\n**Most important question.** Brief your references that this may be asked and ensure they can answer enthusiastically.\n\n## Reference List Template\n\n```\n[YOUR NAME]\n[Your Email] | [Your Phone]\n\nPROFESSIONAL REFERENCES\n\n[REFERENCE 1 - MOST SENIOR\u002FRELEVANT]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n[REFERENCE 2]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n[REFERENCE 3]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n---\nReferences available upon request for additional contacts.\n```\n\n## Reference Timing\n\n### When to Provide References\n\n- **Don't include with initial application** (unless requested)\n- **Bring to interview** (have them ready)\n- **Provide when asked** (usually after final interview)\n- **Always ask before sharing** (confirm permission each time)\n\n### Common Timeline\n\n1. **Application:** \"References available upon request\" (optional on resume)\n2. **First Interview:** Have list ready but don't offer\n3. **Final Rounds:** \"Can you provide references?\" → Share list\n4. **Reference Check:** Company contacts your references\n5. **Offer:** Follow up with references, thank them\n\n## Output Format\n\nWhen building a reference list:\n\n```markdown\n# REFERENCE LIST\n\n## Reference Strategy\n**Target Role:** [Position]\n**Company:** [Company]\n\n## Recommended References\n\n### Primary References (Use These)\n\n**Reference 1: [Name]**\n- Current Title: [Title]\n- Company: [Company]\n- Contact: [Phone\u002FEmail]\n- Relationship: [Description]\n- Why: [What they can speak to]\n- Key points to highlight: [Specific projects\u002Fskills]\n\n**Reference 2: [Name]**\n[Same format]\n\n**Reference 3: [Name]**\n[Same format]\n\n### Backup References (If Needed)\n\n**Reference 4: [Name]**\n[Same format]\n\n## Briefing Notes\n\n### For Each Reference, Send:\n- [ ] Resume\n- [ ] Job description\n- [ ] Key talking points\n- [ ] Timeline\n\n### Key Points to Emphasize\n- [Point 1 - who should mention]\n- [Point 2 - who should mention]\n\n## Reference Outreach\n\n### Permission Request Script\n[Customized script]\n\n### Briefing Email\n[Draft briefing email]\n\n### Thank You Template\n[Post-check thank you message]\n```\n\n## Reference Checklist\n\n- ✅ Have 3-5 references ready\n- ✅ All references have given permission\n- ✅ Contact information is current and accurate\n- ✅ References know about the specific role\n- ✅ Each reference has your resume and talking points\n- ✅ At least one direct supervisor included\n- ✅ References span different aspects of your work\n- ✅ References are enthusiastic (not just willing)\n- ✅ Backup references identified\n- ✅ Thank you notes planned\n","# Reference List Builder\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs to create a professional reference list\n- Wants help choosing the right references\n- Needs to format references properly\n- Is preparing references for job applications\n- Mentions: \"references\", \"reference list\", \"professional references\", \"reference check\"\n\n## Core Capabilities\n\n- Format professional reference lists\n- Guide reference selection strategy\n- Prepare reference briefing materials\n- Anticipate reference check questions\n- Handle difficult reference situations\n- Coordinate reference outreach\n\n## Reference Strategy\n\n### Who Makes a Good Reference?\n\n**Ideal References:**\n- Former direct managers (most important)\n- Senior colleagues who observed your work\n- Cross-functional partners\n- Clients or customers\n- Direct reports (for leadership roles)\n- Professors or advisors (for recent graduates)\n\n**Reference Hierarchy:**\n1. **Most Valuable:** Recent direct supervisor\n2. **Very Valuable:** Senior leaders who know your work\n3. **Valuable:** Peers and cross-functional partners\n4. **Acceptable:** Clients, vendors, professors\n5. **Avoid:** Friends, family, HR contacts only\n\n### Who to Avoid\n\n- ❌ Current employer (without permission)\n- ❌ People who barely know you\n- ❌ References from 10+ years ago only\n- ❌ Personal friends (unless specified)\n- ❌ People who might give lukewarm feedback\n- ❌ Anyone you haven't contacted in advance\n\n## Reference List Format\n\n### Standard Format\n\n```\nPROFESSIONAL REFERENCES\n\nJane Smith\nSenior Director of Product\nTechCorp Inc.\nPhone: (555) 123-4567\nEmail: jane.smith@techcorp.com\nRelationship: Direct supervisor for 3 years (2020-2023)\n\nJohn Doe\nVP of Engineering\nPrevious Company\nPhone: (555) 234-5678\nEmail: john.doe@previous.com\nRelationship: Cross-functional partner on 5 major projects\n```\n\n### Information to Include\n\n**Required:**\n- Full name\n- Current job title\n- Current company\n- Phone number\n- Professional email\n- Your relationship to them\n\n**Optional:**\n- LinkedIn URL\n- Best time to reach\n- Preferred contact method\n\n### Formatting Guidelines\n\n- Match the style of your resume (fonts, formatting)\n- 3-5 references (more only if requested)\n- Separate page from resume\n- Header should match resume header\n- Include \"References\" or \"Professional References\" as title\n\n## Reference Preparation\n\n### Step 1: Ask Permission\n\n**Before listing anyone:**\n- Call or email to ask permission\n- Confirm their contact information\n- Explain the role you're applying for\n- Gauge their willingness and enthusiasm\n\n**Script:**\n```\n\"Hi [Name], I hope you're doing well! I'm applying for a [Role] position at [Company] and was wondering if you'd be comfortable serving as a reference for me. The role involves [brief description], and I think your perspective on [specific project\u002Fskill] would be particularly valuable. Would you be willing to speak with them if they reach out?\"\n```\n\n### Step 2: Brief Your References\n\n**Send them:**\n- Copy of your resume\n- Job description\n- Key points you want highlighted\n- Specific projects to mention\n- Timeline for when they might be contacted\n\n**Briefing Email Template:**\n```\nSubject: Reference Preparation - [Role] at [Company]\n\nHi [Name],\n\nThank you so much for agreeing to be a reference! Here's some context to help:\n\n**The Role:** [Job title] at [Company]\n**What they're looking for:** [Key requirements]\n\n**Points I'm emphasizing:**\n- [Achievement 1]\n- [Achievement 2]\n- [Skill they should mention]\n\n**Our work together they might ask about:**\n- [Project 1]\n- [Project 2]\n\nI've attached my resume and the job description for reference. They may reach out in the next [timeframe].\n\nPlease let me know if you have any questions, and thank you again!\n\nBest,\n[Your name]\n```\n\n### Step 3: Follow Up\n\nAfter references are checked:\n- Thank your references regardless of outcome\n- Let them know the result\n- Offer to reciprocate\n\n## Handling Special Situations\n\n### Current Employer Doesn't Know\n\n**Options:**\n- Ask if reference check can wait until later stage\n- Use colleagues who've left the company\n- Be upfront: \"My current employer doesn't know I'm looking\"\n- Use other professional references\n\n### Manager Left the Company\n\n**Options:**\n- Track them down on LinkedIn\n- Use their personal email\u002Fphone\n- Include their new company in reference list\n- Explain \"Former manager, now at [New Company]\"\n\n### Bad Relationship with Past Manager\n\n**Options:**\n- Use another supervisor from that role\n- Use senior colleagues instead\n- Choose references from different roles\n- Be prepared to explain if asked\n\n### Limited Professional Experience\n\n**Options:**\n- Professors or academic advisors\n- Internship supervisors\n- Volunteer organization leaders\n- Coaches or mentors\n- Client contacts\n\n### Reference Won't Give Positive Review\n\n**Don't use them.** It's better to have fewer references than a lukewarm or negative one.\n\n## What Reference Checkers Ask\n\n### Common Questions\n\n**Performance:**\n- \"How would you describe [name]'s work?\"\n- \"What were their primary responsibilities?\"\n- \"How did they perform against expectations?\"\n\n**Skills:**\n- \"What are their greatest strengths?\"\n- \"What areas could they improve?\"\n- \"How would you rate their [specific skill]?\"\n\n**Work Style:**\n- \"How did they handle pressure\u002Fdeadlines?\"\n- \"How did they work with the team?\"\n- \"How did they handle conflict?\"\n\n**Character:**\n- \"Would you rehire them?\"\n- \"Is there anything else I should know?\"\n- \"How do they compare to peers?\"\n\n### The \"Would You Rehire?\" Question\n\n**Most important question.** Brief your references that this may be asked and ensure they can answer enthusiastically.\n\n## Reference List Template\n\n```\n[YOUR NAME]\n[Your Email] | [Your Phone]\n\nPROFESSIONAL REFERENCES\n\n[REFERENCE 1 - MOST SENIOR\u002FRELEVANT]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n[REFERENCE 2]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n[REFERENCE 3]\n[Name]\n[Title]\n[Company]\nPhone: [Number]\nEmail: [Email]\nRelationship: [How you worked together, dates]\n\n---\nReferences available upon request for additional contacts.\n```\n\n## Reference Timing\n\n### When to Provide References\n\n- **Don't include with initial application** (unless requested)\n- **Bring to interview** (have them ready)\n- **Provide when asked** (usually after final interview)\n- **Always ask before sharing** (confirm permission each time)\n\n### Common Timeline\n\n1. **Application:** \"References available upon request\" (optional on resume)\n2. **First Interview:** Have list ready but don't offer\n3. **Final Rounds:** \"Can you provide references?\" → Share list\n4. **Reference Check:** Company contacts your references\n5. **Offer:** Follow up with references, thank them\n\n## Output Format\n\nWhen building a reference list:\n\n```markdown\n# REFERENCE LIST\n\n## Reference Strategy\n**Target Role:** [Position]\n**Company:** [Company]\n\n## Recommended References\n\n### Primary References (Use These)\n\n**Reference 1: [Name]**\n- Current Title: [Title]\n- Company: [Company]\n- Contact: [Phone\u002FEmail]\n- Relationship: [Description]\n- Why: [What they can speak to]\n- Key points to highlight: [Specific projects\u002Fskills]\n\n**Reference 2: [Name]**\n[Same format]\n\n**Reference 3: [Name]**\n[Same format]\n\n### Backup References (If Needed)\n\n**Reference 4: [Name]**\n[Same format]\n\n## Briefing Notes\n\n### For Each Reference, Send:\n- [ ] Resume\n- [ ] Job description\n- [ ] Key talking points\n- [ ] Timeline\n\n### Key Points to Emphasize\n- [Point 1 - who should mention]\n- [Point 2 - who should mention]\n\n## Reference Outreach\n\n### Permission Request Script\n[Customized script]\n\n### Briefing Email\n[Draft briefing email]\n\n### Thank You Template\n[Post-check thank you message]\n```\n\n## Reference Checklist\n\n- ✅ Have 3-5 references ready\n- ✅ All references have given permission\n- ✅ Contact information is current and accurate\n- ✅ References know about the specific role\n- ✅ Each reference has your resume and talking points\n- ✅ At least one direct supervisor included\n- ✅ References span different aspects of your work\n- ✅ References are enthusiastic (not just willing)\n- ✅ Backup references identified\n- ✅ Thank you notes planned\n",{"name":5,"description":7},"main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Freference-list-builder","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill reference-list-builder",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill reference-list-builder",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill reference-list-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Freference-list-builder\u002FSKILL.md",true,[],[44,51,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":55,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","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`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]