When implementing SDK features or debugging provider-specific issues, check reference implementations.
Works with
When implementing SDK features or debugging provider-specific issues, check reference implementations.
Use btca ask to check how reference SDKs implement similar features:
# Check Vercel AI SDK for streaming patterns
btca ask -r vercel-ai -q "How does streamObject work?"
# Check Anthropic SDK for tool calling
btca ask -r anthropic-sdk -q "How are tools defined and called?"
# Check Zod for validation patterns
btca ask -r zod -q "How does safeParse handle errors?"
vercel-ai - Streaming, tool calling, structured outputanthropic-sdk - Anthropic API patternszod - Schema validationAdd more: btca config resources add -n <name> -t git -u <url> -b <branch>
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreference-sdkExecute the skills CLI command in your project's root directory to begin installation:
Fetches reference-sdk from parcadei/continuous-claude-v3 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 reference-sdk. Access via /reference-sdk 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
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
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.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
reference-sdk fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for reference-sdk matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in reference-sdk — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend reference-sdk for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added reference-sdk from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for reference-sdk matched our evaluation — installs cleanly and behaves as described in the markdown.
reference-sdk reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added reference-sdk from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend reference-sdk for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
reference-sdk fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 74