CtrlK
BlogDocsLog inGet started
Tessl Logo

visual-answer

Answer code/product questions as visual Plan artifacts using repo, bridge, or GitHub context; use for API specs, UI look, schema models, and architecture.

70

Quality

88%

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

90%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.

An exemplary instruction-only skill body: concrete tools, a complete publish example, explicit negative guidance, and crisp routing against sibling skills. The only gaps are a missing post-publish verification step and the absence of any external references despite a body length that is starting to justify them.

DimensionReasoningScore

Conciseness

Lean and efficient across ~90 lines: trigger examples, a 5-step workflow, one compact JSON example, one shell command, and a Don't list — every token earns its place with zero explanation of concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance: named tools to call (get-plan-blocks, list-plan-components), a per-question-type block-selection list, a complete copy-paste-ready visual-answer-source.json example, and the full publish command with flags (--source-url, --prev-plan-id, --visibility).

5 / 5

Workflow Clarity

The 5-step sequence is clear and guardrailed ('Do not invent endpoints, schema fields, UI states'), but there is no explicit validation checkpoint (e.g., confirm blocks rendered or check visual-answer-url.txt after publish). Publishing is not destructive or batch, so the anchor-3 cap does not apply; it still lacks the validate/verify feedback loop of anchor 5.

4 / 5

Progressive Disclosure

Well-organized sections with no nested references and all content appropriately inline for a skill of this size. The body exceeds the ~50-line simple-skill threshold, so the automatic 5 does not apply, and growing detail (block-type matrix, terminal handoff) could eventually warrant a reference file.

4 / 5

Total

18

/

20

Passed

Description

83%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.

A tight, well-constructed description that explicitly covers what the skill does and when to use it with concrete trigger topics. Its only weaknesses are the single dominant action verb and slightly thin synonym coverage for natural user phrasings.

DimensionReasoningScore

Specificity

Names the domain (visual Plan artifacts for code/product questions), the source contexts (repo, bridge, GitHub), and concrete artifact domains (API specs, UI look, schema models, architecture), sitting between anchors 3 and 4. 'Answer' is the only true action verb, keeping it below anchor 5's multi-action coverage.

4 / 5

Completeness

Explicitly answers both 'what' ('Answer code/product questions as visual Plan artifacts using repo, bridge, or GitHub context') and 'when' ('use for API specs, UI look, schema models, and architecture') with concrete trigger topics, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

'API specs', 'UI look', 'schema models', and 'architecture' are natural phrases users would say when needing this skill. Common variations like 'draw the flow', 'data model', or 'diagram' are missing, so it falls just short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Visual Plan artifacts' for inspection-based answers is a fairly distinct niche, but closely related sibling skills (visual-plan, visual-recap) share the Plan-artifact framing and the description alone does not draw that boundary, giving minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

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.