CtrlK
BlogDocsLog inGet started
Tessl Logo

create-component

Create a new Spark UI component with complete file structure including component, styles, tests, stories, and documentation. Use when the user wants to create a new component or add a component to the design system.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is well-organized, concise, and action-oriented with a clear sequenced workflow and verification commands. Its main weakness is the absence of executable code examples and an explicit error-recovery feedback loop around the verification step.

Suggestions

Add at least one minimal copy-paste-ready component template (e.g., a stub .tsx with CVA + data-spark-component) so the guidance reaches fully-executable actionability.

Turn the Verify step into an explicit feedback loop: 'If lint/typecheck/tests fail, fix the reported issues and re-run until all pass before considering the component complete.'

Consider moving the per-file conventions (stories CSF structure, doc.mdx section order) into a bundled reference file and signaling it from SKILL.md to deepen progressive disclosure as the skill grows.

DimensionReasoningScore

Conciseness

The body is bullet-driven and lean, with no conceptual padding or explanation of things Claude already knows (e.g., TypeScript, CVA); every section earns its place, fitting the lean-and-efficient anchor.

3 / 3

Actionability

It gives concrete file names, tooling (Vitest+RTL, CVA, Storybook CSF), and real commands (npm run lint/typecheck/test), but as a checklist rather than executable/copy-paste component code, so it stops short of the fully-executable level 3.

2 / 3

Workflow Clarity

Steps are clearly sequenced 1–10 with an explicit terminal verify step and concrete commands, but it lacks an explicit validate→fix→retry feedback loop, leaving checkpoints present yet without error-recovery guidance.

2 / 3

Progressive Disclosure

The skill is single-purpose with well-organized sections and no nested/deep references; the only referenced paths are external repo locations, so the simple-skill allowance applies and the structure is clear.

3 / 3

Total

10

/

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 concise, concrete, and clearly answers both what the skill does and when to use it with natural trigger terms. It is among the strongest examples in the rubric.

DimensionReasoningScore

Specificity

Lists several concrete deliverables ("component, styles, tests, stories, and documentation") and a concrete action ("Create a new Spark UI component with complete file structure"), matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly states what it does and includes an explicit "Use when the user wants to create a new component or add a component to the design system" trigger, satisfying both the what and when.

3 / 3

Trigger Term Quality

Uses natural phrasing a user would say ("create a new component", "add a component", "design system"); these are exactly the terms someone would utter when needing this skill, not jargon.

3 / 3

Distinctiveness Conflict Risk

The "Spark UI" / "design system" framing carves a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
leboncoin/spark-web
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.