Agent skill

btca-cli

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.

Stars 891
Forks 67

Install this agent skill to your Project

npx add-skill https://github.com/davis7dotsh/better-context/tree/main/skills/btca-cli

SKILL.md

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.

Expand your agent's capabilities with these related and highly-rated skills.

davis7dotsh/better-context

better-result-adopt

Migrate codebase from try/catch or Promise-based error handling to better-result. Use when adopting Result types, converting thrown exceptions to typed errors, or refactoring existing error handling to railway-oriented programming.

891 67
Explore
petekp/claude-code-setup

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

20 6
Explore
petekp/claude-code-setup

every-style-editor

This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.

20 6
Explore
petekp/claude-code-setup

manage-codex

Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.

20 6
Explore
petekp/claude-code-setup

seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

20 6
Explore
petekp/claude-code-setup

capture-learning

Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.

20 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results