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
33%
Does it follow best practices?
Impact
73%
1.43xAverage score across 5 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/theme-factory/SKILL.mdQuality
Discovery
32%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 conveys the general purpose of applying visual themes to artifacts but lacks explicit trigger guidance ('Use when...'), uses second person voice ('you can apply'), and doesn't provide enough specific action verbs or natural user keywords. It would benefit from clearer trigger terms and a more structured format separating what it does from when it should be selected.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to style, theme, or visually format an artifact, or mentions colors, fonts, branding, or visual design.'
Replace second person ('you can apply') with third person ('Applies pre-set or custom themes to artifacts') to match the expected voice.
Include more natural trigger terms users might say, such as 'design', 'visual style', 'brand colors', 'look and feel', 'formatting', 'appearance'.
| 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 elaborated with concrete operations like 'change color palette', 'set typography', etc. | 2 / 3 |
Completeness | Describes what it does (styling artifacts with themes) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'when' is entirely absent here, not even implied clearly, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'theme', 'styling', 'slides', 'docs', 'HTML landing pages', and 'colors/fonts', but misses common user phrases like 'brand', 'look and feel', 'design', 'visual style', 'formatting'. Also uses second person ('you can apply') which is penalized under specificity. | 2 / 3 |
Distinctiveness Conflict Risk | The theming/styling niche is somewhat specific, but terms like 'slides', 'docs', 'reportings' could overlap with presentation, document, or reporting skills. The mention of '10 pre-set themes' adds some distinctiveness but not enough to clearly separate it from general styling or branding skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%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 reasonable high-level framework for theme selection and application but suffers from significant redundancy (repeating the same three bullet points in multiple sections) and lacks concrete, actionable details like actual hex codes, font names, or examples of applied themes. The workflow is sequential but missing validation steps for verifying correct application, and the custom theme creation section is too vague to be useful.
Suggestions
Remove the redundant 'Theme Details' section entirely since it repeats the Purpose section verbatim, and consolidate the 'Application Process' into the 'Usage Instructions' section.
Add a concrete example of a theme specification (e.g., Ocean Depths with actual hex codes and font names) so Claude knows the exact format to expect from theme files.
Add a validation step after theme application: 'Show the user a preview of the styled artifact and ask for confirmation before finalizing.'
Make the 'Create your Own Theme' section actionable by specifying constraints (e.g., minimum contrast ratios, number of colors to include, recommended Google Fonts categories) and providing an example custom theme output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant redundancy throughout. The 'Purpose' section repeats what themes include, then 'Theme Details' repeats the exact same three bullet points verbatim. The skill explains obvious concepts Claude already knows (what a color palette is, what font pairings are) and restates the same information across multiple sections. | 1 / 3 |
Actionability | The workflow steps are listed but lack concrete specifics—no example of how to read a theme file, no sample theme structure showing hex codes/font names, no code or commands for applying styles. The 'Create your Own Theme' section is entirely vague with no concrete guidance on color selection, font pairing rules, or output format. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence for both the selection and application processes, but there are no validation checkpoints—no step to verify the theme was applied correctly, no feedback loop for user approval after application, and no guidance on what to do if contrast/readability checks fail. | 2 / 3 |
Progressive Disclosure | References to `theme-showcase.pdf` and `themes/` directory are present but no bundle files were provided to support them. The content that could be in the main file (like a quick-reference table of theme colors) is missing, while content that should be delegated (the full theme list descriptions) is inline but shallow. The structure is reasonable but the references are unverifiable. | 2 / 3 |
Total | 7 / 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
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.