artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
76
70%
Does it follow best practices?
Impact
78%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/03-developer-artifactsbuilder/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly defines its niche (complex multi-component HTML artifacts on claude.ai) with good technology-specific trigger terms and an explicit negative boundary that aids skill selection. The main weakness is that the 'what' portion describes the domain and technologies rather than listing specific concrete actions the skill enables. Overall it would perform well in a multi-skill selection scenario.
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'Creates multi-page dashboards, builds interactive forms with validation, implements tabbed layouts with shared state'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (HTML artifacts) and some technologies (React, Tailwind CSS, shadcn/ui), and mentions state management and routing, but doesn't list specific concrete actions like 'create dashboards, build multi-page apps, implement form wizards'. The capabilities are described more as categories than specific actions. | 2 / 3 |
Completeness | Clearly answers both what ('creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies') and when ('Use for complex artifacts requiring state management, routing, or shadcn/ui components'), and even specifies when NOT to use it ('not for simple single-file HTML/JSX artifacts'), which is excellent for disambiguation. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'React', 'Tailwind CSS', 'shadcn/ui', 'HTML artifacts', 'state management', 'routing', 'multi-component', 'complex artifacts', 'claude.ai'. These cover the key terms a user would naturally mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries: specifically targets multi-component, complex claude.ai HTML artifacts with named technologies, and explicitly excludes simple single-file artifacts. The negative boundary ('not for simple single-file HTML/JSX artifacts') significantly reduces conflict risk with simpler artifact-generation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a clear high-level workflow for creating artifacts with concrete shell commands for initialization and bundling. However, it falls short on the actual development guidance - Step 2 is essentially empty, referencing a 'Common Development Tasks' section that doesn't exist. For a skill focused on 'elaborate, multi-component' artifacts with 'state management, routing, or shadcn/ui components,' the absence of any code examples, patterns, or development guidance is a significant gap.
Suggestions
Add the missing 'Common Development Tasks' section with concrete code examples for common patterns (e.g., adding a new route, using shadcn/ui components, managing state) - these are the core value-add of the skill.
Add validation/error recovery guidance after the bundle step, e.g., checking bundle.html was created successfully and what to do if Parcel fails.
Include at least one complete mini-example showing a simple multi-component artifact from source to bundled output, demonstrating the React + shadcn/ui + Tailwind stack in practice.
Remove the checklist of what init creates (Claude doesn't need this) and instead use that space for actionable development patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary padding like the checklist of what the init script creates (Claude doesn't need to know all the details of what's pre-installed), and some verbose explanations like 'This file can be directly shared in Claude conversations as an artifact.' The design guidelines section is appropriately brief. | 2 / 3 |
Actionability | Provides concrete bash commands for init and bundling, but the core development step (Step 2) is vague - 'edit the generated files' with a reference to 'Common Development Tasks below' that doesn't exist in the content. No executable code examples for actual React/TypeScript development patterns, component usage, or state management despite the skill description mentioning these. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and logical, but lacks validation checkpoints. There's no guidance on what to do if bundling fails, no validation step after bundling (e.g., checking bundle.html size or correctness), and no error recovery guidance. For a multi-step build process, this is a notable gap. | 2 / 3 |
Progressive Disclosure | References external scripts and a shadcn/ui docs link, which is good. However, it references 'Common Development Tasks below' which doesn't exist in the content, and the skill description mentions complex features (state management, routing, shadcn/ui components) that have no reference files or guidance. The content is reasonably structured but missing promised sections. | 2 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- majiayu000/claude-skill-registry-data
- Commit
6770aaa
- 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.