CtrlK
BlogDocsLog inGet started
Tessl Logo

component

Create and publish one focused interactive UI component or choose a governed Kun visualization.

60

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 ./resources/bundled-skills/component/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured routing skill: lean sections, a concrete tool-selection table, a sequenced workflow, and a completion-gates checklist. Its only weakness is mild actionability gaps where directives are stated without execution detail.

DimensionReasoningScore

Conciseness

The body is lean throughout with no concept over-explanation; every section (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) is terse and assumes Claude's competence.

5 / 5

Actionability

A concrete tool-routing table names specific tools and directives like 'one data-kun-component-root' and 'declare minimum remote origins'; minor gaps remain (e.g., 'Test responsive behavior' lacks how-to), and no executable code is given, but it is actionable for an instruction-only routing skill.

4 / 5

Workflow Clarity

A clear 5-step sequence is present with a separate Completion gates section acting as a checklist; checkpoints are mostly present though slightly implicit, and the operation is non-destructive so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clearly labeled sections; per the simple-skills guideline this warrants a 5 with well-organized sections.

5 / 5

Total

18

/

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 states a clear purpose but omits any explicit trigger ('Use when...') guidance, which caps its completeness and weakens trigger-term quality. It is concise and reasonably distinct, yet light on concrete capability enumeration.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks for an interactive UI component, a dashboard widget, or a Kun flow/card/chart/diagram visualization') to lift the completeness cap and improve trigger-term coverage.

Enumerate the concrete deliverable types (flow, cards, callout, chart, table, diagram) directly in the description to raise specificity from a 1-2 action statement to comprehensive coverage.

Include natural synonyms and file/medium cues users say (e.g., 'interactive widget', 'data viz', 'HTML snippet') to broaden trigger-term recognition and reduce wrong-skill conflict.

DimensionReasoningScore

Specificity

Names the domain ('interactive UI component', 'Kun visualization') and 1-2 concrete actions (create+publish, choose), but does not enumerate component or visualization types, so it is not comprehensive.

3 / 5

Completeness

The 'what' is clear, but no 'when' guidance is present; per the rubric a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords ('interactive UI component', 'visualization') appear, but common natural variations and synonyms a user would say are missing and there is no 'Use when' phrasing.

3 / 5

Distinctiveness Conflict Risk

The 'Kun visualization' niche and focused interactive component framing are mostly distinct, with only minor overlap risk between the component and visualization routing paths.

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
KunAgent/Kun
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.