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.
67
53%
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 ./skills/anthropic-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—applying visual themes to various artifact types—and mentions a distinctive feature (10 pre-set themes). However, it lacks an explicit 'Use when...' clause, uses second-person voice ('you can apply'), and doesn't fully enumerate concrete actions or natural trigger terms users would employ. These gaps reduce its effectiveness for skill selection among many candidates.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'theme', 'styling', 'color scheme', 'typography', 'brand colors', 'visual design', or 'look and feel'.
Rewrite in third person voice (e.g., 'Applies pre-set or custom themes to artifacts' instead of 'you can apply').
List more specific concrete actions such as 'applies color palettes, sets font families, adjusts layout styling, previews theme options' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (styling artifacts with themes) and lists some artifact types (slides, docs, reportings, HTML landing pages), but the actual actions are vague—'apply' a theme or 'generate' a new one are only two loosely described actions rather than multiple concrete operations. | 2 / 3 |
Completeness | The 'what' is reasonably covered (apply pre-set themes or generate new themes for artifacts), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. Per the rubric, a missing 'Use when' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes some useful keywords like 'slides', 'docs', 'HTML landing pages', 'theme', 'colors/fonts', and 'styling', but misses common user phrasings like 'brand', 'design', 'look and feel', 'color scheme', 'typography', or file extensions. Coverage of natural trigger terms is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of '10 pre-set themes' and on-the-fly theme generation gives it some distinctiveness, but the broad scope ('slides, docs, reportings, HTML landing pages, etc.') and generic term 'styling artifacts' could overlap with other design, branding, or formatting skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structural organization and appropriate progressive disclosure with references to external theme files and a showcase PDF. However, it suffers from redundant content (Purpose and Theme Details sections overlap significantly) and lacks concrete, actionable guidance — there are no code examples, no sample theme file format, and no validation steps to confirm correct application. The custom theme creation section is particularly underspecified.
Suggestions
Remove the redundant 'Theme Details' section or merge it with 'Purpose' to eliminate the repeated bullet points about color palettes, font pairings, and visual identity.
Add a concrete example of a theme file's structure (e.g., a snippet showing hex codes and font names) so Claude knows exactly what format to expect when reading from `themes/`.
Add a validation/review step after theme application, such as 'Show the user a preview of the styled artifact and ask for confirmation before finalizing.'
Provide more specific guidance for custom theme creation — e.g., how many colors to include, what font sources to use, or an example of generating a theme from a description like 'corporate blue'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is noticeable redundancy — the bullet list under 'Purpose' (color palette, font pairings, visual identity) is repeated almost verbatim under 'Theme Details'. Some filler phrases like 'carefully selected' and 'curated collection' add no value. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides a clear process (show PDF, ask user, apply theme) and references theme files in a `themes/` directory, but lacks any concrete code, commands, or examples of what a theme file looks like or how to actually apply colors/fonts to an artifact. The custom theme section is especially vague with no specifics on color selection or font pairing logic. | 2 / 3 |
Workflow Clarity | Steps are listed 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 review after application, and no error handling guidance. The 'Application Process' step 3 ('Ensure proper contrast and readability') is vague with no concrete validation method. | 2 / 3 |
Progressive Disclosure | The skill appropriately keeps the overview concise and delegates detailed theme specifications to the `themes/` directory and visual showcase to `theme-showcase.pdf`. References are one level deep and clearly signaled. The structure is well-organized with logical sections. | 3 / 3 |
Total | 9 / 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
- boisenoise/skills-collections
- Commit
636b862
- 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.