Skill This
AI Skill Report Card

Converting Docs to Skills

B+78·Sep 23, 2026·Source: Extension-page
Quick Start14 / 15

Convert a docs site's llms.txt into a skill and install it immediately:

Bash
npx txtskills@latest convert https://docs.example.com/llms.txt --install
Recommendation▾
Add a troubleshooting example showing actual command output/error and how to resolve it, not just described pitfalls
Workflow14 / 15

Progress:

  • Identify the docs source (direct llms.txt URL or base domain)
  • Run convert with appropriate flags
  • Verify conversion succeeded (check output or --json result)
  • Install the skill (via --install or add)
  • Confirm skill is available; use list/search to double-check

Step 1: Convert

Use a direct llms.txt URL when available:

Bash
npx txtskills@latest convert https://docs.example.com/llms.txt

Or pass just the base domain — txtskills will locate llms.txt itself:

Bash
npx txtskills@latest convert docs.example.com

Set a custom skill name if the auto-derived name is unclear:

Bash
npx txtskills@latest convert docs.example.com --name example-docs

Step 2: Install

Auto-install right after conversion:

Bash
npx txtskills@latest convert docs.example.com --install

Or skip the install prompt and do it manually later:

Bash
npx txtskills@latest convert docs.example.com --skip-install
npx txtskills@latest add example-docs

Step 3: Discover existing skills (optional, before converting)

Check if a skill already exists so you don't duplicate work:

Bash
npx txtskills@latest search example
npx txtskills@latest list

Step 4: Manage

Remove a skill no longer needed:

Bash
npx txtskills@latest remove example-docs
Recommendation▾
Include a flags reference table (all convert/add/remove/list/search flags) for completeness since CLI options are scattered throughout prose
Examples16 / 20

Example 1: Input: "Turn the Stripe docs into a Claude skill and install it" Output:

Bash
npx txtskills@latest convert https://docs.stripe.com/llms.txt --install

Example 2: Input: "Check if a skill for docs.foo.com already exists before converting" Output:

Bash
npx txtskills@latest search foo
# if not found:
npx txtskills@latest convert docs.foo.com --name foo-docs --install

Example 3: Input: "The foo-docs skill changed upstream, regenerate it" Output:

Bash
npx txtskills@latest convert docs.foo.com --name foo-docs --force --install

Example 4: Input: "Get machine-readable output from a conversion for a script" Output:

Bash
npx txtskills@latest convert docs.example.com --json
Recommendation▾
Show a 'bad outcome' example (e.g., forgetting --install, or naming collision) with the resulting error message to ground the pitfalls section in concrete evidence
Best Practices
  • Prefer passing the direct llms.txt URL when known — it's faster and unambiguous.
  • Use --name explicitly when the base domain could produce an awkward/ambiguous auto-generated name.
  • Run search/list before converting to avoid creating duplicate skills.
  • Use --force only when the source docs have changed; otherwise the existing skill is reused.
  • Use --json when the CLI output needs to be parsed programmatically (e.g., in CI or another script).
  • Use --skip-install when converting many skills in bulk, then batch-install afterward with add.
Common Pitfalls
  • Don't assume a base domain always resolves — if conversion fails, try the direct .../llms.txt URL instead.
  • Don't forget --install or a follow-up add — a converted skill isn't usable until installed.
  • Don't re-run convert without --force expecting changes to take effect if the skill already exists unchanged.
  • Don't hardcode the default API endpoint in scripts if a custom one is required — use --api https://txtskills.hari.works (or the relevant endpoint) explicitly.
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
14/15
Examples
16/20
Completeness
14/20
Format
15/15
Conciseness
13/15
Save to My Skills