reference-sdk

Check reference SDK implementations using btca ask

422 stars

Best use case

reference-sdk is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Check reference SDK implementations using btca ask

Teams using reference-sdk should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/reference-sdk/SKILL.md --create-dirs "https://raw.githubusercontent.com/vibeeval/vibecosystem/main/skills/reference-sdk/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/reference-sdk/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How reference-sdk Compares

Feature / Agentreference-sdkStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Check reference SDK implementations using btca ask

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

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

Related Skills

cli-reference

422
from vibeeval/vibecosystem

Claude Code CLI commands, flags, headless mode, and automation patterns

workflow-router

422
from vibeeval/vibecosystem

Goal-based workflow orchestration - routes tasks to specialist agents based on user goals

wiring

422
from vibeeval/vibecosystem

Wiring Verification

websocket-patterns

422
from vibeeval/vibecosystem

Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.

visual-verdict

422
from vibeeval/vibecosystem

Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.

verification-loop

422
from vibeeval/vibecosystem

Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.

vector-db-patterns

422
from vibeeval/vibecosystem

Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.

variant-analysis

422
from vibeeval/vibecosystem

Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.

validate-agent

422
from vibeeval/vibecosystem

Validation agent that validates plan tech choices against current best practices

tracing-patterns

422
from vibeeval/vibecosystem

OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries

tour

422
from vibeeval/vibecosystem

Friendly onboarding tour of Claude Code capabilities for users asking what it can do.

tldr-stats

422
from vibeeval/vibecosystem

Show full session token usage, costs, TLDR savings, and hook activity