[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FX73MT252KCJSYXBBEMKEK":3,"skill-same:01M6FX73MT252KCJSYXBBEMKEK":71},{"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":28,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6FX73MT252KCJSYXBBEMKEK","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-...","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fprompt-library\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42],"prompt library","library","prompt","prompt templates","templates","collection","quality","user","use","prompts","community","task","Role-Based","refinement","2026-11-10 10:12:30",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-...\"\nrisk: unknown\nsource: community\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,"risk":48,"source":39,"description":7},"unknown","master","dff58085da947e81e8418c922055644bf0082b1b","other\u002Fprompt-library","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add reikiplanet\u002Fdaoskills --skill prompt-library",{"tool":63,"command":64},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill prompt-library",{"tool":66,"command":67},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill prompt-library","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fprompt-library\u002FSKILL.md",true,[],[72,98,110,123,143,166],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":43},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[79,80,81,82,83,84,39,85,86,87,88,89,90,91,92,93,94,95,96,97],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"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":104,"publishedAt":43},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[105,106,96,107,108,39,86,87,88,82,109,83],"ar","vr ar","interaction","requirements","performance",{"skillNo":111,"name":33,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":43},"01M6G60XNMHAMV1SV0EJ1CX0AY","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[33,116,117,118,119,120,39,37,88,121,122,82],"project scaffolding","From Scratch","tech","project","scaffolding","projects","applications",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":43},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[130,131,132,133,134,39,135,136,137,138,37,139,140,141,142],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":43},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[150,151,152,153,154,155,156,157,39,88,82,158,83,159,160,161,162,163,164,165],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":43},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[173,174,175,176,177,178,179,180,163,37,181,182,183,39,184,185,186,160,187,188],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]