Graph-based issue tracker that survives conversation compaction.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbeadsExecute the skills CLI command in your project's root directory to begin installation:
Fetches beads from boshu2/agentops 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 beads. Access via /beads 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
260
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
260
stars
Graph-based issue tracker that survives conversation compaction.
bd (beads) replaces markdown task lists with a dependency-aware graph stored in git.
Key Distinction:
Decision Rule: If resuming in 2 weeks would be hard without bd, use bd.
bd reads as authoritative. Use bd show, bd ready, bd list, and bd export to inspect current tracker state. Do not treat .beads/issues.jsonl as the primary decision source when live bd data is available..beads/issues.jsonl as a git-friendly export artifact. If the repo tracks .beads/issues.jsonl and you mutate tracker state, refresh it explicitly with bd export -o .beads/issues.jsonl.bd ready returns a broad umbrella issue, do not implement directly against vague parent wording. First narrow the remaining gap into an execution-ready child issue, then land the child and reconcile the parent.bd ... # mutate tracker state
bd export -o .beads/issues.jsonl # if tracked in git
bd vc status
bd dolt commit -m "..." # if tracker changes are pending
bd dolt push # only if a Dolt remote is configured
bd init run once (humans do this, not agents)User says: /vibe
What happens:
bd show <id> to read issue metadataResult: Validation report includes issue context, no manual bd lookups needed.
User says: /implement ag-xyz-123
What happens:
bd show ag-xyz-123 to read issue bodybd close ag-xyz-123 after completionResult: Issue lifecycle managed automatically during implementation.
| Problem | Cause | Solution |
|---|---|---|
| bd command not found | bd CLI not installed or not in PATH | Install bd: brew install bd or check PATH |
| "not a git repository" error | bd requires git repo, current dir not initialized | Run git init or navigate to git repo root |
| "beads not initialized" error | .beads/ directory missing | Human runs bd init --prefix <prefix> once |
| Issue ID format errors | Wrong prefix or malformed ID | Check rigs.json for correct prefix, follow <prefix>-<tag>-<num> format |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in beads — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for beads matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: beads is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend beads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
beads is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
beads reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: beads is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend beads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for beads matched our evaluation — installs cleanly and behaves as described in the markdown.
beads reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 62