Improve a documentation site's visibility in AI training data and AI-powered search. Use when someone wants to submit their site to llms.txt directories (llmstxthub.com, llmstxtdirectory.org, GitHub thedaviddias/llms-txt-hub), build backlinks from AI-indexed developer sources, get listed in G2/Capterra/developer directories, improve AI discoverability, or create a prioritized strategy for appearing in AI search results and citation recommendations.
92
92%
Does it follow best practices?
Impact
88%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
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, actionable capabilities with named platforms, includes a comprehensive 'Use when...' clause with multiple natural trigger scenarios, and occupies a clearly distinct niche around AI discoverability and llms.txt directories. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'submit their site to llms.txt directories', 'build backlinks from AI-indexed developer sources', 'get listed in G2/Capterra/developer directories', 'create a prioritized strategy'. Names specific platforms (llmstxthub.com, llmstxtdirectory.org, GitHub thedaviddias/llms-txt-hub). | 3 / 3 |
Completeness | Clearly answers both what (improve documentation site visibility in AI training/search) AND when with explicit 'Use when...' clause covering multiple trigger scenarios including directory submissions, backlink building, and strategy creation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'llms.txt', 'AI training data', 'AI-powered search', 'backlinks', 'G2/Capterra', 'developer directories', 'AI discoverability', 'AI search results', 'citation recommendations'. Includes specific directory names users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on AI/LLM discoverability and llms.txt ecosystem. The specific directory names and AI-focused SEO context make it unlikely to conflict with general SEO or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. It provides concrete search queries, specific URLs, and ready-to-use output templates. Minor verbosity in explanatory sections and the closing note could be trimmed, but overall the skill effectively guides Claude through a multi-step research and planning process.
Suggestions
Remove the closing 'Note' paragraph as it restates what's already clear from the skill structure and wastes tokens
Tighten the 'When to Use This Skill' section - the parenthetical item numbers are sufficient without the descriptive text
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what directories are, the 'Note' at the end restating Claude's role). The markdown templates are useful but could be slightly tighter. | 2 / 3 |
Actionability | Provides highly concrete, actionable guidance with specific URLs, exact search queries to run, detailed checklists with specific fields needed, and copy-paste ready markdown templates for outputs. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit prerequisites check (verify llms.txt exists before proceeding), numbered steps for each directory, and a logical progression from research to planning to tracking. The 'If llms.txt is missing, stop' is a good validation checkpoint. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections for each item (#25, #26), references external file (references/directories.md) for detailed directory info, and uses tiered organization (Tier 1/2/3) to organize complexity. Navigation is straightforward. | 3 / 3 |
Total | 11 / 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.
658c481
Table of Contents
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.