theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
57
35%
Does it follow best practices?
Impact
100%
2.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/theme-factory/SKILL.mdQuality
Discovery
50%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 communicates the general purpose of theming artifacts and mentions specific artifact types and the existence of 10 pre-set themes, which is helpful. However, it lacks an explicit 'Use when...' clause, uses second person ('you can apply'), and could be more specific about concrete actions and trigger terms to better distinguish it from overlapping skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'theme', 'styling', 'brand colors', 'visual design', 'apply a theme', 'change the look'.
Replace second person voice ('you can apply') with third person ('Applies pre-set themes to artifacts') to match expected description conventions.
Include more natural trigger keywords users might say, such as 'design template', 'color scheme', 'typography', 'visual formatting', or 'restyle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (styling artifacts with themes) and lists some artifact types (slides, docs, reportings, HTML landing pages), but the actions are vague—'apply' and 'generate' are mentioned but not as clearly enumerated concrete actions like 'extract text, fill forms, merge documents'. | 2 / 3 |
Completeness | Describes what it does (applies pre-set themes or generates new themes for artifacts) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, so the 'when' is only implied from context. Per rubric guidelines, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'slides', 'docs', 'HTML landing pages', 'theme', 'colors/fonts', and 'styling', but misses common user-facing variations like 'design', 'branding', 'look and feel', 'visual style', 'template', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'themes' and '10 pre-set themes' adds some distinctiveness, but the broad scope covering slides, docs, reportings, and HTML pages could overlap with presentation skills, document formatting skills, or web design skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is overly verbose with significant redundancy between sections (Purpose, Theme Details, and Application Process repeat similar information). It lacks concrete, actionable guidance—there are no examples of theme file formats, no code showing how themes are applied to artifacts, and no validation steps. The workflow structure exists but is split across two overlapping sections without clear checkpoints.
Suggestions
Remove redundant sections (Theme Details repeats Purpose; Application Process overlaps Usage Instructions) and consolidate into a single clear workflow
Add a concrete example of a theme file format from the themes/ directory so Claude knows exactly what data structure to expect and apply
Include a specific example of applying a theme to an artifact (e.g., showing before/after HTML/CSS or slide markup with theme colors and fonts applied)
Add a validation step after theme application (e.g., 'Show the user a preview of the themed artifact and ask for confirmation before finalizing')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and repetitive. The 'Theme Details' section repeats the same bullet points from the 'Purpose' section nearly verbatim. The theme list descriptions are padding that Claude doesn't need since they're in the PDF/theme files. Multiple sections restate the same workflow. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. Instructions like 'apply the specified colors and fonts consistently' and 'ensure proper contrast and readability' are vague. There's no example of what applying a theme actually looks like—no CSS snippets, no HTML examples, no concrete format for theme files. | 1 / 3 |
Workflow Clarity | The workflow steps are listed in sequence (show showcase → ask → wait → apply), which provides basic structure. However, there are no validation checkpoints—no step to verify the theme was applied correctly, no feedback loop for user approval of the result, and the 'Application Process' section is a second workflow that partially overlaps with 'Usage Instructions'. | 2 / 3 |
Progressive Disclosure | References to `theme-showcase.pdf` and `themes/` directory suggest appropriate content splitting, but no bundle files are provided to verify these exist. The SKILL.md itself contains redundant sections that could be consolidated, and the references to external files aren't clearly signaled with navigation links. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
c911a92
- 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.