CtrlK
BlogDocsLog inGet started
Tessl Logo

visualize-repo

Open or create a repo-native visual documentation workspace backed by local Plan MDX files. Use when the user asks to visualize a repository, create durable visual docs for APIs/components/models/flows, launch a visual repo viewer, review repo docs like a visual IDE, or collect Plan comments that should become coding-agent changes.

67

Quality

81%

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

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 compact, actionable reference with concrete commands, a sequenced workflow, and a clear privacy boundary. Main gaps are a missing MDX example and an explicit validate-fix-retry loop.

Suggestions

Add one copy-paste MDX snippet showing a valid visual block (e.g., api-endpoint or data-model) so the workflow's step 3 is fully executable.

Make the check->fix->re-check feedback loop explicit in the Agent Workflow ("If check fails, fix the MDX and re-run check until it passes").

Move the extended CLI variant list into a references file and keep SKILL.md to the default plus one targeted example to tighten token budget.

DimensionReasoningScore

Conciseness

Mostly lean with copy-paste command blocks and no padding about concepts Claude already knows; a few framing sentences (e.g., "It is for durable repo understanding, not a one-off plan") could be trimmed.

4 / 5

Actionability

Provides executable npx commands and concrete flag variants, but the Agent Workflow step on MDX block types is instructional without a copy-paste MDX example.

4 / 5

Workflow Clarity

The numbered Agent Workflow includes validation checkpoints (run check after editing, use verify before handoff), but lacks an explicit error-recovery feedback loop if check fails.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no bundle files; content is appropriately self-contained, though slightly above the simple-skill line and could in principle split privacy/CLI detail into references.

4 / 5

Total

16

/

20

Passed

Description

87%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 is well-constructed: it states a concrete capability and follows with an explicit, multi-phrase Use-when clause. Third-person voice is maintained and it avoids fluff.

Suggestions

Add a couple of synonyms or file/extension triggers (e.g., ".mdx", "repo diagram") to push trigger-term coverage toward comprehensive.

Consider naming the check/verify sub-actions in the description to round out the specificity of capabilities.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Open or create a repo-native visual documentation workspace", "launch a visual repo viewer", "review repo docs", "collect Plan comments"), though a few broad verbs and missing command-level capabilities leave minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Open or create a repo-native visual documentation workspace backed by local Plan MDX files") and when ("Use when the user asks to visualize a repository...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural phrases ("visualize a repository", "launch a visual repo viewer", "review repo docs like a visual IDE") give good keyword coverage, but no file extensions or synonyms are present.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (repo-native visual docs) with distinct triggers unlikely to fire for unrelated skills, minimizing conflict risk.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
BuilderIO/agent-native
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.