CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

readme-lint

Linter di conformità per README. Valida che un README rispetti gli standard ecosistema fgt-sdk, i principi anti-AI-slop (wwewtech/anti-slop-design), no-ai-slop (petergyang/no-ai-slop su zread.ai) e diagram-design (cathrynlavery/diagram-design).

Quality

74%

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 ./skill/readme-lint/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.

The body is a tight, actionable rulebook: 35 concrete checkable rules with severities, a complete JSON output contract, and a clear quality gate, with no bundle files to navigate. Its main weaknesses are the unspecified computation for the numeric score and anti_slop_axes ratings and a merely implicit execution sequence.

Suggestions

Define how the numeric 'score' is computed (e.g., start at 100, −10 per Errore, −5 per Avviso) and how rule violations map to each anti_slop_axes rating, so the output contract is fully executable.

Add a brief 3–4 step execution sequence (read README → apply rules by severity → compute score/axes → emit JSON report) to make the workflow explicit rather than implied.

DimensionReasoningScore

Conciseness

The body is dense and rule-focused with almost no concept explanation Claude already knows — each of the 35 rules is a terse table row and the banned-words list is execution data, not padding. The only trimmable redundancy is the 7-axis table partially restating rules 11–20, which keeps it just below the lean 5 anchor.

4 / 5

Actionability

Rules are concretely checkable (e.g., 'Nessun riferimento a `0.0.0.0`', an explicit banned-word list, severity levels, and a fully specified JSON output example), making guidance mostly executable. Minor gaps remain: the numeric 'score' (e.g., 85) and the anti_slop_axes ratings have no stated computation rule, so it falls short of fully copy-paste-ready 5.

4 / 5

Workflow Clarity

As a simple single-pass lint the action is unambiguous in shape (apply the rule tables, emit the JSON report), and the read-only nature avoids the destructive/batch validation cap. However, the execution sequence (read → check by severity → score → report) is only implicit and score computation is unspecified, placing it at 4 rather than 5.

4 / 5

Progressive Disclosure

The single file (~100 lines) is well organized into clearly signaled sections (fgt-sdk rules, three anti-slop rule sets, output, quality gate, triggers) with all content needed at execution time, so inlining is appropriate. It exceeds the under-50-line simple-skill bar and the rule tables could arguably split into reference files, so it sits at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

61%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 clearly identifies a README compliance linter with a distinct niche and decent natural keywords, but it is incomplete: it lacks any 'when to use' trigger clause and omits key capabilities (conformity report with errors, warnings, and suggestions) that only appear in the body. Adding a trigger clause and one more concrete action would lift it substantially.

Suggestions

Add an explicit 'Use when…' trigger clause to the description (e.g., 'Use quando l'utente chiede di verificare, lintare o de-sloppare un README') so both what and when are answered in the description itself.

Mention the concrete output in the description — that it returns a conformity report with errors, warnings, and correction suggestions — to move specificity from one action toward several listed actions.

Include common term variations such as 'README.md', 'documentazione', or 'de-slop' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Linter di conformità per README') and one concrete action ('Valida che un README rispetti gli standard') against four named frameworks, but stops there — it never mentions producing a report, errors, warnings, or fixes. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive', not the level above, which requires several listed specific actions.

3 / 5

Completeness

The 'what' is clear (validates README compliance against named standards) but the description contains no 'Use when…' clause or equivalent trigger guidance — the Trigger section lives only in the body, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

It contains the natural terms a user would say — 'README', 'Linter', 'conformità', 'anti-AI-slop', 'no-ai-slop' — giving good keyword coverage, though a few natural variations ('README.md', 'docs', 'de-slop') are absent, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Linter di conformità per README' tied to specific named frameworks (fgt-sdk, anti-slop-design, no-ai-slop, diagram-design) carves a mostly distinct niche with minor overlap risk against generic markdown/docs linting skills, fitting the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

biodoia/readmago

Path

skill/readme-lint/SKILL.md

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.