Btca Cli
Install this when you need grounded answers from official repo, npm, or local docs instead of guessing library APIs while coding.
Overview
btca-cli is an agent skill most often used in Build (also Idea, Validate) that walks agents through btca CLI setup, resource management, and source-grounded `ask` queries against libraries and frameworks.
Install
npx skills add https://github.com/davis7dotsh/better-context --skill btca-cliWhat is this skill?
- Hydrates git repos, local paths, and npm packages into searchable context for grounded Q&A
- Supports persistent named resources plus one-off anonymous repos in `btca ask`
- Multi-resource questions in a single `btca ask` for cross-library topics (e.g. React + TypeScript)
- Project setup: add resources, `btca resources` verification, then source-first answers
- Official CLI reference at docs.btca.dev for full command surface
Adoption & trust: 689 installs on skills.sh; 1.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are integrating a library but need accurate behavior from real repos and packages, not hallucinated API details from chat.
Who is it for?
Solo builders who want a repeatable CLI ritual for library research inside the same repo they are shipping.
Skip if: Teams that only need a one-line web search with no local resource cache or who are not willing to install and configure the btca CLI.
When should I use this skill?
User says "use btca", needs btca setup, provider connection, resource management, or detailed research on a specific library or framework.
What do I get? / Deliverables
Your agent runs documented btca add, verify, and ask flows so answers are grounded in the resources you configured or one-off URLs you pass in.
- Configured btca resources list
- Source-grounded answers from `btca ask` commands
- Verified resource catalog via `btca resources`
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because btca is wired into day-to-day implementation research, resource hydration, and ask workflows against libraries you are integrating. Integrations fits adding git/npm/local resources and querying them—the same loop as wiring third-party frameworks into your product.
Where it fits
Compare Svelte docs repo versus implementation repo with one-off `btca ask` before picking a framework.
Hydrate @types/node and framework repos to sanity-check typings and APIs before locking the MVP scope.
Keep named resources for React and TypeScript and ask cross-cutting questions while wiring state and types.
Teach the agent to invoke btca when the user needs deeper research on a dependency the skill names explicitly.
How it compares
Use for source-hydrated CLI research instead of ad-hoc "read the docs" chat without indexed project resources.
Common Questions / FAQ
Who is btca-cli for?
Indie and solo developers using coding agents who already use or want to adopt btca for framework-specific, source-first answers during Build and earlier discovery.
When should I use btca-cli?
During Idea or Validate when scoping a stack from real repos; during Build when adding resources and asking integration questions; whenever the user says "use btca" or needs detailed research on a named library.
Is btca-cli safe to install?
The skill describes shell and network operations typical of a research CLI; review the Security Audits panel on this Prism page and your org policy before granting agent shell access.
SKILL.md
READMESKILL.md - Btca Cli
interface: display_name: "BTCA CLI" short_description: "Help with BTCA CLI setup and usage workflows" --- name: btca-cli description: Operate the btca CLI for local resources and source-first answers. Use when setting up btca in a project, connecting a provider, adding or managing resources, and asking questions via btca commands. Invoke this skill when the user says "use btca" or needs to do more detailed research on a specific library or framework. --- # btca CLI `btca` is a source-first research CLI. It hydrates resources (git, local, npm) into searchable context, then answers questions grounded in those sources. Use configured resources for ongoing work, or one-off anonymous resources directly in `btca ask`. Full CLI reference: https://docs.btca.dev/guides/cli-reference Add resources: ```bash # Git resource btca add -n svelte-dev https://github.com/sveltejs/svelte.dev # Local directory btca add -n my-docs -t local /absolute/path/to/docs # npm package btca add npm:@types/node@22.10.1 -n node-types -t npm ``` Verify resources: ```bash btca resources ``` Ask a question: ```bash btca ask -r svelte-dev -q "How do I define remote functions?" ``` ## Common Tasks - Ask with multiple resources: ```bash btca ask -r react -r typescript -q "How do I type useState?" ``` - Ask with anonymous one-off resources (not saved to config): ```bash # One-off git repo btca ask -r https://github.com/sveltejs/svelte -q "Where is the implementation of writable stores?" # One-off npm package btca ask -r npm:react@19.0.0 -q "How is useTransition exported?" ``` ## Config Overview - Config lives in `btca.config.jsonc` (project) and `~/.config/btca/btca.config.jsonc` (global). - Project config overrides global and controls provider/model and resources. ## Troubleshooting - "No resources configured": add resources with `btca add ...` and re-run `btca resources`. - "Provider not connected": run `btca connect` and follow the prompts. - "Unknown resource": use `btca resources` for configured names, or pass a valid HTTPS git URL / `npm:<package>` as an anonymous one-off in `btca ask`.