[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE4NEHCE5SQZ67N7YG29WR":3,"skill-same:01M6AE4NEHCE5SQZ67N7YG29WR":82},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6AE4NEHCE5SQZ67N7YG29WR","portfolio-case-study-writer",null,"Transform resume bullets into detailed portfolio case studies with context, action, and outcome. Use when the user mentions portfolio, case study, project write-up, or expanding a resume bullet into a longer narrative.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fportfolio-case-study-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"portfolio case study writer","case","portfolio","case study writer","writer","study","when","action","with","transform","narrative","project","case studies","resume","up","use","outcome","user","context","write","2026-11-10 10:12:30",false,"---\nname: portfolio-case-study-writer\ndescription: Transform resume bullets into detailed portfolio case studies with context, action, and outcome. Use when the user mentions portfolio, case study, project write-up, or expanding a resume bullet into a longer narrative.\n---\n\n# Portfolio Case Study Writer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Wants to create portfolio case studies\n- Needs to expand resume bullets into detailed writeups\n- Is building a portfolio website\n- Wants to showcase project work in depth\n- Mentions: \"case study\", \"portfolio\", \"project writeup\", \"work samples\", \"portfolio piece\"\n\n## Core Capabilities\n\n- Transform resume bullets into detailed case studies\n- Structure case studies for maximum impact\n- Create compelling project narratives\n- Balance technical detail with business context\n- Format for portfolio websites\n- Tailor depth to audience\n\n## Case Study Purpose\n\n**Why Case Studies Matter:**\n- Resumes show WHAT you did; case studies show HOW and WHY\n- Demonstrate thinking process, not just outcomes\n- Allow deeper showcase of skills\n- Differentiate you from other candidates\n- Required for many PM, UX, and creative roles\n\n## The Case Study Structure\n\n### Standard Structure\n\n```\n1. Overview (Project summary)\n2. Problem (What needed to be solved)\n3. Process (How you approached it)\n4. Solution (What you created\u002Fdelivered)\n5. Results (The impact)\n6. Learnings (What you'd do differently)\n```\n\n### Time to Read\n- **Quick Read:** 3-5 minutes (essential for portfolio)\n- **Deep Dive:** 10-15 minutes (for interested readers)\n\n## Section-by-Section Guide\n\n### 1. Overview Section\n\n**Purpose:** Hook the reader, provide context\n\n**Include:**\n- Project name and company\n- Your role\n- Timeline\n- Team size\n- One-sentence summary of impact\n\n**Example:**\n```\n# Redesigning the Checkout Flow\n\n**Company:** E-Commerce Inc.\n**Role:** Lead Product Designer\n**Timeline:** 6 weeks\n**Team:** 2 designers, 3 engineers, 1 PM\n\n**Summary:** Reduced cart abandonment by 35% through a streamlined 3-step checkout process, generating $2M in recovered revenue.\n```\n\n### 2. Problem Section\n\n**Purpose:** Set up why this work mattered\n\n**Include:**\n- Business context\n- User pain points\n- Key metrics or goals\n- Constraints\n\n**Example:**\n```\n## The Problem\n\nE-Commerce Inc. was experiencing 68% cart abandonment—significantly higher than the industry average of 55%. Exit surveys and user research revealed several issues:\n\n- **Too many steps:** Our checkout had 7 screens\n- **Forced account creation:** Users had to register before purchasing\n- **Hidden costs:** Shipping wasn't shown until step 5\n- **Mobile friction:** Forms weren't optimized for mobile\n\n**Goal:** Reduce cart abandonment to below 50% within 3 months.\n\n**Constraints:**\n- No changes to existing payment integrations\n- Had to maintain PCI compliance\n- 6-week timeline before holiday season\n```\n\n### 3. Process Section\n\n**Purpose:** Show your thinking and methodology\n\n**Include:**\n- Research conducted\n- Stakeholders involved\n- Hypotheses formed\n- Options considered\n- Decisions made (and why)\n\n**Example:**\n```\n## Process\n\n### Research\nI started by understanding the problem deeply:\n- Analyzed Mixpanel funnel data for drop-off points\n- Conducted 10 user interviews with recent abandoners\n- Reviewed heatmaps and session recordings\n- Benchmarked against 5 competitor checkout flows\n\n**Key Insight:** 73% of drop-offs occurred at the account creation screen. Users wanted to purchase, not commit to a relationship.\n\n### Ideation\nI explored several approaches:\n1. Guest checkout only (simplest)\n2. Social login options (lower friction)\n3. Progressive profiling (collect info over time)\n4. One-page checkout (Amazon-style)\n\nAfter weighing feasibility, timeline, and impact, we chose a hybrid approach...\n\n### Decisions Made\n- **Guest checkout first:** Made registration optional and post-purchase\n- **Transparent pricing:** Showed shipping on the first screen\n- **Mobile-first design:** Designed for mobile, then adapted for desktop\n- **Progress indicator:** Added clear \"Step 1 of 3\" indicator\n```\n\n### 4. Solution Section\n\n**Purpose:** Show what you actually created\n\n**Include:**\n- Visual artifacts (mockups, screenshots, diagrams)\n- Key features\u002Fchanges\n- Technical implementation (if relevant)\n- How it addressed the problems\n\n**Example:**\n```\n## Solution\n\n### The New Checkout Flow\n\n**Before:** 7 screens with mandatory registration\n**After:** 3 screens with optional guest checkout\n\n[IMAGE: Before\u002FAfter comparison]\n\n### Key Changes\n\n**1. Transparent Pricing Widget**\n[IMAGE: Pricing widget mockup]\nShowed order total, shipping, and taxes from the start. No surprises.\n\n**2. Guest Checkout Option**\n[IMAGE: Guest checkout screen]\nMade account creation optional with clear value proposition for why to register.\n\n**3. Smart Form Design**\n[IMAGE: Form design]\n- Single-column layout on mobile\n- Auto-format for phone\u002Fcard numbers\n- Address autocomplete integration\n- Clear error messaging\n\n**4. Trust Signals**\nAdded security badges, money-back guarantee, and customer service contact throughout the flow.\n```\n\n### 5. Results Section\n\n**Purpose:** Prove impact with data\n\n**Include:**\n- Quantitative results (with timeframe)\n- Comparison to goals\n- Secondary metrics affected\n- Business impact\n\n**Example:**\n```\n## Results\n\n### Primary Metrics (90 days post-launch)\n\n| Metric | Before | After | Change |\n|--------|--------|-------|--------|\n| Cart Abandonment | 68% | 44% | -35% |\n| Checkout Completion | 32% | 56% | +75% |\n| Mobile Conversion | 18% | 41% | +128% |\n| Revenue per Visitor | $2.40 | $3.85 | +60% |\n\n### Business Impact\n- **$2M additional revenue** in first quarter\n- **15% increase in mobile orders**\n- **Customer support tickets about checkout** dropped by 45%\n\n### Secondary Effects\n- Account creation actually increased 20% (post-purchase)\n- Average order value stayed stable\n- Return customer rate improved\n```\n\n### 6. Learnings Section\n\n**Purpose:** Show growth mindset and self-awareness\n\n**Include:**\n- What worked well\n- What you'd do differently\n- Unexpected challenges\n- Skills developed\n\n**Example:**\n```\n## Learnings\n\n### What Worked\n- **Early user research** prevented us from building the wrong solution\n- **Cross-functional alignment** meetings kept everyone on the same page\n- **Launching with analytics** let us measure impact immediately\n\n### What I'd Do Differently\n- **More A\u002FB testing:** We launched the full redesign at once. Would have preferred to test individual changes to understand what drove results.\n- **Earlier mobile focus:** We designed desktop-first then adapted. Starting mobile-first would have been more efficient.\n- **Stakeholder education:** Spent too long convincing leadership. Would start stakeholder alignment earlier next time.\n\n### Skills Developed\n- Advanced Figma prototyping\n- Working with A\u002FB testing frameworks\n- Presenting data-driven design decisions to executives\n```\n\n## Case Study Types by Role\n\n### Product Manager Case Study\n**Focus on:**\n- Strategy and prioritization\n- Stakeholder management\n- Metrics and outcomes\n- Technical trade-offs\n\n### UX\u002FProduct Designer Case Study\n**Focus on:**\n- User research\n- Design process\n- Visual artifacts\n- Usability improvements\n\n### Software Engineer Case Study\n**Focus on:**\n- Technical architecture\n- Problem-solving approach\n- System design\n- Code quality\u002Fperformance\n\n### Marketing Case Study\n**Focus on:**\n- Strategy and targeting\n- Creative execution\n- Channel performance\n- ROI and attribution\n\n## Visual Elements\n\n### Must-Have Visuals\n- Before\u002Fafter comparisons\n- Key screens or deliverables\n- Process diagrams\n- Results charts\n\n### Nice-to-Have Visuals\n- User journey maps\n- Wireframes evolution\n- Research artifacts\n- Team photos\n\n### Visual Tips\n- Use consistent image sizing\n- Add captions explaining each image\n- Blur sensitive data if needed\n- Ensure mobile-friendly image sizes\n\n## Output Format\n\nWhen creating a case study:\n\n```markdown\n# CASE STUDY: [PROJECT NAME]\n\n## Quick Facts\n- **Role:** [Your role]\n- **Company:** [Company]\n- **Timeline:** [Duration]\n- **Team:** [Team composition]\n- **Impact:** [One-line result]\n\n---\n\n## Overview\n[2-3 sentence summary of the project]\n\n## Problem\n[Context and challenges - what needed to be solved]\n\n## Process\n### Research\n[What you learned]\n\n### Approach\n[How you tackled it]\n\n### Key Decisions\n[Important choices and rationale]\n\n## Solution\n[What you built\u002Fcreated - include visual descriptions]\n\n### Feature 1\n[Description]\n\n### Feature 2\n[Description]\n\n## Results\n[Quantified impact]\n\n| Metric | Before | After | Change |\n|--------|--------|-------|--------|\n\n## Learnings\n[Reflections and growth]\n\n---\n\n## Visual Asset List\n[List of images\u002Fscreenshots needed]\n```\n\n## Case Study Quality Checklist\n\n- ✅ Clear problem statement\n- ✅ Evidence of user\u002Fcustomer focus\n- ✅ Process clearly explained\n- ✅ Your specific contributions are clear\n- ✅ Quantified results\n- ✅ Visual artifacts included\n- ✅ Honest about challenges\u002Flearnings\n- ✅ Appropriate length (3-10 min read)\n- ✅ Proofread and polished\n- ✅ Can discuss in detail in interview\n","# Portfolio Case Study Writer\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Wants to create portfolio case studies\n- Needs to expand resume bullets into detailed writeups\n- Is building a portfolio website\n- Wants to showcase project work in depth\n- Mentions: \"case study\", \"portfolio\", \"project writeup\", \"work samples\", \"portfolio piece\"\n\n## Core Capabilities\n\n- Transform resume bullets into detailed case studies\n- Structure case studies for maximum impact\n- Create compelling project narratives\n- Balance technical detail with business context\n- Format for portfolio websites\n- Tailor depth to audience\n\n## Case Study Purpose\n\n**Why Case Studies Matter:**\n- Resumes show WHAT you did; case studies show HOW and WHY\n- Demonstrate thinking process, not just outcomes\n- Allow deeper showcase of skills\n- Differentiate you from other candidates\n- Required for many PM, UX, and creative roles\n\n## The Case Study Structure\n\n### Standard Structure\n\n```\n1. Overview (Project summary)\n2. Problem (What needed to be solved)\n3. Process (How you approached it)\n4. Solution (What you created\u002Fdelivered)\n5. Results (The impact)\n6. Learnings (What you'd do differently)\n```\n\n### Time to Read\n- **Quick Read:** 3-5 minutes (essential for portfolio)\n- **Deep Dive:** 10-15 minutes (for interested readers)\n\n## Section-by-Section Guide\n\n### 1. Overview Section\n\n**Purpose:** Hook the reader, provide context\n\n**Include:**\n- Project name and company\n- Your role\n- Timeline\n- Team size\n- One-sentence summary of impact\n\n**Example:**\n```\n# Redesigning the Checkout Flow\n\n**Company:** E-Commerce Inc.\n**Role:** Lead Product Designer\n**Timeline:** 6 weeks\n**Team:** 2 designers, 3 engineers, 1 PM\n\n**Summary:** Reduced cart abandonment by 35% through a streamlined 3-step checkout process, generating $2M in recovered revenue.\n```\n\n### 2. Problem Section\n\n**Purpose:** Set up why this work mattered\n\n**Include:**\n- Business context\n- User pain points\n- Key metrics or goals\n- Constraints\n\n**Example:**\n```\n## The Problem\n\nE-Commerce Inc. was experiencing 68% cart abandonment—significantly higher than the industry average of 55%. Exit surveys and user research revealed several issues:\n\n- **Too many steps:** Our checkout had 7 screens\n- **Forced account creation:** Users had to register before purchasing\n- **Hidden costs:** Shipping wasn't shown until step 5\n- **Mobile friction:** Forms weren't optimized for mobile\n\n**Goal:** Reduce cart abandonment to below 50% within 3 months.\n\n**Constraints:**\n- No changes to existing payment integrations\n- Had to maintain PCI compliance\n- 6-week timeline before holiday season\n```\n\n### 3. Process Section\n\n**Purpose:** Show your thinking and methodology\n\n**Include:**\n- Research conducted\n- Stakeholders involved\n- Hypotheses formed\n- Options considered\n- Decisions made (and why)\n\n**Example:**\n```\n## Process\n\n### Research\nI started by understanding the problem deeply:\n- Analyzed Mixpanel funnel data for drop-off points\n- Conducted 10 user interviews with recent abandoners\n- Reviewed heatmaps and session recordings\n- Benchmarked against 5 competitor checkout flows\n\n**Key Insight:** 73% of drop-offs occurred at the account creation screen. Users wanted to purchase, not commit to a relationship.\n\n### Ideation\nI explored several approaches:\n1. Guest checkout only (simplest)\n2. Social login options (lower friction)\n3. Progressive profiling (collect info over time)\n4. One-page checkout (Amazon-style)\n\nAfter weighing feasibility, timeline, and impact, we chose a hybrid approach...\n\n### Decisions Made\n- **Guest checkout first:** Made registration optional and post-purchase\n- **Transparent pricing:** Showed shipping on the first screen\n- **Mobile-first design:** Designed for mobile, then adapted for desktop\n- **Progress indicator:** Added clear \"Step 1 of 3\" indicator\n```\n\n### 4. Solution Section\n\n**Purpose:** Show what you actually created\n\n**Include:**\n- Visual artifacts (mockups, screenshots, diagrams)\n- Key features\u002Fchanges\n- Technical implementation (if relevant)\n- How it addressed the problems\n\n**Example:**\n```\n## Solution\n\n### The New Checkout Flow\n\n**Before:** 7 screens with mandatory registration\n**After:** 3 screens with optional guest checkout\n\n[IMAGE: Before\u002FAfter comparison]\n\n### Key Changes\n\n**1. Transparent Pricing Widget**\n[IMAGE: Pricing widget mockup]\nShowed order total, shipping, and taxes from the start. No surprises.\n\n**2. Guest Checkout Option**\n[IMAGE: Guest checkout screen]\nMade account creation optional with clear value proposition for why to register.\n\n**3. Smart Form Design**\n[IMAGE: Form design]\n- Single-column layout on mobile\n- Auto-format for phone\u002Fcard numbers\n- Address autocomplete integration\n- Clear error messaging\n\n**4. Trust Signals**\nAdded security badges, money-back guarantee, and customer service contact throughout the flow.\n```\n\n### 5. Results Section\n\n**Purpose:** Prove impact with data\n\n**Include:**\n- Quantitative results (with timeframe)\n- Comparison to goals\n- Secondary metrics affected\n- Business impact\n\n**Example:**\n```\n## Results\n\n### Primary Metrics (90 days post-launch)\n\n| Metric | Before | After | Change |\n|--------|--------|-------|--------|\n| Cart Abandonment | 68% | 44% | -35% |\n| Checkout Completion | 32% | 56% | +75% |\n| Mobile Conversion | 18% | 41% | +128% |\n| Revenue per Visitor | $2.40 | $3.85 | +60% |\n\n### Business Impact\n- **$2M additional revenue** in first quarter\n- **15% increase in mobile orders**\n- **Customer support tickets about checkout** dropped by 45%\n\n### Secondary Effects\n- Account creation actually increased 20% (post-purchase)\n- Average order value stayed stable\n- Return customer rate improved\n```\n\n### 6. Learnings Section\n\n**Purpose:** Show growth mindset and self-awareness\n\n**Include:**\n- What worked well\n- What you'd do differently\n- Unexpected challenges\n- Skills developed\n\n**Example:**\n```\n## Learnings\n\n### What Worked\n- **Early user research** prevented us from building the wrong solution\n- **Cross-functional alignment** meetings kept everyone on the same page\n- **Launching with analytics** let us measure impact immediately\n\n### What I'd Do Differently\n- **More A\u002FB testing:** We launched the full redesign at once. Would have preferred to test individual changes to understand what drove results.\n- **Earlier mobile focus:** We designed desktop-first then adapted. Starting mobile-first would have been more efficient.\n- **Stakeholder education:** Spent too long convincing leadership. Would start stakeholder alignment earlier next time.\n\n### Skills Developed\n- Advanced Figma prototyping\n- Working with A\u002FB testing frameworks\n- Presenting data-driven design decisions to executives\n```\n\n## Case Study Types by Role\n\n### Product Manager Case Study\n**Focus on:**\n- Strategy and prioritization\n- Stakeholder management\n- Metrics and outcomes\n- Technical trade-offs\n\n### UX\u002FProduct Designer Case Study\n**Focus on:**\n- User research\n- Design process\n- Visual artifacts\n- Usability improvements\n\n### Software Engineer Case Study\n**Focus on:**\n- Technical architecture\n- Problem-solving approach\n- System design\n- Code quality\u002Fperformance\n\n### Marketing Case Study\n**Focus on:**\n- Strategy and targeting\n- Creative execution\n- Channel performance\n- ROI and attribution\n\n## Visual Elements\n\n### Must-Have Visuals\n- Before\u002Fafter comparisons\n- Key screens or deliverables\n- Process diagrams\n- Results charts\n\n### Nice-to-Have Visuals\n- User journey maps\n- Wireframes evolution\n- Research artifacts\n- Team photos\n\n### Visual Tips\n- Use consistent image sizing\n- Add captions explaining each image\n- Blur sensitive data if needed\n- Ensure mobile-friendly image sizes\n\n## Output Format\n\nWhen creating a case study:\n\n```markdown\n# CASE STUDY: [PROJECT NAME]\n\n## Quick Facts\n- **Role:** [Your role]\n- **Company:** [Company]\n- **Timeline:** [Duration]\n- **Team:** [Team composition]\n- **Impact:** [One-line result]\n\n---\n\n## Overview\n[2-3 sentence summary of the project]\n\n## Problem\n[Context and challenges - what needed to be solved]\n\n## Process\n### Research\n[What you learned]\n\n### Approach\n[How you tackled it]\n\n### Key Decisions\n[Important choices and rationale]\n\n## Solution\n[What you built\u002Fcreated - include visual descriptions]\n\n### Feature 1\n[Description]\n\n### Feature 2\n[Description]\n\n## Results\n[Quantified impact]\n\n| Metric | Before | After | Change |\n|--------|--------|-------|--------|\n\n## Learnings\n[Reflections and growth]\n\n---\n\n## Visual Asset List\n[List of images\u002Fscreenshots needed]\n```\n\n## Case Study Quality Checklist\n\n- ✅ Clear problem statement\n- ✅ Evidence of user\u002Fcustomer focus\n- ✅ Process clearly explained\n- ✅ Your specific contributions are clear\n- ✅ Quantified results\n- ✅ Visual artifacts included\n- ✅ Honest about challenges\u002Flearnings\n- ✅ Appropriate length (3-10 min read)\n- ✅ Proofread and polished\n- ✅ Can discuss in detail in interview\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fportfolio-case-study-writer",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add davila7\u002Fclaude-code-templates --skill portfolio-case-study-writer",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill portfolio-case-study-writer",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill portfolio-case-study-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcareer\u002Fportfolio-case-study-writer\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",100,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002Fagents\u002Fopenai.yaml",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"LOGIC.md",6036,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FLOGIC.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"UI.md",6913,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FUI.md",[83,112,138,171,206,230],{"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":94,"publishedAt":39},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[95,96,97,98,99,100,101,102,34,25,103,27,104,105,106,107,108,109,110,111],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":39},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[118],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[120,121,122,123,124,125,126,127,30,128,129,25,130,131,132,133,134,135,136,137],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"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":153,"publishedAt":39},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[144,147,148],{"categoryNo":145,"categoryName":146,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[154,155,156,157,158,159,160,100,161,162,163,164,165,166,167,34,168,169,25,170],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":39},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,100,205],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":217,"publishedAt":39},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[213,216],{"categoryNo":214,"categoryName":215,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":180,"categoryName":181,"taxonomyType":92,"taxonomyTypeDesc":93},[218,219,220,221,222,184,223,193,194,224,225,226,227,100,228,27,229],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":234,"sourceHtmlUrl":235,"categories":236,"keywords":244,"publishedAt":39},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[237,240,241],{"categoryNo":238,"categoryName":239,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":242,"categoryName":243,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000036","内容创作者",[245,246,247,248,249,250,251,252,186,253,196,130,254,255,256,257,33,166,258,25,259,260,261,262,263,109,264],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]