Teaches how to discover, validate, and add llms.txt documentation sources to the blz CLI. Use when adding documentation to blz, finding llms.txt or llms-full.txt files, validating sources, refreshing content, or managing the documentation index. Covers source discovery, dry-run validation, and index file handling.
Manages llms.txt documentation sources for the blz CLI with discovery, validation, and index handling.
/plugin marketplace add outfitter-dev/blz/plugin install outfitter-dev-blz@outfitter-dev/blzThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Add and manage llms.txt documentation sources for local search.
| Type | Description | Action |
|---|---|---|
llms-full.txt | Complete documentation (preferred) | Add directly |
llms.txt (full) | Complete docs under standard name | Add directly |
llms.txt (index) | Links to other docs (< 100 lines) | Expand linked files |
# 1. Dry-run to validate
blz add react https://react.dev/llms.txt --dry-run --quiet
# 2. Check output
# Good: contentType: "full", lineCount > 1000
# Index: contentType: "index", lineCount < 100 → find linked docs
# 3. Add if good
blz add react https://react.dev/llms.txt -y
# 4. Verify
blz list --json | jq '.[] | select(.alias=="react")'
Web search patterns:
"llms-full.txt" site:docs.example.com
"llms.txt" OR "llms-full.txt" <library-name>
site:github.com/org/repo "llms.txt"
Common URL patterns:
https://docs.example.com/llms-full.txt
https://example.com/llms.txt
https://example.com/llms-full.txt
If dry-run shows contentType: "index" with < 100 lines:
# Inspect the index
curl -s <index-url> | head -50
# Look for .txt references like:
# ./guides.txt
# ./js.txt
# ./python.txt
# Resolve and add each linked file
blz add supabase-guides https://supabase.com/llms/guides.txt -y
blz add supabase-js https://supabase.com/llms/js.txt -y
| Criteria | Good | Index | Skip |
|---|---|---|---|
| contentType | "full" | "index" | "unknown" |
| lineCount | > 1000 | < 100 | < 50 |
| Action | Add | Expand | Investigate |
Good aliases:
bun, react, deno (short, clear)supabase-guides (variant-specific)langchain-python (language-specific)Bad aliases:
b (too short)my-docs (vague)the-react-docs-2024 (too long)# List sources
blz list --json
blz list --status --json # With freshness
# Refresh sources
blz refresh --all --json # Update all
blz refresh bun --json # Update specific
# Remove source
blz remove bun
# Source details
blz info bun --json
| Issue | Solution |
|---|---|
| 404 Not Found | Try /llms.txt vs /llms-full.txt, check GitHub repo |
| Small line count | Likely index file - expand linked docs |
| contentType unknown | Inspect content manually, verify it's markdown/text |
| Already exists | Use blz refresh <alias> to update |
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.