CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

godocai

Documentation creator for Biodoia ecosystem. Explodes any software into nocode snippets — descriptive, verbal, exhaustive text fragments that describe what each part does without writing code. Uses GoFainder for research, Memogo for memory, SpegOplain for spec assembly.

Quality

48%

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/godocai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 core documentation engine sections (What, Pipeline, Commands, Dependencies, Rules) are reasonably structured, but the body is dominated by an unrelated Italian-language anti-pattern register about software quality and crypto-trading conduct, plus a second dated manual that contradicts the first command set. The skill needs its off-topic content removed to separate files or deleted, one unified command interface, and validation steps in the pipeline.

Suggestions

Remove the entire ANTI-PATTERN REGISTER and trading/meme-coin sections from SKILL.md; if that policy must exist, move it to a separate reference file (or a project-level CLAUDE.md) and link it in one line.

Unify the two conflicting command sections into one: either the 'python src/doc_creator.py' invocations or the 'godocai scan/generate' CLI, showing how the CLI is installed/invoked and including the snippet.json schema that commit_snippet.py expects.

Add validation checkpoints to the pipeline, e.g. verifying the snippet catalog after explosion ('check catalog integrity / spot-check N snippets against source') before handing off to SpegOplain, since repo explosion is a batch operation.

DimensionReasoningScore

Conciseness

Roughly 120 of the ~195 body lines are an off-topic 'ANTI-PATTERN REGISTER' in Italian covering generic quality rules, meme-coin sniping, and trading risk, plus a dated 'Manuale d'uso' — heavily padded content with no place in this skill. Time-sensitive dates ('17 novembre 2026', 'v1.0 (2026-11-20)') appear outside any deprecated/old-patterns section, matching the 'severely verbose; heavily padded' anchor rather than the merely 'noticeably verbose' level 2.

1 / 5

Actionability

There are concrete commands ('python src/doc_creator.py /path/to/repo', 'python src/commit_snippet.py snippet.json') but the later manual introduces a second, conflicting interface ('godocai scan -d <repo>', 'godocai generate readme') with no indication of how it is installed or invoked, and the snippet.json format referenced by commit_snippet.py is never shown. This fits 'some concrete guidance but incomplete; missing key details' rather than level 4's 'minor gaps'.

3 / 5

Workflow Clarity

The 6-step Pipeline (Understand → Remember → Research → Explode → Catalog → Pass) is clearly sequenced, but there are no validation or verification checkpoints anywhere, and exploding a whole repo into a snippet catalog is a batch operation — the rubric caps workflow clarity at 3 in that case. It is not a 2 because the sequence itself is coherent and well-ordered.

3 / 5

Progressive Disclosure

There are no bundle files at all, and large blocks of content that clearly belong in separate files — the anti-pattern register, the full command table, the runtime backend status — are inlined into SKILL.md. This matches 'content that clearly belongs in separate files is inlined'; it is not a 3 because beyond the core sections the organization digresses into unrelated material rather than merely needing tidier references.

2 / 5

Total

9

/

20

Passed

Description

42%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 clear core capability (code-free documentation snippets) but relies almost entirely on invented ecosystem jargon instead of natural trigger terms, and provides no 'use when' guidance. It reads as an internal component label rather than a discoverable skill description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when documenting an unfamiliar codebase, generating README/API/architecture docs, or describing what code does without writing code.'

Replace or supplement jargon ('explodes', 'nocode snippets', 'Biodoia ecosystem') with natural phrases users would actually say: 'document a repo', 'generate documentation', 'describe code in plain language'.

Lead with the concrete actions (scan, research, generate docs, catalog snippets) rather than the service names, which mean nothing outside the ecosystem.

DimensionReasoningScore

Specificity

The description names its domain ('Documentation creator for Biodoia ecosystem') and a couple of concrete actions ('Explodes any software into nocode snippets', 'Uses GoFainder for research, Memogo for memory'), matching the '1-2 concrete actions but not comprehensive' anchor. It is not a 4 because the action list is narrow and the idiosyncratic phrasing ('explodes', 'nocode snippets') obscures what is actually done.

3 / 5

Completeness

The 'what' is stated clearly (creates descriptive, code-free documentation snippets from software), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

'Documentation' is the only natural keyword a user would say; the remaining terms ('Biodoia ecosystem', 'nocode snippets', 'GoFainder', 'Memogo', 'SpegOplain') are invented proper-noun jargon users would not spontaneously utter, fitting 'one or two generic keywords; missing the natural phrases users say'. It is not a 3 because common variations like 'docs', 'document a codebase', or 'generate documentation' are absent.

2 / 5

Distinctiveness Conflict Risk

The ecosystem proper nouns (GoFainder, Memogo, Biodoia) give it a niche, but the opening 'Documentation creator' is broad and would overlap with any general documentation skill, matching 'somewhat specific but could still overlap with similar skills'. It is not a 4 because no distinct trigger phrase separates it from generic documentation helpers.

3 / 5

Total

11

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

biodoia/readmago

Path

skill/godocai/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.