Reference Sdk
- 463 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
reference-sdk is a Claude agent skill that queries official SDK reference implementations with btca ask for developers implementing or debugging provider-specific AI SDK features inside the IDE.
About
reference-sdk is a continuous-claude-v3 skill that gives Claude persistent, version-controlled access to official SDK reference documentation through btca ask without leaving the IDE. Developers invoke it when implementing SDK features, debugging provider-specific issues, or comparing how libraries like Vercel AI SDK or Anthropic SDK solve streaming, tool calling, and similar patterns. Example commands include btca ask -r vercel-ai for streamObject patterns and btca ask -r anthropic for tool-calling behavior. The skill is not user-invocable directly and fires during SDK integration tasks.
- Provides always-up-to-date Claude SDK reference directly to your agent
- Eliminates hallucinated method signatures and outdated parameter lists
- Works across multiple Claude SDK versions and language bindings
- Reduces token usage by replacing long pasted docs with precise lookups
- Seamless integration with Cursor, Claude Code, and Windsurf
Reference Sdk by the numbers
- 463 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,860 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill reference-sdkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 463 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you check official SDK reference implementations in the IDE?
Give Claude persistent, version-controlled access to official SDK reference documentation without leaving the IDE.
Who is it for?
Developers implementing AI SDK features who need authoritative reference answers for Vercel AI SDK, Anthropic SDK, or similar providers without tab-switching.
Skip if: General language documentation lookups unrelated to AI SDK integration or teams without btca installed.
When should I use this skill?
Claude is implementing SDK features, debugging provider-specific behavior, or comparing reference library patterns.
What you get
btca ask answers citing reference SDK patterns for streaming, tool calling, and provider APIs.
- SDK pattern answers
- Provider-specific implementation guidance
By the numbers
- Documents btca ask queries for vercel-ai and anthropic reference repositories
Files
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
1. Before implementing - See how others solved similar problems 2. When debugging - Find how reference code handles edge cases 3. Multi-provider support - Compare implementations across SDKs 4. 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)
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use reference-sdk for authoritative SDK pattern lookups via btca; use web search when btca repositories do not cover the provider.
FAQ
How does reference-sdk look up SDK patterns?
reference-sdk uses btca ask with repository flags like -r vercel-ai or -r anthropic to retrieve how official reference SDKs implement features such as streamObject or tool calling.
When should reference-sdk be invoked?
reference-sdk should be invoked when implementing SDK features, debugging provider-specific issues, or answering questions like how Vercel AI SDK or Anthropic SDK solve streaming and tool-use patterns.