CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

playground-project-architecture

Create an interactive HTML architecture explorer playground for the current project

Quality

70%

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 ./playground-project-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 delivers highly actionable, executable guidance with a clear phased workflow, but it is held back by redundant repeated mandates and a monolithic structure that inlines ~200 lines of schema reference that belongs in separate reference files. Adding an explicit validation step before opening the output would complete the workflow.

Suggestions

Consolidate the message-ID and componentData-completeness mandates into a single 'Critical Rules' section and drop the duplicated IMPORTANT comments/paragraphs elsewhere in the body.

Move the detailed Sequence Flow Configuration and Workflow V2 schema sections into a reference file (e.g., references/diagram-config.md), keeping SKILL.md as a lean overview with one-level-deep, clearly signaled references.

Add an explicit validation step in Phase 3 (e.g., check that every componentId, participant id, and message id has a matching componentData entry) before the final 'open in browser' step.

DimensionReasoningScore

Conciseness

The body is dense, skill-specific schema documentation rather than explanation of known concepts, but it duplicates instructions: the sequence-message-ID mandate appears three times ("// IMPORTANT: Subsequent flows also need IDs on ALL messages!", the **IMPORTANT** paragraph under Messages, and Critical Rule 8) and the componentData-completeness rule is repeated in the CONFIG comment and Critical Rule 7; the ~130-line inline CONFIG example could also be tightened. Not 2 because most content is non-redundant, concrete guidance; not 4 because the repeated mandates are clearly trimmable padding.

3 / 5

Actionability

Guidance is copy-paste ready: a complete CONFIG object example covering every diagram type, exact bash commands ("mkdir -p docs/playground", the cp of the template with its full path), a precise file-naming convention with the YYYYMMDD-HHMM timestamp format, and the exact HTML edit (script tag before the main <script> tag). Not 4 because no notable gaps remain in the common-case path.

5 / 5

Workflow Clarity

Phases 1-3 are clearly sequenced (codebase analysis -> build CONFIG -> generate output) with numbered generation steps and 'double-check' instructions for sequence flow IDs. Not 5 because there is no explicit validation checkpoint (e.g., verifying every componentId/id resolves to a componentData entry before opening the file); not 3 because the sequence and ordering are unambiguous and partial verification cues exist.

4 / 5

Progressive Disclosure

Sections are clearly headed, but the SKILL.md is monolithic: roughly 200 lines of detailed config-schema reference (Sequence Flow Configuration, Workflow V2, badge and node-type tables) are inlined rather than split into reference files, and the referenced template (templates/architecture-explorer.html) is not present in the bundle's file listing. Not 2 because structure and navigation within the file are good; not 4 because content that clearly belongs in separate reference files is inlined and the sole referenced path is unverifiable.

3 / 5

Total

15

/

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 gives a clear, concrete statement of what the skill produces, but omits any 'when to use' trigger guidance, which caps its completeness. Trigger terms are relevant but lack natural synonyms users would actually say.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g., 'Use when the user wants to visualize or explore a codebase's architecture, generate architecture diagrams, or onboard to an unfamiliar project.'

Enumerate the key capabilities in the description (component tree, workflow/data-flow/sequence diagrams, annotations) to lift specificity.

Add natural synonyms such as 'codebase', 'visualize architecture', and 'project structure' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"Create an interactive HTML architecture explorer playground for the current project" names the domain clearly and one concrete action (creating the playground), but does not list the several specific capabilities it provides (component tree, workflow/data-flow diagrams, annotations). Not 4 because no multiple concrete actions are enumerated; not 2 because the action named is specific and grounded, not generic.

3 / 5

Completeness

The description clearly answers 'what' (creates an interactive HTML architecture explorer playground) but has no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing 'when' caps completeness at 3. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords exist ("architecture", "explorer", "playground", "HTML", "current project"), but common natural variations users would say are missing ("codebase", "visualize", "diagram", "explore project structure", "onboarding"). Not 4 because keyword coverage is thin with several natural terms absent.

3 / 5

Distinctiveness Conflict Risk

"Architecture explorer playground" is a fairly distinct niche unlikely to collide with unrelated skills, with only minor overlap risk against general visualization or documentation-generation skills. Not 5 because terms like "architecture" and "playground" could still overlap with other diagramming or interactive-artifact skills.

4 / 5

Total

13

/

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

fernandezbaptiste/claude-playground-explorer

Path

playground-project-architecture/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.