[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72DFJZZRRN13BGC8VB2P17Z":3,"skill-same:01M72DFJZZRRN13BGC8VB2P17Z":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72DFJZZRRN13BGC8VB2P17Z","ship-learn-next",null,"Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fship-learn-next\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: ship-learn-next\ndescription: Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.\nallowed-tools:\n  - Read\n  - Write\n---\n\n# Ship-Learn-Next Action Planner\n\nThis skill helps transform passive learning content into actionable **Ship-Learn-Next cycles** - turning advice and lessons into concrete, shippable iterations.\n\n## When to Use This Skill\n\nActivate when the user:\n- Has a transcript\u002Farticle\u002Ftutorial and wants to \"implement the advice\"\n- Asks to \"turn this into a plan\" or \"make this actionable\"\n- Wants to extract implementation steps from educational content\n- Needs help breaking down big ideas into small, shippable reps\n- Says things like \"I watched\u002Fread X, now what should I do?\"\n\n## Core Framework: Ship-Learn-Next\n\nEvery learning quest follows three repeating phases:\n\n1. **SHIP** - Create something real (code, content, product, demonstration)\n2. **LEARN** - Honest reflection on what happened\n3. **NEXT** - Plan the next iteration based on learnings\n\n**Key principle**: 100 reps beats 100 hours of study. Learning = doing better, not knowing more.\n\n## How This Skill Works\n\n### Step 1: Read the Content\n\nRead the file the user provides (transcript, article, notes):\n\n```bash\n# User provides path to file\nFILE_PATH=\"\u002Fpath\u002Fto\u002Fcontent.txt\"\n```\n\nUse the Read tool to analyze the content.\n\n### Step 2: Extract Core Lessons\n\nIdentify from the content:\n- **Main advice\u002Flessons**: What are the key takeaways?\n- **Actionable principles**: What can actually be practiced?\n- **Skills being taught**: What would someone learn by doing this?\n- **Examples\u002Fcase studies**: Real implementations mentioned\n\n**Do NOT**:\n- Summarize everything (focus on actionable parts)\n- List theory without application\n- Include \"nice to know\" vs \"need to practice\"\n\n### Step 3: Define the Quest\n\nHelp the user frame their learning goal:\n\nAsk:\n1. \"Based on this content, what do you want to achieve in 4-8 weeks?\"\n2. \"What would success look like? (Be specific)\"\n3. \"What's something concrete you could build\u002Fcreate\u002Fship?\"\n\n**Example good quest**: \"Ship 10 cold outreach messages and get 2 responses\"\n**Example bad quest**: \"Learn about sales\" (too vague)\n\n### Step 4: Design Rep 1 (The First Iteration)\n\nBreak down the quest into the **smallest shippable version**:\n\nAsk:\n- \"What's the smallest version you could ship THIS WEEK?\"\n- \"What do you need to learn JUST to do that?\" (not everything)\n- \"What would 'done' look like for rep 1?\"\n\n**Make it:**\n- Concrete and specific\n- Completable in 1-7 days\n- Produces real evidence\u002Fartifact\n- Small enough to not be intimidating\n- Big enough to learn something meaningful\n\n### Step 5: Create the Rep Plan\n\nStructure each rep with:\n\n```markdown\n## Rep 1: [Specific Goal]\n\n**Ship Goal**: [What you'll create\u002Fdo]\n**Success Criteria**: [How you'll know it's done]\n**What You'll Learn**: [Specific skills\u002Finsights]\n**Resources Needed**: [Minimal - just what's needed for THIS rep]\n**Timeline**: [Specific deadline]\n\n**Action Steps**:\n1. [Concrete step 1]\n2. [Concrete step 2]\n3. [Concrete step 3]\n...\n\n**After Shipping - Reflection Questions**:\n- What actually happened? (Be specific)\n- What worked? What didn't?\n- What surprised you?\n- On a scale of 1-10, how did this rep go?\n- What would you do differently next time?\n```\n\n### Step 6: Map Future Reps (2-5)\n\nBased on the content, suggest a progression:\n\n```markdown\n## Rep 2: [Next level]\n**Builds on**: What you learned in Rep 1\n**New challenge**: One new thing to try\u002Fimprove\n**Expected difficulty**: [Easier\u002FSame\u002FHarder - and why]\n\n## Rep 3: [Continue progression]\n...\n```\n\n**Progression principles**:\n- Each rep adds ONE new element\n- Increase difficulty based on success\n- Reference specific lessons from the content\n- Keep reps shippable (not theoretical)\n\n### Step 7: Connect to Content\n\nFor each rep, reference the source material:\n\n- \"This implements the [concept] from minute X\"\n- \"You're practicing the [technique] mentioned in the video\"\n- \"This tests the advice about [topic]\"\n\n**But**: Always emphasize DOING over studying. Point to resources only when needed for the specific rep.\n\n## Conversation Style\n\n**Direct but supportive**:\n- No fluff, but encouraging\n- \"Ship it, then we'll improve it\"\n- \"What's the smallest version you could do this week?\"\n\n**Question-driven**:\n- Make them think, don't just tell\n- \"What exactly do you want to achieve?\" not \"Here's what you should do\"\n\n**Specific, not generic**:\n- \"By Friday, ship one landing page\" not \"Learn web development\"\n- Push for concrete commitments\n\n**Action-oriented**:\n- Always end with \"what's next?\"\n- Focus on the next rep, not the whole journey\n\n## What NOT to Do\n\n- ❌ Don't create a study plan (create a SHIP plan)\n- ❌ Don't list all resources to read\u002Fwatch (pick minimal resources for current rep)\n- ❌ Don't make perfect the enemy of shipped\n- ❌ Don't let them plan forever without starting\n- ❌ Don't accept vague goals (\"learn X\" → \"ship Y by Z date\")\n- ❌ Don't overwhelm with the full journey (focus on rep 1)\n\n## Key Phrases to Use\n\n- \"What's the smallest version you could ship this week?\"\n- \"What do you need to learn JUST to do that?\"\n- \"This isn't about perfection - it's rep 1 of 100\"\n- \"Ship something real, then we'll improve it\"\n- \"Based on [content], what would you actually DO differently?\"\n- \"Learning = doing better, not knowing more\"\n\n## Example Output Structure\n\n```markdown\n# Your Ship-Learn-Next Quest: [Title]\n\n## Quest Overview\n**Goal**: [What they want to achieve in 4-8 weeks]\n**Source**: [The content that inspired this]\n**Core Lessons**: [3-5 key actionable takeaways from content]\n\n---\n\n## Rep 1: [Specific, Shippable Goal]\n\n**Ship Goal**: [Concrete deliverable]\n**Timeline**: [This week \u002F By [date]]\n**Success Criteria**:\n- [ ] [Specific thing 1]\n- [ ] [Specific thing 2]\n- [ ] [Specific thing 3]\n\n**What You'll Practice** (from the content):\n- [Skill\u002Fconcept 1 from source material]\n- [Skill\u002Fconcept 2 from source material]\n\n**Action Steps**:\n1. [Concrete step]\n2. [Concrete step]\n3. [Concrete step]\n4. Ship it (publish\u002Fdeploy\u002Fshare\u002Fdemonstrate)\n\n**Minimal Resources** (only for this rep):\n- [Link or reference - if truly needed]\n\n**After Shipping - Reflection**:\nAnswer these questions:\n- What actually happened?\n- What worked? What didn't?\n- What surprised you?\n- Rate this rep: _\u002F10\n- What's one thing to try differently next time?\n\n---\n\n## Rep 2: [Next Iteration]\n\n**Builds on**: Rep 1 + [what you learned]\n**New element**: [One new challenge\u002Fskill]\n**Ship goal**: [Next concrete deliverable]\n\n[Similar structure...]\n\n---\n\n## Rep 3-5: Future Path\n\n**Rep 3**: [Brief description]\n**Rep 4**: [Brief description]\n**Rep 5**: [Brief description]\n\n*(Details will evolve based on what you learn in Reps 1-2)*\n\n---\n\n## Remember\n\n- This is about DOING, not studying\n- Aim for 100 reps over time (not perfection on rep 1)\n- Each rep = Plan → Do → Reflect → Next\n- You learn by shipping, not by consuming\n\n**Ready to ship Rep 1?**\n```\n\n## Processing Different Content Types\n\n### YouTube Transcripts\n- Focus on advice, not stories\n- Extract concrete techniques mentioned\n- Identify case studies\u002Fexamples to replicate\n- Note timestamps for reference later (but don't require watching again)\n\n### Articles\u002FTutorials\n- Identify the \"now do this\" parts vs theory\n- Extract the specific workflow\u002Fprocess\n- Find the minimal example to start with\n\n### Course Notes\n- What's the smallest project from the course?\n- Which modules are needed for rep 1? (ignore the rest for now)\n- What can be practiced immediately?\n\n## Success Metrics\n\nA good Ship-Learn-Next plan has:\n- ✅ Specific, shippable rep 1 (completable in 1-7 days)\n- ✅ Clear success criteria (user knows when they're done)\n- ✅ Concrete artifacts (something real to show)\n- ✅ Direct connection to source content\n- ✅ Progression path for reps 2-5\n- ✅ Emphasis on action over consumption\n- ✅ Honest reflection built in\n- ✅ Small enough to start today, big enough to learn\n\n## Saving the Plan\n\n**IMPORTANT**: Always save the plan to a file for the user.\n\n### Filename Convention\n\nAlways use the format:\n- `Ship-Learn-Next Plan - [Brief Quest Title].md`\n\nExamples:\n- `Ship-Learn-Next Plan - Build in Proven Markets.md`\n- `Ship-Learn-Next Plan - Learn React.md`\n- `Ship-Learn-Next Plan - Cold Email Outreach.md`\n\n**Quest title should be**:\n- Brief (3-6 words)\n- Descriptive of the main goal\n- Based on the content's core lesson\u002Ftheme\n\n### What to Save\n\n**Complete plan including**:\n- Quest overview with goal and source\n- All reps (1-5) with full details\n- Action steps and reflection questions\n- Timeline commitments\n- Reference to source material\n\n**Format**: Always save as Markdown (`.md`) for readability\n\n## After Creating the Plan\n\n**Display to user**:\n1. Show them you've saved the plan: \"✓ Saved to: [filename]\"\n2. Give a brief overview of the quest\n3. Highlight Rep 1 (what's due this week)\n\n**Then ask**:\n1. \"When will you ship Rep 1?\"\n2. \"What's the one thing that might stop you? How will you handle it?\"\n3. \"Come back after you ship and we'll reflect + plan Rep 2\"\n\n**Remember**: You're not creating a curriculum. You're helping them ship something real, learn from it, and ship the next thing.\n\nLet's help them ship.\n","# Ship-Learn-Next Action Planner\n\nThis skill helps transform passive learning content into actionable **Ship-Learn-Next cycles** - turning advice and lessons into concrete, shippable iterations.\n\n## When to Use This Skill\n\nActivate when the user:\n- Has a transcript\u002Farticle\u002Ftutorial and wants to \"implement the advice\"\n- Asks to \"turn this into a plan\" or \"make this actionable\"\n- Wants to extract implementation steps from educational content\n- Needs help breaking down big ideas into small, shippable reps\n- Says things like \"I watched\u002Fread X, now what should I do?\"\n\n## Core Framework: Ship-Learn-Next\n\nEvery learning quest follows three repeating phases:\n\n1. **SHIP** - Create something real (code, content, product, demonstration)\n2. **LEARN** - Honest reflection on what happened\n3. **NEXT** - Plan the next iteration based on learnings\n\n**Key principle**: 100 reps beats 100 hours of study. Learning = doing better, not knowing more.\n\n## How This Skill Works\n\n### Step 1: Read the Content\n\nRead the file the user provides (transcript, article, notes):\n\n```bash\n# User provides path to file\nFILE_PATH=\"\u002Fpath\u002Fto\u002Fcontent.txt\"\n```\n\nUse the Read tool to analyze the content.\n\n### Step 2: Extract Core Lessons\n\nIdentify from the content:\n- **Main advice\u002Flessons**: What are the key takeaways?\n- **Actionable principles**: What can actually be practiced?\n- **Skills being taught**: What would someone learn by doing this?\n- **Examples\u002Fcase studies**: Real implementations mentioned\n\n**Do NOT**:\n- Summarize everything (focus on actionable parts)\n- List theory without application\n- Include \"nice to know\" vs \"need to practice\"\n\n### Step 3: Define the Quest\n\nHelp the user frame their learning goal:\n\nAsk:\n1. \"Based on this content, what do you want to achieve in 4-8 weeks?\"\n2. \"What would success look like? (Be specific)\"\n3. \"What's something concrete you could build\u002Fcreate\u002Fship?\"\n\n**Example good quest**: \"Ship 10 cold outreach messages and get 2 responses\"\n**Example bad quest**: \"Learn about sales\" (too vague)\n\n### Step 4: Design Rep 1 (The First Iteration)\n\nBreak down the quest into the **smallest shippable version**:\n\nAsk:\n- \"What's the smallest version you could ship THIS WEEK?\"\n- \"What do you need to learn JUST to do that?\" (not everything)\n- \"What would 'done' look like for rep 1?\"\n\n**Make it:**\n- Concrete and specific\n- Completable in 1-7 days\n- Produces real evidence\u002Fartifact\n- Small enough to not be intimidating\n- Big enough to learn something meaningful\n\n### Step 5: Create the Rep Plan\n\nStructure each rep with:\n\n```markdown\n## Rep 1: [Specific Goal]\n\n**Ship Goal**: [What you'll create\u002Fdo]\n**Success Criteria**: [How you'll know it's done]\n**What You'll Learn**: [Specific skills\u002Finsights]\n**Resources Needed**: [Minimal - just what's needed for THIS rep]\n**Timeline**: [Specific deadline]\n\n**Action Steps**:\n1. [Concrete step 1]\n2. [Concrete step 2]\n3. [Concrete step 3]\n...\n\n**After Shipping - Reflection Questions**:\n- What actually happened? (Be specific)\n- What worked? What didn't?\n- What surprised you?\n- On a scale of 1-10, how did this rep go?\n- What would you do differently next time?\n```\n\n### Step 6: Map Future Reps (2-5)\n\nBased on the content, suggest a progression:\n\n```markdown\n## Rep 2: [Next level]\n**Builds on**: What you learned in Rep 1\n**New challenge**: One new thing to try\u002Fimprove\n**Expected difficulty**: [Easier\u002FSame\u002FHarder - and why]\n\n## Rep 3: [Continue progression]\n...\n```\n\n**Progression principles**:\n- Each rep adds ONE new element\n- Increase difficulty based on success\n- Reference specific lessons from the content\n- Keep reps shippable (not theoretical)\n\n### Step 7: Connect to Content\n\nFor each rep, reference the source material:\n\n- \"This implements the [concept] from minute X\"\n- \"You're practicing the [technique] mentioned in the video\"\n- \"This tests the advice about [topic]\"\n\n**But**: Always emphasize DOING over studying. Point to resources only when needed for the specific rep.\n\n## Conversation Style\n\n**Direct but supportive**:\n- No fluff, but encouraging\n- \"Ship it, then we'll improve it\"\n- \"What's the smallest version you could do this week?\"\n\n**Question-driven**:\n- Make them think, don't just tell\n- \"What exactly do you want to achieve?\" not \"Here's what you should do\"\n\n**Specific, not generic**:\n- \"By Friday, ship one landing page\" not \"Learn web development\"\n- Push for concrete commitments\n\n**Action-oriented**:\n- Always end with \"what's next?\"\n- Focus on the next rep, not the whole journey\n\n## What NOT to Do\n\n- ❌ Don't create a study plan (create a SHIP plan)\n- ❌ Don't list all resources to read\u002Fwatch (pick minimal resources for current rep)\n- ❌ Don't make perfect the enemy of shipped\n- ❌ Don't let them plan forever without starting\n- ❌ Don't accept vague goals (\"learn X\" → \"ship Y by Z date\")\n- ❌ Don't overwhelm with the full journey (focus on rep 1)\n\n## Key Phrases to Use\n\n- \"What's the smallest version you could ship this week?\"\n- \"What do you need to learn JUST to do that?\"\n- \"This isn't about perfection - it's rep 1 of 100\"\n- \"Ship something real, then we'll improve it\"\n- \"Based on [content], what would you actually DO differently?\"\n- \"Learning = doing better, not knowing more\"\n\n## Example Output Structure\n\n```markdown\n# Your Ship-Learn-Next Quest: [Title]\n\n## Quest Overview\n**Goal**: [What they want to achieve in 4-8 weeks]\n**Source**: [The content that inspired this]\n**Core Lessons**: [3-5 key actionable takeaways from content]\n\n---\n\n## Rep 1: [Specific, Shippable Goal]\n\n**Ship Goal**: [Concrete deliverable]\n**Timeline**: [This week \u002F By [date]]\n**Success Criteria**:\n- [ ] [Specific thing 1]\n- [ ] [Specific thing 2]\n- [ ] [Specific thing 3]\n\n**What You'll Practice** (from the content):\n- [Skill\u002Fconcept 1 from source material]\n- [Skill\u002Fconcept 2 from source material]\n\n**Action Steps**:\n1. [Concrete step]\n2. [Concrete step]\n3. [Concrete step]\n4. Ship it (publish\u002Fdeploy\u002Fshare\u002Fdemonstrate)\n\n**Minimal Resources** (only for this rep):\n- [Link or reference - if truly needed]\n\n**After Shipping - Reflection**:\nAnswer these questions:\n- What actually happened?\n- What worked? What didn't?\n- What surprised you?\n- Rate this rep: _\u002F10\n- What's one thing to try differently next time?\n\n---\n\n## Rep 2: [Next Iteration]\n\n**Builds on**: Rep 1 + [what you learned]\n**New element**: [One new challenge\u002Fskill]\n**Ship goal**: [Next concrete deliverable]\n\n[Similar structure...]\n\n---\n\n## Rep 3-5: Future Path\n\n**Rep 3**: [Brief description]\n**Rep 4**: [Brief description]\n**Rep 5**: [Brief description]\n\n*(Details will evolve based on what you learn in Reps 1-2)*\n\n---\n\n## Remember\n\n- This is about DOING, not studying\n- Aim for 100 reps over time (not perfection on rep 1)\n- Each rep = Plan → Do → Reflect → Next\n- You learn by shipping, not by consuming\n\n**Ready to ship Rep 1?**\n```\n\n## Processing Different Content Types\n\n### YouTube Transcripts\n- Focus on advice, not stories\n- Extract concrete techniques mentioned\n- Identify case studies\u002Fexamples to replicate\n- Note timestamps for reference later (but don't require watching again)\n\n### Articles\u002FTutorials\n- Identify the \"now do this\" parts vs theory\n- Extract the specific workflow\u002Fprocess\n- Find the minimal example to start with\n\n### Course Notes\n- What's the smallest project from the course?\n- Which modules are needed for rep 1? (ignore the rest for now)\n- What can be practiced immediately?\n\n## Success Metrics\n\nA good Ship-Learn-Next plan has:\n- ✅ Specific, shippable rep 1 (completable in 1-7 days)\n- ✅ Clear success criteria (user knows when they're done)\n- ✅ Concrete artifacts (something real to show)\n- ✅ Direct connection to source content\n- ✅ Progression path for reps 2-5\n- ✅ Emphasis on action over consumption\n- ✅ Honest reflection built in\n- ✅ Small enough to start today, big enough to learn\n\n## Saving the Plan\n\n**IMPORTANT**: Always save the plan to a file for the user.\n\n### Filename Convention\n\nAlways use the format:\n- `Ship-Learn-Next Plan - [Brief Quest Title].md`\n\nExamples:\n- `Ship-Learn-Next Plan - Build in Proven Markets.md`\n- `Ship-Learn-Next Plan - Learn React.md`\n- `Ship-Learn-Next Plan - Cold Email Outreach.md`\n\n**Quest title should be**:\n- Brief (3-6 words)\n- Descriptive of the main goal\n- Based on the content's core lesson\u002Ftheme\n\n### What to Save\n\n**Complete plan including**:\n- Quest overview with goal and source\n- All reps (1-5) with full details\n- Action steps and reflection questions\n- Timeline commitments\n- Reference to source material\n\n**Format**: Always save as Markdown (`.md`) for readability\n\n## After Creating the Plan\n\n**Display to user**:\n1. Show them you've saved the plan: \"✓ Saved to: [filename]\"\n2. Give a brief overview of the quest\n3. Highlight Rep 1 (what's due this week)\n\n**Then ask**:\n1. \"When will you ship Rep 1?\"\n2. \"What's the one thing that might stop you? How will you handle it?\"\n3. \"Come back after you ship and we'll reflect + plan Rep 2\"\n\n**Remember**: You're not creating a curriculum. You're helping them ship something real, learn from it, and ship the next thing.\n\nLet's help them ship.\n",{"name":5,"description":7,"allowed-tools":23},[24,25],"Read","Write","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fship-learn-next","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Sansar35\u002Fclaude-agent --skill ship-learn-next",{"tool":38,"command":39},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill ship-learn-next",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill ship-learn-next","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fship-learn-next\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},".skill-source.json","REFERENCE","参考文档",502,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fship-learn-next\u002F.skill-source.json",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"README.md",6796,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fship-learn-next\u002FREADME.md",[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]