Transform learning content into concrete, shippable implementation cycles using the Ship-Learn-Next framework.
Works with
Converts passive content (transcripts, articles, tutorials) into actionable rep-based plans with specific weekly goals and success criteria
Structures learning as repeating cycles: Ship (create something real), Learn (reflect honestly), Next (iterate based on insights)
Emphasizes doing over studying—each rep produces a tangible artifact and builds one new skill, designed to
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionship-learn-nextExecute the skills CLI command in your project's root directory to begin installation:
Fetches ship-learn-next from softaworks/agent-toolkit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ship-learn-next. Access via /ship-learn-next in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
1.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.4K
stars
This skill helps transform passive learning content into actionable Ship-Learn-Next cycles - turning advice and lessons into concrete, shippable iterations.
Activate when the user:
Every learning quest follows three repeating phases:
Key principle: 100 reps beats 100 hours of study. Learning = doing better, not knowing more.
Read the file the user provides (transcript, article, notes):
# User provides path to file
FILE_PATH="/path/to/content.txt"
Use the Read tool to analyze the content.
Identify from the content:
Do NOT:
Help the user frame their learning goal:
Ask:
Example good quest: "Ship 10 cold outreach messages and get 2 responses" Example bad quest: "Learn about sales" (too vague)
Break down the quest into the smallest shippable version:
Ask:
Make it:
Structure each rep with:
## Rep 1: [Specific Goal]
**Ship Goal**: [What you'll create/do]
**Success Criteria**: [How you'll know it's done]
**What You'll Learn**: [Specific skills/insights]
**Resources Needed**: [Minimal - just what's needed for THIS rep]
**Timeline**: [Specific deadline]
**Action Steps**:
1. [Concrete step 1]
2. [Concrete step 2]
3. [Concrete step 3]
...
**After Shipping - Reflection Questions**:
- What actually happened? (Be specific)
- What worked? What didn't?
- What surprised you?
- On a scale of 1-10, how did this rep go?
- What would you do differently next time?
Based on the content, suggest a progression:
## Rep 2: [Next level]
**Builds on**: What you learned in Rep 1
**New challenge**: One new thing to try/improve
**Expected difficulty**: [Easier/Same/Harder - and why]
## Rep 3: [Continue progression]
...
Progression principles:
For each rep, reference the source material:
But: Always emphasize DOING over studying. Point to resources only when needed for the specific rep.
Direct but supportive:
Question-driven:
Specific, not generic:
Action-oriented:
# Your Ship-Learn-Next Quest: [Title]
## Quest Overview
**Goal**: [What they want to achieve in 4-8 weeks]
**Source**: [The content that inspired this]
**Core Lessons**: [3-5 key actionable takeaways from content]
---
## Rep 1: [Specific, Shippable Goal]
**Ship Goal**: [Concrete deliverable]
**Timeline**: [This week / By [date]]
**Success Criteria**:
- [ ] [Specific thing 1]
- [ ] [Specific thing 2]
- [ ] [Specific thing 3]
**What You'll Practice** (from the content):
- [Skill/concept 1 from source material]
- [Skill/concept 2 from source material]
**Action Steps**:
1. [Concrete step]
2. [Concrete step]
3. [Concrete step]
4. Ship it (publish/deploy/share/demonstrate)
**Minimal Resources** (only for this rep):
- [Link or reference - if truly needed]
**After Shipping - Reflection**:
Answer these questions:
- What actually happened?
- What worked? What didn't?
- What surprised you?
- Rate this rep: _/10
- What's one thing to try differently next time?
---
## Rep 2: [Next Iteration]
**Builds on**: Rep 1 + [what you learned]
**New element**: [One new challenge/skill]
**Ship goal**: [Next concrete deliverable]
[Similar structure...]
---
## Rep 3-5: Future Path
**Rep 3**: [Brief description]
**Rep 4**: [Brief description]
**Rep 5**: [Brief description]
*(Details will evolve based on what you learn in Reps 1-2)*
---
## Remember
- This is about DOING, not studying
- Aim for 100 reps over time (not perfection on rep 1)
- Each rep = Plan → Do → Reflect → Next
- You learn by shipping, not by consuming
**Ready to ship Rep 1?**
A good Ship-Learn-Next plan has:
IMPORTANT: Always save the plan to a file for the user.
Always use the format:
Ship-Learn-Next Plan - [Brief Quest Title].mdExamples:
Ship-Learn-Next Plan - Build in Proven Markets.mdShip-Learn-Next Plan - Learn React.mdShip-Learn-Next Plan - Cold Email Outreach.mdQuest title should be:
Complete plan including:
Format: Always save as Markdown (.md) for readability
Display to user:
Then ask:
Remember: You're not creating a curriculum. You're helping them ship something real, learn from it, and ship the next thing.
Let's help them ship.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
vercel-labs/next-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
Keeps context tight: ship-learn-next is the kind of skill you can hand to a new teammate without a long onboarding doc.
ship-learn-next is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for ship-learn-next matched our evaluation — installs cleanly and behaves as described in the markdown.
ship-learn-next fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in ship-learn-next — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
ship-learn-next has been reliable in day-to-day use. Documentation quality is above average for community skills.
ship-learn-next fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
ship-learn-next has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: ship-learn-next is the kind of skill you can hand to a new teammate without a long onboarding doc.
ship-learn-next reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 31