mcpbeat

Reference SDK

parcadei/reference-sdk

Check reference SDK implementations using btca ask

375 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3880
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill reference-sdk

The instruction itself

6 sections, as written by the author

Reference SDK Check

When implementing SDK features or debugging provider-specific issues, check reference implementations.

When to Use

  • Implementing SDK features
  • Debugging provider-specific issues
  • Understanding how other libraries solve similar problems
  • "How does Vercel AI SDK do X?"
  • "Check Anthropic SDK for Y"

Commands

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?"

Configured Resources

  • vercel-ai - Streaming, tool calling, structured output
  • anthropic-sdk - Anthropic API patterns
  • zod - Schema validation

Add more: btca config resources add -n <name> -t git -u <url> -b <branch>

When to Check

  • Before implementing - See how others solved similar problems
  • When debugging - Find how reference code handles edge cases
  • Multi-provider support - Compare implementations across SDKs
  • Validation patterns - Check idiomatic approaches

Don't Use For

  • Documentation lookups (use /nia-docs instead)
  • Simple API questions (use WebSearch)
  • Project-specific patterns (use Grep/Glob)

How to use it

Copy the folder

Take parcadei/reference-sdk from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.