Skip to content
Development
Skill

/reference-sdk

Check reference SDK implementations using btca ask

From plugin
continuous-claude-v3
3.9k156 skills32 agents
Install
$ npx -y skills add parcadei/Continuous-Claude-v3 --skill reference-sdk --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/reference-sdk

Context preview

The summary Claude sees to decide when to auto-load this skill.

Check reference SDK implementations using btca ask

SKILL.md

reference-sdk.SKILL.md
name: reference-sdk
description: Check reference SDK implementations using btca ask
user-invocable: false

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

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)
Read more
Ships withcontinuous-claude-v3

A persistent, learning, multi-agent development environment built on Claude Code Continuous Claude transforms Claude Code into a continuously learning system that maintains context across sessions, orchestrates specialized agents, and eliminates wasting

Get the whole plugin

Other skills on continuous-claude-v3.