[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYR8BQQYCYMYM1CMFC4ZRH":3,"skill-same:01M6BYR8BQQYCYMYM1CMFC4ZRH":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6BYR8BQQYCYMYM1CMFC4ZRH","prototype",null,"Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","Vortex375\u002Fseraph","Vortex375","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5016523?v=4","01M6BYMHA5FQE4EMD6BSZ13M46","Benjamin Schmitz","01M6BYMHEYGQ7DM3Q8A7KBNZ48",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"when","design","throwaway","state model","answer","sanity","logic","build","look","use","user","question","check","model","explore","ui","state","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":46,"description":47},"portfolio-case-study-writer","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.","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","app\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype",0,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph","https:\u002F\u002Fgithub.com\u002FVortex375","2026-11-08 18:46:14",{"source":8,"skillName":46,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Vortex375\u002Fseraph --skill portfolio-case-study-writer",{"tool":61,"command":62},"bunx","bunx skills add Vortex375\u002Fseraph --skill portfolio-case-study-writer",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Vortex375\u002Fseraph --skill portfolio-case-study-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",100,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002Fagents\u002Fopenai.yaml",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"LOGIC.md",6036,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FLOGIC.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"UI.md",6913,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fprototype\u002FUI.md",[84,104,129,154,170,188],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":98,"publishedAt":41},"01M6BYS1QVW7F887EXS5RR34TA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[99,100,101,24,33,102,103],"writing","for","writing for agents","editing","documents",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":41},"01M6BYRZNREK0C7V6Y43AKDJWW","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[106,111,112,113,114,115,116,117,24,118,119,100,120,121,122,123,124,125,33,126,127,128],"provisioning","ci","generate","infrastructure","dashboard","can","running","invoke","party","credentials","human","provisioning infrastructure","migration","up","only","interactive","Bash","secrets",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":41},"01M6BYRY92S448X31PTG25TCJC","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[131,136,137,138,116,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"at","map","agent session","time","true","shared","more","tickets","as","clear","issue","session","one at a time","work","decision","plan","chunk","tracker",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":41},"01M6BYRWXMYWB6PD7E9PAD44M4","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[161,162,163,140,164,165,166,167,168,169],"wait what","wait","re","last","it","pitch","message","stop","land",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":41},"01M6BYRTS6JNDYB7BZVAWK7JJ9","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[172,177,178,179,180,181,182,183,40,184,185,186,140,187],"machine","roles","grill","ready","write","verify","issues","move","prs","state machine","briefs",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":41},"01M6BYRRRCDHNXH2YBDTYJPG36","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[195,143,196,197,198,140,199,200,144,201,153,202,151,203,204],"to tickets","spec","links","break","native","ticket","conversation","text","SET","file"]