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.

79

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-structured: concrete CLI commands, a sequenced workflow with validation checkpoints, and a clear privacy boundary. No bundle files are referenced, and the self-contained organization is appropriate for this single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean and operational — copy-paste commands, a numbered workflow, and a load-bearing privacy boundary — with no padding explaining concepts Claude already knows, matching the level-3 "every token earns its place" anchor.

3 / 3

Actionability

Provides fully executable `npx @agent-native/core@latest visualize-repo` commands and variants plus specific block types (api-endpoint, data-model, wireframe, diagram, annotated-code), matching the copy-paste-ready level-3 anchor.

3 / 3

Workflow Clarity

The Agent Workflow is a clear 5-step sequence with explicit validation checkpoints (run `check` after editing MDX, use `verify` before handoff), exceeding the implicit-checkpoint level-2 anchor; it is not a destructive/batch operation that would require a spelled-out fix-and-retry loop to score 3.

3 / 3

Progressive Disclosure

A single self-contained document with well-organized sections and no nested external references; per the simple-skills note, a single-purpose skill needing no external references can score 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

100%

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 specific, uses natural trigger terms, explicitly pairs what-and-when, and carves out a distinct niche. It uses appropriate third-person/imperative voice with no first- or second-person phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Open or create a repo-native visual documentation workspace" and "create durable visual docs for APIs/components/models/flows" — matching the level-3 anchor of multiple specific concrete actions, not the level-2 partial coverage.

3 / 3

Completeness

Explicitly answers what (open/create a visual documentation workspace backed by local Plan MDX files) and when via a "Use when…" clause enumerating several trigger scenarios, matching the level-3 anchor rather than the implied-when level-2 anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "visualize a repository", "launch a visual repo viewer", "review repo docs like a visual IDE", "collect Plan comments" — with good breadth rather than jargon-only or partial coverage.

3 / 3

Distinctiveness Conflict Risk

The niche is specific (repo-native Plan MDX visual docs) with distinct triggers unlikely to fire for unrelated skills, satisfying the clear-niche level-3 anchor and well above the generic level-1/2 anchors.

3 / 3

Total

12

/

12

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.