CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-architect

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

52

Quality

57%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wiki-architect/SKILL.md

The canonical home for this skill is wiki-architect in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is well-structured and concise with a clear procedure, but it lacks an executable example of the output JSON schema and any validation checkpoints in its workflow. Progressive disclosure is good for a self-contained single-file skill.

Suggestions

Add a concrete JSON example block in the Output section showing the actual catalogue schema (title, name, prompt, children) so the guidance is copy-paste ready.

Insert an explicit validation step in the Procedure (e.g. verify every cited file_path:line_number exists and nesting stays within the 4-level / 8-children limits) with a fix-and-retry loop.

Remove the duplicate trailing 'When to Use' section and the verbatim repetition of the description to tighten the body further.

DimensionReasoningScore

Conciseness

The body is mostly efficient with bullet points and no padding about concepts Claude already knows; only minor trim opportunities exist (the intro line repeats the description verbatim and a duplicated, near-empty 'When to Use' section at the end).

4 / 5

Actionability

It gives concrete procedural guidance (scan, detect, identify layers, generate a catalogue with named fields) and explicit constraints, but the Output section describes the JSON schema in prose without showing an executable example, leaving a key detail missing.

3 / 5

Workflow Clarity

A clear 5-step sequence (Scan -> Detect -> Identify -> Generate -> Cite) is present, but there are no explicit validation checkpoints (e.g. verify cited files exist, confirm nesting limits) and no error-feedback loop.

3 / 5

Progressive Disclosure

No bundle files exist and the single-file skill is well organized with clear section headers; it is slightly over the simple-skill line count with a dense inline Onboarding Guide Architecture section, keeping it just below the top anchor.

4 / 5

Total

14

/

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 clearly conveys what the skill produces but omits any 'when to use it' trigger guidance, which caps completeness and limits trigger-term quality. It is specific enough to be distinct from generic doc skills.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasings such as 'create a wiki', 'document this repo', 'generate docs', or 'onboarding guide'.

List a few more concrete actions (e.g. detect project type, identify architectural layers, generate a hierarchical JSON catalogue) to raise specificity above 2 actions.

Include synonyms/file-extension-style natural terms users would actually say when they need this skill.

DimensionReasoningScore

Specificity

Names the domain ('documentation architect') and two concrete actions ('produces structured wiki catalogues and onboarding guides from codebases'), but does not enumerate several specific actions, fitting the 1-2 concrete-actions anchor rather than the several-actions anchor above.

3 / 5

Completeness

It clearly states 'what' the skill does but contains no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ('wiki', 'documentation', 'onboarding guides', 'codebases'), but it lacks the natural user phrasings (e.g. 'create a wiki', 'document this repo') and synonyms that the higher anchors reward.

3 / 5

Distinctiveness Conflict Risk

The niche of structured wiki catalogues and onboarding guides generated from codebases is mostly distinct, with only minor overlap risk against general documentation skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.