llms-txt-creator
Create or fix llms.txt and llms-full.txt files for a documentation project, following the llmstxt.org specification. Use this skill whenever someone needs to create an llms.txt file, generate a full documentation text dump (llms-full.txt), or fix a malformed llms.txt. Also use when optimizing a docs site for AI crawlers, when setting up AI discoverability files, or when the user mentions making their docs readable by LLMs, ChatGPT, Perplexity, or other AI systems.
100
100%
Does it follow best practices?
Impact
100%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes a comprehensive 'Use this skill whenever...' clause with natural trigger terms spanning technical (llms.txt) to conversational (making docs readable by ChatGPT), and occupies a clear, distinctive niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create or fix llms.txt and llms-full.txt files', 'generate a full documentation text dump', 'fix a malformed llms.txt'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what (create/fix llms.txt files following llmstxt.org spec) AND when (explicit 'Use this skill whenever...' clause with multiple trigger scenarios including AI optimization and specific AI system mentions). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'llms.txt', 'llms-full.txt', 'AI crawlers', 'AI discoverability', 'docs readable by LLMs', 'ChatGPT', 'Perplexity', 'AI systems', 'documentation project'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on llmstxt.org specification and AI discoverability files. The specific file names (llms.txt, llms-full.txt) and purpose (AI crawler optimization) make it unlikely to conflict with general documentation or file handling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It provides concrete, executable guidance with clear workflows, appropriate validation steps, and efficient use of tokens. The structure balances quick-reference needs with detailed implementation guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what llms.txt is or why it matters. | 3 / 3 |
Actionability | Provides fully executable code for the build script, specific format templates, exact file placement paths per framework, and concrete validation checklists. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints in Steps 2 and 4. Includes specific verification criteria (spot-check links, file size checks) and a checklist format for validation. | 3 / 3 |
Progressive Disclosure | Clean overview structure with a single reference to the full spec file. Content is appropriately split between the skill (workflow) and the reference file (spec details). Navigation is clear with numbered steps and logical sections. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- kubical-ai/aeo-geo-optimization
- Commit
658c481
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.