CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-llms-txt

Generates llms.txt and llms-full.txt files for LLM-friendly project documentation following the llms.txt specification. Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/deep-wiki/skills/wiki-llms-txt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction skill with concrete commands, format templates, and a validation checklist. Main gaps are the absence of an explicit retry feedback loop and some redundancy between the two format sections.

Suggestions

Add an explicit validate→fix→retry loop after the Validation Checklist (e.g., "If a check fails, fix the offending entry and re-run the checklist before finalizing") to lift workflow clarity.

Consolidate the llms.txt and llms-full.txt format blocks since llms-full.txt shares the same structure — state the shared skeleton once and only show the diff (inlined <doc> blocks).

Optionally move the detailed format templates and Description Quality table into a reference file (e.g., references/format.md) and link to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no preamble on what llms.txt is), with concrete tables and templates; minor redundancy between the llms.txt and llms-full.txt format blocks could be trimmed.

4 / 5

Actionability

Provides concrete git commands, explicit file-format templates, named output paths, and a checkable validation list; guidance is executable with only minor gaps (no sample populated output).

4 / 5

Workflow Clarity

Clear sequence with a gated "MUST DO FIRST" resolution step ("Do NOT proceed until resolved") and a final validation checklist, but it lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clear headed sections with no nested references and a self-contained single file; the detailed format specs are inlined rather than split into reference files, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states both capability and activation triggers tied to the llms.txt standard. It is distinct and complete, with only minor room to broaden action specificity and trigger synonyms.

DimensionReasoningScore

Specificity

"Generates llms.txt and llms-full.txt files" names the domain and two concrete output actions, but coverage is limited to generating those two file types rather than a comprehensive action list.

3 / 5

Completeness

Explicitly answers both what ("Generates llms.txt and llms-full.txt files...") and when ("Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ("llms.txt files", "LLM-readable summaries", "make their wiki accessible to language models") with good synonym coverage, though a few common phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (the llms.txt specification) with distinct triggers, but "make their wiki accessible to language models" has minor overlap with general wiki-generation skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
freightCognition/linehaulai-claude-marketplace
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.