smithery/parcadei

reference-sdk

Check reference SDK implementations using btca ask

Installation

$ npx skills add smithery/parcadei --skill reference-sdk

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/parcadei · top by installs.

npx skills add smithery/parcadei

Browse all from smithery/parcadei

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,501 B
  • docs SUMMARY.md 71 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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)