- Home
- Skills
- Sounder25
- Google Antigravity Skills Library
- 11 Llmstxt Doc Parsing
11_llmstxt_doc_parsing_skill
- PowerShell
20
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill sounder25/google-antigravity-skills-library --skill 11_llmstxt_doc_parsing- fetch_docs.ps13.1 KB
- SKILL.md2.3 KB
Overview
This skill rapidly ingests project documentation via the /llms.txt convention to give an agent a fast-track understanding of libraries and APIs. It fetches a curated list of markdown files, consolidates them into a single knowledge artifact, and enables immediate, accurate responses without scraping entire sites. Implemented as a PowerShell utility, it outputs a machine-readable index and an optimized consolidated doc.
How this skill works
The script checks the provided base URL for llms.txt or llms-full.txt and parses the file for project metadata and markdown links. It then fetches the referenced markdown files (up to the configured limit), counts tokens for each file, and writes DOCS_INDEX.json plus CONSOLIDATED_KNOWLEDGE.md. After consolidation, the agent reads the single file for instant familiarity with the library or API.
When to use it
- You need rapid familiarity with a new framework or API without crawling the entire site
- Documentation providers publish an llms.txt manifest to speed LLM consumption
- Preparing a code assistant to answer detailed questions about a library before coding
- Onboarding agents to third-party SDKs during runtime or in CI pipelines
Best practices
- Provide the exact project docs base URL or the direct llms.txt link to avoid redirects
- Set a sensible --max-files to balance coverage vs. fetch time (default 10)
- Use a dedicated output directory (default .docs) to keep artifacts isolated
- Validate that the target site intentionally exposes llms.txt to respect owner intent
- Review DOCS_INDEX.json after fetch to confirm token counts and included files
Example use cases
- Agent prepares to answer API usage questions by ingesting a library’s llms.txt and producing a consolidated cheat sheet
- CI job runs the fetch before integration tests so agents have authoritative API docs available
- Support engineers rapidly build a knowledge snapshot for troubleshooting third-party SDK behavior
- Security review: fetch manifest and scan consolidated content for deprecated or risky API usage
FAQ
Provide the direct link to a curated manifest or a list of markdown files; without an llms.txt the script cannot auto-discover files.
Can I change how many files are fetched?
Yes — use the --max-files parameter to limit the number of referenced files fetched and consolidated.
Does this respect robots or site permissions?
The script performs standard HTTP fetches; ensure you have permission to retrieve and store the documentation before running it.