CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

readme-gen

Generatore di README spettacolari da sorgente + contesto del repository. Include principi anti-AI-slop (wwewtech/anti-slop-design), no-ai-slop (petergyang/no-ai-slop su zread.ai) e diagrammi self-contained HTML+SVG (cathrynlavery/diagram-design). Coerente con gli standard ecosistema fgt-sdk.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skill/readme-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 well-organized and rich in concrete rules, but it reads as a template plus rule catalog rather than an operational skill: no sequenced workflow connects repo source to finished README, key tooling references (nocodaigo, godocai scan) are unexplained, and long rule catalogs that belong in reference files are inlined. It scores slightly below the rubric midpoint overall.

Suggestions

Add an explicit numbered workflow (inspect repo source → collect the input table fields → draft sections per template → apply anti-slop rules → verify facts/links) with a validation checkpoint before finalizing.

Move the 12 anti-pattern catalog, banned-words list, and formatting rules into a references/ file (e.g. references/anti-slop.md), keeping only a summary in SKILL.md.

Explain or operationalize the repo-analysis step: how placeholders like <descrizione architettura> get filled and what "nocodaigo + godocai scan" invocations look like, and strip project-specific noise (hardcoded dates, personal links) from the template.

DimensionReasoningScore

Conciseness

The rule catalogs are dense and skill-specific (not concepts Claude already knows), but the ~60-line README template embeds unnecessary project-specific noise ("https://github.com/bidoia", "aigoproxy · goleciave · PebbleDB", "Go 1.27.1", repeated "2026-11-20" dates) that could be trimmed, and the time-sensitive dates penalize conciseness per the rubric guidelines. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4's minor trims.

3 / 5

Actionability

The input table, full output template, and rules with concrete values (#09090b, 127.0.0.1, specific banned words) provide real guidance, but the core transformation — how to derive the README content from the repo source — is never operationalized: placeholders like "<descrizione architettura>" and tools like "nocodaigo + godocai scan" are mentioned with no instruction on filling or running them. This matches 'Some concrete guidance but incomplete' rather than 4's 'minor gaps'.

3 / 5

Workflow Clarity

There is no sequenced process at all: the implied flow (analyze repo → gather inputs → apply template → apply rules → verify) must be inferred from section order, steps are poorly defined, and validation is absent as a process step ("Verifica" appears only as text inside the output template). This fits 'Rough sequence present but many gaps; validation absent' rather than 3, which requires steps actually listed.

2 / 5

Progressive Disclosure

Sections are clearly headed and the skill is self-contained with no bundle files, but at ~147 lines the 12-item anti-pattern catalog, banned-words list, formatting rules, and full README template are exactly the content that belongs in one-level-deep reference files. This matches 'Some structure but could be better organized; content that should be separate is inline' rather than 4, since the split would be substantial, not a minor gap.

3 / 5

Total

11

/

20

Passed

Description

53%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 communicates a concrete purpose (README generation from repo source) and is distinct from generic doc skills, but it completely lacks a 'when to use' trigger clause and natural keyword variations, and "spettacolari" is fluffy. It sits at or slightly above the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to generate, improve, or de-slop a README, or to align documentation with fgt-sdk standards."

Enumerate the concrete actions the skill performs (generate from scratch, rewrite existing README, create product landing page, remove AI-slop) instead of the single generic action.

Add natural synonyms users would say ("documentazione", "docs page", "landing page") and drop the fluffy "spettacolari".

DimensionReasoningScore

Specificity

"Generatore di README spettacolari da sorgente + contesto del repository" names the domain and one concrete action, but does not list the several specific actions the body actually covers (generating from scratch, improving an existing README, de-slopping AI output). It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is clearly stated (generate READMEs from source and repo context), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guideline. It is not 2 because the 'what' is concrete, and not 4 because 'when' is entirely absent rather than just implicit.

3 / 5

Trigger Term Quality

"README" is the one strong natural keyword a user would say, with "repository" as secondary support, but common variations are missing ("documentazione", "docs", "landing page", "migliorare README", "de-slop"). This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

README generation with named design frameworks (anti-slop-design, no-ai-slop, diagram-design) is a fairly distinct niche with minor overlap risk against generic documentation skills. It is not 5 because the word "spettacolari" and the absence of explicit triggers leave it slightly less crisp than the 'clear niche with distinct triggers' anchor.

4 / 5

Total

13

/

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: 2 possibly missing (AGENTS.md, QWEN.md)

Warning

Total

15

/

16

Passed

Repository

biodoia/readmago

Path

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