SkillHub ClubShip Full StackFull Stack

reference-sdk

Check reference SDK implementations using btca ask

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

3,613

Hot score

Updated

March 20, 2026

Overall rating

C5.0

Composite score

5.0

Best-practice grade

B84.0

Install command

npx @skill-hub/cli install parcadei-continuous-claude-v3-reference-sdk

Repository

parcadei/Continuous-Claude-v3

Skill path: .claude/skills/reference-sdk

Check reference SDK implementations using btca ask

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: parcadei.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install reference-sdk into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/parcadei/Continuous-Claude-v3 before adding reference-sdk to shared team environments
Use reference-sdk for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw 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:

```bash
# 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)