[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AKVTNZJN22ASK11VC6499W":3,"skill-same:01M7AKVTNZJN22ASK11VC6499W":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AKVTNZJN22ASK11VC6499W","prompt-library",null,"Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fprompt-library\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prompt-library\ndescription: \"Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.\"\n---\n\n# 📝 Prompt Library\n\n> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Needs ready-to-use prompt templates\n- Wants role-based prompts (act as X)\n- Asks for prompt examples or inspiration\n- Needs task-specific prompt patterns\n- Wants to improve their prompting\n\n## Prompt Categories\n\n### 🎭 Role-Based Prompts\n\n#### Expert Developer\n\n```\nAct as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:\n1. Identify bugs and potential issues\n2. Suggest performance improvements\n3. Recommend better patterns\n4. Explain your reasoning clearly\nAlways prioritize readability and maintainability over cleverness.\n```\n\n#### Code Reviewer\n\n```\nAct as a senior code reviewer. Your role is to:\n1. Check for bugs, edge cases, and error handling\n2. Evaluate code structure and organization\n3. Assess naming conventions and readability\n4. Identify potential security issues\n5. Suggest improvements with specific examples\n\nFormat your review as:\n🔴 Critical Issues (must fix)\n🟡 Suggestions (should consider)\n🟢 Praise (what's done well)\n```\n\n#### Technical Writer\n\n```\nAct as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:\n- Use simple language, avoid jargon\n- Include practical examples\n- Structure with clear headings\n- Add code snippets where helpful\n- Consider the reader's experience level\n```\n\n#### System Architect\n\n```\nAct as a senior system architect designing for scale. Consider:\n- Scalability (horizontal and vertical)\n- Reliability (fault tolerance, redundancy)\n- Maintainability (modularity, clear boundaries)\n- Performance (latency, throughput)\n- Cost efficiency\n\nProvide architecture decisions with trade-off analysis.\n```\n\n### 🛠️ Task-Specific Prompts\n\n#### Debug This Code\n\n```\nDebug the following code. Your analysis should include:\n\n1. **Problem Identification**: What exactly is failing?\n2. **Root Cause**: Why is it failing?\n3. **Fix**: Provide corrected code\n4. **Prevention**: How to prevent similar bugs\n\nShow your debugging thought process step by step.\n```\n\n#### Explain Like I'm 5 (ELI5)\n\n```\nExplain [CONCEPT] as if I'm 5 years old. Use:\n- Simple everyday analogies\n- No technical jargon\n- Short sentences\n- Relatable examples from daily life\n- A fun, engaging tone\n```\n\n#### Code Refactoring\n\n```\nRefactor this code following these priorities:\n1. Readability first\n2. Remove duplication (DRY)\n3. Single responsibility per function\n4. Meaningful names\n5. Add comments only where necessary\n\nShow before\u002Fafter with explanation of changes.\n```\n\n#### Write Tests\n\n```\nWrite comprehensive tests for this code:\n1. Happy path scenarios\n2. Edge cases\n3. Error conditions\n4. Boundary values\n\nUse [FRAMEWORK] testing conventions. Include:\n- Descriptive test names\n- Arrange-Act-Assert pattern\n- Mocking where appropriate\n```\n\n#### API Documentation\n\n```\nGenerate API documentation for this endpoint including:\n- Endpoint URL and method\n- Request parameters (path, query, body)\n- Request\u002Fresponse examples\n- Error codes and meanings\n- Authentication requirements\n- Rate limits if applicable\n\nFormat as OpenAPI\u002FSwagger or Markdown.\n```\n\n### 📊 Analysis Prompts\n\n#### Code Complexity Analysis\n\n```\nAnalyze the complexity of this codebase:\n\n1. **Cyclomatic Complexity**: Identify complex functions\n2. **Coupling**: Find tightly coupled components\n3. **Cohesion**: Assess module cohesion\n4. **Dependencies**: Map critical dependencies\n5. **Technical Debt**: Highlight areas needing refactoring\n\nRate each area and provide actionable recommendations.\n```\n\n#### Performance Analysis\n\n```\nAnalyze this code for performance issues:\n\n1. **Time Complexity**: Big O analysis\n2. **Space Complexity**: Memory usage patterns\n3. **I\u002FO Bottlenecks**: Database, network, disk\n4. **Algorithmic Issues**: Inefficient patterns\n5. **Quick Wins**: Easy optimizations\n\nPrioritize findings by impact.\n```\n\n#### Security Review\n\n```\nPerform a security review of this code:\n\n1. **Input Validation**: Check all inputs\n2. **Authentication\u002FAuthorization**: Access control\n3. **Data Protection**: Sensitive data handling\n4. **Injection Vulnerabilities**: SQL, XSS, etc.\n5. **Dependencies**: Known vulnerabilities\n\nClassify issues by severity (Critical\u002FHigh\u002FMedium\u002FLow).\n```\n\n### 🎨 Creative Prompts\n\n#### Brainstorm Features\n\n```\nBrainstorm features for [PRODUCT]:\n\nFor each feature, provide:\n- Name and one-line description\n- User value proposition\n- Implementation complexity (Low\u002FMed\u002FHigh)\n- Dependencies on other features\n\nGenerate 10 ideas, then rank top 3 by impact\u002Feffort ratio.\n```\n\n#### Name Generator\n\n```\nGenerate names for [PROJECT\u002FFEATURE]:\n\nProvide 10 options in these categories:\n- Descriptive (what it does)\n- Evocative (how it feels)\n- Acronyms (memorable abbreviations)\n- Metaphorical (analogies)\n\nFor each, explain the reasoning and check domain availability patterns.\n```\n\n### 🔄 Transformation Prompts\n\n#### Migrate Code\n\n```\nMigrate this code from [SOURCE] to [TARGET]:\n\n1. Identify equivalent constructs\n2. Handle incompatible features\n3. Preserve functionality exactly\n4. Follow target language idioms\n5. Add necessary dependencies\n\nShow the migration step by step with explanations.\n```\n\n#### Convert Format\n\n```\nConvert this [SOURCE_FORMAT] to [TARGET_FORMAT]:\n\nRequirements:\n- Preserve all data\n- Use idiomatic target format\n- Handle edge cases\n- Validate the output\n- Provide sample verification\n```\n\n## Prompt Engineering Techniques\n\n### Chain of Thought (CoT)\n\n```\nLet's solve this step by step:\n1. First, I'll understand the problem\n2. Then, I'll identify the key components\n3. Next, I'll work through the logic\n4. Finally, I'll verify the solution\n\n[Your question here]\n```\n\n### Few-Shot Learning\n\n```\nHere are some examples of the task:\n\nExample 1:\nInput: [example input 1]\nOutput: [example output 1]\n\nExample 2:\nInput: [example input 2]\nOutput: [example output 2]\n\nNow complete this:\nInput: [actual input]\nOutput:\n```\n\n### Persona Pattern\n\n```\nYou are [PERSONA] with [TRAITS].\nYour communication style is [STYLE].\nYou prioritize [VALUES].\n\nWhen responding:\n- [Behavior 1]\n- [Behavior 2]\n- [Behavior 3]\n```\n\n### Structured Output\n\n```\nRespond in the following JSON format:\n{\n  \"analysis\": \"your analysis here\",\n  \"recommendations\": [\"rec1\", \"rec2\"],\n  \"confidence\": 0.0-1.0,\n  \"caveats\": [\"caveat1\"]\n}\n```\n\n## Prompt Improvement Checklist\n\nWhen crafting prompts, ensure:\n\n- [ ] **Clear objective**: What exactly do you want?\n- [ ] **Context provided**: Background information included?\n- [ ] **Format specified**: How should output be structured?\n- [ ] **Examples given**: Are there reference examples?\n- [ ] **Constraints defined**: Any limitations or requirements?\n- [ ] **Success criteria**: How do you measure good output?\n\n## Resources\n\n- [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)\n- [prompts.chat](https:\u002F\u002Fprompts.chat)\n- [Learn Prompting](https:\u002F\u002Flearnprompting.org\u002F)\n\n---\n\n> 💡 **Tip**: The best prompts are specific, provide context, and include examples of desired output.\n","# 📝 Prompt Library\n\n> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Needs ready-to-use prompt templates\n- Wants role-based prompts (act as X)\n- Asks for prompt examples or inspiration\n- Needs task-specific prompt patterns\n- Wants to improve their prompting\n\n## Prompt Categories\n\n### 🎭 Role-Based Prompts\n\n#### Expert Developer\n\n```\nAct as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:\n1. Identify bugs and potential issues\n2. Suggest performance improvements\n3. Recommend better patterns\n4. Explain your reasoning clearly\nAlways prioritize readability and maintainability over cleverness.\n```\n\n#### Code Reviewer\n\n```\nAct as a senior code reviewer. Your role is to:\n1. Check for bugs, edge cases, and error handling\n2. Evaluate code structure and organization\n3. Assess naming conventions and readability\n4. Identify potential security issues\n5. Suggest improvements with specific examples\n\nFormat your review as:\n🔴 Critical Issues (must fix)\n🟡 Suggestions (should consider)\n🟢 Praise (what's done well)\n```\n\n#### Technical Writer\n\n```\nAct as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:\n- Use simple language, avoid jargon\n- Include practical examples\n- Structure with clear headings\n- Add code snippets where helpful\n- Consider the reader's experience level\n```\n\n#### System Architect\n\n```\nAct as a senior system architect designing for scale. Consider:\n- Scalability (horizontal and vertical)\n- Reliability (fault tolerance, redundancy)\n- Maintainability (modularity, clear boundaries)\n- Performance (latency, throughput)\n- Cost efficiency\n\nProvide architecture decisions with trade-off analysis.\n```\n\n### 🛠️ Task-Specific Prompts\n\n#### Debug This Code\n\n```\nDebug the following code. Your analysis should include:\n\n1. **Problem Identification**: What exactly is failing?\n2. **Root Cause**: Why is it failing?\n3. **Fix**: Provide corrected code\n4. **Prevention**: How to prevent similar bugs\n\nShow your debugging thought process step by step.\n```\n\n#### Explain Like I'm 5 (ELI5)\n\n```\nExplain [CONCEPT] as if I'm 5 years old. Use:\n- Simple everyday analogies\n- No technical jargon\n- Short sentences\n- Relatable examples from daily life\n- A fun, engaging tone\n```\n\n#### Code Refactoring\n\n```\nRefactor this code following these priorities:\n1. Readability first\n2. Remove duplication (DRY)\n3. Single responsibility per function\n4. Meaningful names\n5. Add comments only where necessary\n\nShow before\u002Fafter with explanation of changes.\n```\n\n#### Write Tests\n\n```\nWrite comprehensive tests for this code:\n1. Happy path scenarios\n2. Edge cases\n3. Error conditions\n4. Boundary values\n\nUse [FRAMEWORK] testing conventions. Include:\n- Descriptive test names\n- Arrange-Act-Assert pattern\n- Mocking where appropriate\n```\n\n#### API Documentation\n\n```\nGenerate API documentation for this endpoint including:\n- Endpoint URL and method\n- Request parameters (path, query, body)\n- Request\u002Fresponse examples\n- Error codes and meanings\n- Authentication requirements\n- Rate limits if applicable\n\nFormat as OpenAPI\u002FSwagger or Markdown.\n```\n\n### 📊 Analysis Prompts\n\n#### Code Complexity Analysis\n\n```\nAnalyze the complexity of this codebase:\n\n1. **Cyclomatic Complexity**: Identify complex functions\n2. **Coupling**: Find tightly coupled components\n3. **Cohesion**: Assess module cohesion\n4. **Dependencies**: Map critical dependencies\n5. **Technical Debt**: Highlight areas needing refactoring\n\nRate each area and provide actionable recommendations.\n```\n\n#### Performance Analysis\n\n```\nAnalyze this code for performance issues:\n\n1. **Time Complexity**: Big O analysis\n2. **Space Complexity**: Memory usage patterns\n3. **I\u002FO Bottlenecks**: Database, network, disk\n4. **Algorithmic Issues**: Inefficient patterns\n5. **Quick Wins**: Easy optimizations\n\nPrioritize findings by impact.\n```\n\n#### Security Review\n\n```\nPerform a security review of this code:\n\n1. **Input Validation**: Check all inputs\n2. **Authentication\u002FAuthorization**: Access control\n3. **Data Protection**: Sensitive data handling\n4. **Injection Vulnerabilities**: SQL, XSS, etc.\n5. **Dependencies**: Known vulnerabilities\n\nClassify issues by severity (Critical\u002FHigh\u002FMedium\u002FLow).\n```\n\n### 🎨 Creative Prompts\n\n#### Brainstorm Features\n\n```\nBrainstorm features for [PRODUCT]:\n\nFor each feature, provide:\n- Name and one-line description\n- User value proposition\n- Implementation complexity (Low\u002FMed\u002FHigh)\n- Dependencies on other features\n\nGenerate 10 ideas, then rank top 3 by impact\u002Feffort ratio.\n```\n\n#### Name Generator\n\n```\nGenerate names for [PROJECT\u002FFEATURE]:\n\nProvide 10 options in these categories:\n- Descriptive (what it does)\n- Evocative (how it feels)\n- Acronyms (memorable abbreviations)\n- Metaphorical (analogies)\n\nFor each, explain the reasoning and check domain availability patterns.\n```\n\n### 🔄 Transformation Prompts\n\n#### Migrate Code\n\n```\nMigrate this code from [SOURCE] to [TARGET]:\n\n1. Identify equivalent constructs\n2. Handle incompatible features\n3. Preserve functionality exactly\n4. Follow target language idioms\n5. Add necessary dependencies\n\nShow the migration step by step with explanations.\n```\n\n#### Convert Format\n\n```\nConvert this [SOURCE_FORMAT] to [TARGET_FORMAT]:\n\nRequirements:\n- Preserve all data\n- Use idiomatic target format\n- Handle edge cases\n- Validate the output\n- Provide sample verification\n```\n\n## Prompt Engineering Techniques\n\n### Chain of Thought (CoT)\n\n```\nLet's solve this step by step:\n1. First, I'll understand the problem\n2. Then, I'll identify the key components\n3. Next, I'll work through the logic\n4. Finally, I'll verify the solution\n\n[Your question here]\n```\n\n### Few-Shot Learning\n\n```\nHere are some examples of the task:\n\nExample 1:\nInput: [example input 1]\nOutput: [example output 1]\n\nExample 2:\nInput: [example input 2]\nOutput: [example output 2]\n\nNow complete this:\nInput: [actual input]\nOutput:\n```\n\n### Persona Pattern\n\n```\nYou are [PERSONA] with [TRAITS].\nYour communication style is [STYLE].\nYou prioritize [VALUES].\n\nWhen responding:\n- [Behavior 1]\n- [Behavior 2]\n- [Behavior 3]\n```\n\n### Structured Output\n\n```\nRespond in the following JSON format:\n{\n  \"analysis\": \"your analysis here\",\n  \"recommendations\": [\"rec1\", \"rec2\"],\n  \"confidence\": 0.0-1.0,\n  \"caveats\": [\"caveat1\"]\n}\n```\n\n## Prompt Improvement Checklist\n\nWhen crafting prompts, ensure:\n\n- [ ] **Clear objective**: What exactly do you want?\n- [ ] **Context provided**: Background information included?\n- [ ] **Format specified**: How should output be structured?\n- [ ] **Examples given**: Are there reference examples?\n- [ ] **Constraints defined**: Any limitations or requirements?\n- [ ] **Success criteria**: How do you measure good output?\n\n## Resources\n\n- [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)\n- [prompts.chat](https:\u002F\u002Fprompts.chat)\n- [Learn Prompting](https:\u002F\u002Flearnprompting.org\u002F)\n\n---\n\n> 💡 **Tip**: The best prompts are specific, provide context, and include examples of desired output.\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fai-research\u002Fprompt-library","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill prompt-library",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill prompt-library",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill prompt-library","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fprompt-library\u002FSKILL.md",true,[],[46,53,62,69,76,83],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]