[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P0PK385D45DDWD3VEN724N":3,"skill-same:01M6P0PK385D45DDWD3VEN724N":55},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M6P0PK385D45DDWD3VEN724N","portfolio-case-study-writer",null,"Transform resume bullets into detailed portfolio case studies","shreyasbhakta\u002FCareerReboot","shreyasbhakta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55823227?v=4","01M6P0DV5QY0C5FEMNYKBD4YFJ","Shreyas Bhakta","01M6P0DV9YG9JPTG0VVGG866PP",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fportfolio-case-study-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"portfolio case study writer","portfolio","case study writer","writer","study","case","resume","case studies","transform","2026-11-10 10:12:30",false,"---\nname: portfolio-case-study-writer\ndescription: Transform resume bullets into detailed portfolio case studies\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","466b9f58403b6b473023097f5b9f3f094ebeb493","skills\u002Fresume-skills\u002Fskills\u002Fportfolio-case-study-writer","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta","shreyasbhakta.dev","Software Engineer | Backend & Distributed Systems | Java, Spring Boot, Kafka, Python | Agentic AI, LangGraph, RAG | Ex-Vymo, Ex-SIXT | Cybersecurity Enthusiast","2026-10-17 04:01:42",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add shreyasbhakta\u002FCareerReboot --skill portfolio-case-study-writer",{"tool":47,"command":48},"bunx","bunx skills add shreyasbhakta\u002FCareerReboot --skill portfolio-case-study-writer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add shreyasbhakta\u002FCareerReboot --skill portfolio-case-study-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fportfolio-case-study-writer\u002FSKILL.md",true,[],[56,80,102,117,127,138],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":28},"01M6P0SGCMXDZ5DH19S9RS4PZZ","tech-resume-optimizer","Optimize resumes for software engineering, PM, and technical roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Ftech-resume-optimizer\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[68,25,69,70,71,72,73,74,75,76,77,78,79],"tech resume optimizer","resume optimizer","optimizer","tech","software engineering","for","engineering","technical","optimize","pm","roles","software",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":28},"01M6P0SC37HWQ8CTWA37SVPAA3","salary-negotiation-prep","Research market rates, build negotiation strategy, and create counter-offer scripts","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fsalary-negotiation-prep\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[92,93,94,95,96,97,98,99,100,101],"negotiation prep","prep","negotiation","salary negotiation prep","build","scripts","Market","research","create","strategy",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":28},"01M6P0RSXGGR789TX42ZXNR09N","resume-version-manager","Track different resume versions, maintain master resume, manage tailored versions","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-version-manager\u002FSKILL.md",[108],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[110,25,111,112,113,114,115,116],"manager","version","resume version manager","master","manage","maintain","track",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":28},"01M6P0RK6FX16FYCC01T2HA2MA","resume-tailor","Customize resume for specific job postings while maintaining truthfulness","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-tailor\u002FSKILL.md",[123],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[25,125,73,126],"resume tailor","customize",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":28},"01M6P0R57S7ASRV6VAYQ4K2J9Y","resume-section-builder","Create targeted resume sections optimized for different experience levels and roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-section-builder\u002FSKILL.md",[133],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[135,136,25,137,100,78,73],"section","builder","resume section builder",{"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":145,"publishedAt":28},"01M6P0R0TVRRDSTTM047HWXNCD","resume-quantifier","Find opportunities to add metrics and estimate numbers when exact data unavailable","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-quantifier\u002FSKILL.md",[144],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[25,146,147,148,149,150,151],"resume quantifier","metrics","data","find","add","estimate"]