Name: update-llms-text
Rating: 56.8 (1 reviews)
Author: flutter

update-llms-text

Update and maintain the llms.txt file. Use when the user wants to add sections, add links, correct information, or review the llms.txt file.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/update-llms-text/SKILL.md

Quality

Content

65%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.

The skill body is well-structured and concise, with a clear overview, action-based sections, and explicit formatting rules. Its weak points are actionability (some steps are abstract rather than executable) and workflow clarity (write operations lack validation/verification checkpoints).

Suggestions

Add explicit verification steps after each write action, e.g. after adding links: re-read the section to confirm the entry rendered correctly and the URL resolves.

Make the link-loading step concrete by specifying the tool or command to read a source file and extract its title, rather than the abstract "Load and analyze its source file".

Add a final consistency check (duplicate-detection and broken-link check) to the add/correct actions, not just to the dedicated review action, since edits can introduce the same problems.

Dimension	Reasoning	Score
Conciseness	The body is lean at ~55 lines, avoids explaining concepts Claude already knows, and keeps each action's steps tight; the only minor padding is the opening sentence restating what the file is ("a curated resource list that helps LLMs understand the Flutter framework"), which could be trimmed.	4 / 5
Actionability	It gives concrete structure (the exact link Markdown format and a code block example), but the per-link step "Load and analyze its source file to identify its title and determine an appropriate description" is high-level guidance rather than an executable, copy-paste-ready procedure, and no tool/code is specified for loading or validating links.	3 / 5
Workflow Clarity	Each action has a numbered sequence, but there are no validation checkpoints: adding/editing links and correcting information are write operations on a shared file with no verify-after-edit step (e.g., re-read the file, check the link resolves, confirm formatting), which caps clarity per the destructive/batch-operation rule.	3 / 5
Progressive Disclosure	For a sub-50-line, single-file skill with no external references, the content is well organized into a clear overview plus per-action sections and a formatting-rules summary; no bundle files exist to reference, so this structure is appropriately complete.	5 / 5
	Total	15 / 20 Passed

Description

67%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.

The description is concise, third-person, and clearly scoped to a specific file with an explicit "Use when" trigger clause. Its main weakness is trigger-term diversity — it relies on a single keyword (llms.txt) without synonyms that users might naturally say.

Suggestions

Broaden trigger terms to include synonyms users might say, e.g. "llms.txt, LLM context file, resource list, or .txt context file for LLMs".

Differentiate the "when" clause from the "what" clause by adding situational triggers (e.g., "Use when onboarding LLMs to the Flutter docs"), not just restating the actions.

Consider noting the file extension or location cue in the trigger phrase to reduce overlap with generic document-editing skills.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "add sections, add links, correct information, or review the llms.txt file" — giving good coverage of the skill's capabilities, with only minor gaps (e.g., it does not mention removing or reorganizing links).	4 / 5
Completeness	It states both the "what" ("Update and maintain the llms.txt file") and an explicit "when" ("Use when the user wants to add sections, add links, correct information, or review the llms.txt file"), but the "when" clause largely restates the "what" rather than adding distinct trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural phrase "llms.txt file" repeated in the trigger clause, but misses common synonyms and variants users might say (e.g., "llms text", "LLM context file", "resource list"), so keyword coverage is only partial.	3 / 5
Distinctiveness Conflict Risk	The narrow focus on a specific named file (llms.txt) gives it a clear niche with minimal conflict risk, though the generic verbs (add/correct/review) could lightly overlap with general doc-editing skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: flutter/website
Path: .agents/skills/update-llms-text/SKILL.md
Commit: 0438a63

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.