Name: docs
Rating: 64.8 (1 reviews)
Author: TanStack

docs

Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning or implementing a new feature or change in a repo (docs ship with the code). Also use when tempted to write docs without showing the discovered readers to the user, without asking for tone, or without loading simple-english and i-have-adhd. Triggers on "write docs for X", "document this feature", "add a guide", "update the docs", "reorganize the docs", "plan feature X", "implement X", or /docs.

Quality

81%

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

The canonical home for this skill is docs in TanStack/ai

Quality

Content

77%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 highly actionable and has an exceptionally clear gated workflow with real validation feedback loops. Its weaknesses are redundancy (duplicated gate scaffolding and a red-flags table that repeats body rules) and monolithic structure that ignores progressive disclosure for a file of this size.

Suggestions

Split reference material out of SKILL.md into bundle files (e.g., references/package-manager-tabs.md for the tabs spec and rules, references/red-flags.md for the table), keeping the core two-phase workflow and gates in the body.

Factor the shared HARD-GATE scaffolding (AskQuestion fallback, default-stop path, skip conditions) into one stated pattern referenced by both gates, or trim the red-flags table to only rows not already covered verbatim earlier in the body.

Dimension	Reasoning	Score
Conciseness	The body mostly earns its tokens (concrete Bad/Good pairs, exact commands), but the persona and tone gates repeat near-identical scaffolding (AskQuestion handling, stop/skip paths), and the 25-row red-flags table restates rules already stated verbatim in earlier sections. It is above anchor 2 (not padded throughout) but below anchor 4 (several sections are pure repetition that could be tightened).	3 / 5
Actionability	Fully executable guidance throughout: exact doc-folder probe list ('docs/', 'documentation/', 'content/docs/', 'site/'), exact tab markup ('::start:tabs variant="package-manager" mode="install"') with per-mode command shapes, exact skill file paths to load, prescribed gate message contents, and a concrete user-story format. Instruction-only skill with no meaningful actionability gaps.	5 / 5
Workflow Clarity	Clear two-phase sequence with an explicit flow diagram, two hard gates with stop/skip paths and enumerated non-skips, a stop condition when prerequisite files are missing, and end-of-page validation with a feedback loop ('search your own added text for the forbidden glyphs; if a hit survived, fix it', then run the simple-english self-check).	5 / 5
Progressive Disclosure	The file is well-sectioned and navigable, but it is a single 425-line monolith with no bundle files: the package-manager tabs spec, the forbidden-glyph rules, and the red-flags table are inline content that clearly belongs in reference files. The under-50-line exception does not apply, so this sits at anchor 3 rather than 5.	3 / 5
	Total	16 / 20 Passed

Description

75%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 has excellent explicit triggers and concrete actions, with both what and when covered. Its main weakness is deliberate over-breadth: claiming every feature plan and implementation as a trigger creates high conflict risk with the rest of the skill library.

Suggestions

Narrow the broad trigger 'whenever planning or implementing a new feature or change in a repo' to contexts where docs are actually at stake (e.g., features with user-facing or public behavior changes), and drop the standalone 'implement X' trigger to reduce conflict with general coding skills.

Open with a one-line third-person capability statement (e.g., 'Writes and organizes repo documentation built around named readers, gated on persona and tone choices') before the 'Use when' clauses, so the 'what' is stated directly instead of implied by triggers.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writing, editing, or organizing documentation', 'planning what docs a feature needs', 'showing the discovered readers to the user', 'asking for tone', 'loading simple-english and i-have-adhd') with only minor coverage gaps. It falls short of a 5 because the actions are framed as trigger conditions rather than a complete capability statement.	4 / 5
Completeness	Both 'what' and 'when' are present and the 'when' is highly explicit with concrete triggers, but the 'what' is woven into 'Use when...' phrasing rather than stated as a direct capability sentence, so it does not fully match the 5 anchor.	4 / 5
Trigger Term Quality	Comprehensive natural trigger phrases with variations: 'write docs for X', 'document this feature', 'add a guide', 'update the docs', 'reorganize the docs', 'plan feature X', and the /docs slash-command form. These are phrasings a user would naturally say, matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	The clauses 'whenever planning or implementing a new feature or change in a repo' and the trigger 'implement X' fire on virtually any coding session, creating high overlap risk with many unrelated skills. It is not a 1 because the documentation-specific triggers ('write docs for X', 'update the docs') are clearly distinct.	2 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: TanStack/ai
Path: .grok/skills/docs/SKILL.md
Commit: 7fb4a5f

Reviewed: 2 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.