artisan

Implementing production frontend code for React/Vue/Svelte: hooks design, state management, Server Components, form handling, data fetching. Converts Forge prototypes to production quality.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./artisan/SKILL.md

Quality

Content

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

A well-structured, actionable skill body with an exemplary reference map and clear phased workflow; its main weakness is conciseness, driven by an HTML comment block that duplicates visible tables and some explanatory padding.

Suggestions

Remove or collapse the leading HTML comment block (CAPABILITIES_SUMMARY / COLLABORATION_PATTERNS / BIDIRECTIONAL_PARTNERS) since the same information already appears in the Framework Coverage and Collaboration tables.

Trim educational parentheticals in the capabilities list (e.g. 'Baseline 2024', 'Chrome Canary', explanatory CSS descriptions) that restate concepts Claude already knows.

Make the VERIFY feedback loop explicit in the Workflow table (e.g. 'if checklist fails: fix and re-VERIFY; only proceed when VERIFY passes') to reach full workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and information-dense, but the leading HTML comment block (CAPABILITIES_SUMMARY, COLLABORATION_PATTERNS) duplicates the visible Framework Coverage and Collaboration tables, and some parentheticals (e.g. 'Baseline 2024', 'Chrome Canary') explain concepts Claude already knows.	3 / 5
Actionability	Guidance is concrete and executable — specific version pins (React 19.2.1+, Next.js 15.1.4+), libraries (RHF + Zod v4, TanStack Form v1), thresholds (INP < 200ms, WCAG ≥ 24×24px), and a branded-type code example — with only minor gaps from sparse full code blocks (deferred to reference files).	4 / 5
Workflow Clarity	A clear ANALYZE → DESIGN → IMPLEMENT → VERIFY → HANDOFF sequence with per-recipe VERIFY gates is present, but the explicit validate → fix → re-validate feedback loop is implied rather than spelled out, keeping it below the anchor-5 example.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with a dedicated Reference Map table giving well-signaled, one-level-deep references (reference/.md, _common/.md) organized for easy navigation, matching the clear-overview anchor.	5 / 5
	Total	16 / 20 Passed

Description

75%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 specific, well-niched description that names concrete capabilities and distinct frameworks, but it omits an explicit "Use when..." trigger clause, which caps its completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when converting Forge prototypes to production React/Vue/Svelte components, or implementing production frontend involving hooks, state management, Server Components, forms, or data fetching.'

Include common synonyms and file extensions (.tsx, .jsx, .vue, .svelte) to raise trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — "hooks design, state management, Server Components, form handling, data fetching" plus "Converts Forge prototypes to production quality" — giving comprehensive coverage of the frontend production domain.	5 / 5
Completeness	It clearly answers "what" (production frontend implementation across listed capabilities) but has no explicit "Use when..." trigger clause; per the rubric guideline, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms users say are well covered ("React/Vue/Svelte", "hooks", "Server Components", "form handling", "data fetching", "Forge prototypes"), but common synonyms and file extensions (.tsx, .jsx, .vue, .svelte) are missing, so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche — production-quality frontend for React/Vue/Svelte with Forge prototype conversion — with distinct triggers and minimal overlap risk against neighboring skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: simota/agent-skills
Path: artisan/SKILL.md
Commit: f425adc

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.