Operate the btca source-first research CLI to add resources and ask grounded questions.
- What it does
- This skill explains how to use the btca command-line tool, a source-first research CLI that hydrates git, local, and npm resources into searchable context and answers questions grounded in those sources. It covers adding resources, verifying them, asking questions with one or more resources, using anonymous one-off resources, config file locations, and troubleshooting common errors. It produces command guidance and configuration knowledge rather than files.
- When to use it
- Use it when setting up btca in a project, connecting a provider, adding or managing resources, or asking questions through btca commands. It is also meant for users who say "use btca" or need more detailed research on a specific library or framework.
- Requirements
- Requires the btca CLI to be installed and a connected provider; network access is needed for git and npm resources. No scripts ship with the skill; it is instructions only.
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:
Verify resources:
Ask a question:
Common Tasks
- Ask with multiple resources:
- Ask with anonymous one-off resources (not saved to config):
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.