reference-sdk
Searches SDK repositories to help developers understand idiomatic patterns and handle provider-specific edge cases.
Install
mkdir -p .claude/skills/reference-sdk && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4621" && unzip -o skill.zip -d .claude/skills/reference-sdk && rm skill.zipInstalls to .claude/skills/reference-sdk
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Check reference SDK implementations using btca askKey capabilities
- →Query reference SDK implementations
- →Standardize tool-calling patterns
- →Compare provider-specific API handling
- →Validate schema implementation
How it works
Uses the btca ask command to query structured reference repositories and extract specific implementation patterns.
Inputs & outputs
When to use reference-sdk
- →Find streaming patterns in Vercel AI SDK
- →Check Anthropic SDK tool calling patterns
- →Understand validation with Zod
About this skill
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 outputanthropic-sdk- Anthropic API patternszod- 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)
When not to use it
- →General documentation lookups
- →Generic web searches
Prerequisites
Limitations
- →Limited to pre-configured resources
- →Dependent on reference repository quality
How it compares
Analyzes actual source code patterns in established SDKs rather than relying on generic documentation.
Compared to similar skills
reference-sdk side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| reference-sdk (this skill) | 1 | 7mo | Review | Intermediate |
| using-serena-for-exploration | 9 | 8mo | Review | Intermediate |
| cursor-explorer-mcp | 6 | 8mo | No flags | Intermediate |
| react-expert | 8 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
using-serena-for-exploration
seanGSISG
Use when exploring codebases with Serena MCP tools for architectural understanding and pattern discovery - guides efficient symbolic exploration workflow minimizing token usage through targeted symbol reads, overview tools, and progressive narrowing
cursor-explorer-mcp
sepiabrown
Use for token-expensive operations requiring multi-file analysis - codebase exploration, broad searches, architecture understanding, tracing flows, finding implementations across files. Uses MCP cursor-agent server (company pays) with clean async interface. Do NOT use for single-file analysis, explaining code already in immediate context, or pure reasoning tasks.
react-expert
reactjs
Use when researching React APIs or concepts for documentation. Use when you need authoritative usage examples, caveats, warnings, or errors for a React feature.
analyzing-projects
CloudAI-X
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"
leann-search
parcadei
Semantic search across codebase using LEANN vector index
cartographer
kingbootoshi
Maps and documents codebases of any size by orchestrating parallel subagents. Creates docs/CODEBASE_MAP.md with architecture, file purposes, dependencies, and navigation guides. Updates CLAUDE.md with a summary. Use when user says "map this codebase", "cartographer", "/cartographer", "create codebase map", "document the architecture", "understand this codebase", or when onboarding to a new project. Automatically detects if map exists and updates only changed sections.