CtrlK
BlogDocsLog inGet started
Tessl Logo

docs-build-and-verify

Use when asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concise, highly actionable skill with concrete commands and a sensible build-then-verify sequence. Main gaps are the missing fix-retry feedback loop and an inlined script that would benefit from externalization.

Suggestions

Add an explicit feedback loop after the broken-image and reST checks (e.g., 'if broken images are found, fix the source reference and re-run yarn build').

Move the inline Python broken-image checker into scripts/check_broken_images.py and reference it, keeping the SKILL.md body under the simple-skill threshold.

Clarify the ordering/dependency between the three verification checks (e.g., note that reST cross-reference resolution requires a successful build first).

DimensionReasoningScore

Conciseness

Mostly lean with purposeful command disambiguations ("Full production build", "Dev server with hot reload", "Regenerate API data and sidebars only"), but the inline ~25-line Python script and a few prose intros could be trimmed or externalized.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (nvm use 20, yarn build/start/crocodocs:generate, the complete Python broken-image script, and the grep one-liner) covering the common cases.

5 / 5

Workflow Clarity

Clear build-then-check sequence with an explicit validation checkpoint ("The build fails if any are found"), but lacks an explicit fix-and-retry feedback loop for the image and reST cross-reference checks.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but the body exceeds the simple-skill threshold and inlines a sizable Python script that could live in a scripts/ file.

4 / 5

Total

17

/

20

Passed

Description

92%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-scoped description that clearly pairs concrete capabilities with an explicit use-when trigger. Only minor weakness is a lack of synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "build, preview, or verify the Flet documentation website" plus three specific checks ("broken links, broken images, and unresolved reST cross-references"), giving comprehensive coverage of the docs build/verify domain.

5 / 5

Completeness

Explicitly states both what (build/preview/verify the Flet docs site and run the three checks) and when ("Use when asked to build, preview, or verify...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("build", "preview", "verify", "documentation website", "broken links", "broken images"), but misses common synonyms/variants like "docs", "dead links", or "404s".

4 / 5

Distinctiveness Conflict Risk

Scoped to "Flet documentation website" with distinct verification triggers, creating a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flet-dev/flet
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.