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.
69
53%
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 the skill (applying themes to artifacts) and mentions specific artifact types and the existence of pre-set themes. 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 help Claude reliably select it over competing skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'theme', 'style', 'visual design', 'color scheme', 'branding', 'look and feel', or 'formatting'.
Switch from second person ('you can apply') to third person voice (e.g., 'Applies pre-set or custom themes to artifacts including slides, documents, reports, and HTML pages').
List more specific concrete actions such as 'apply color palettes, set typography, switch between 10 built-in themes, or generate custom themes on the fly'.
| 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 concrete, distinct operations. It doesn't list specific capabilities like 'change color palette', 'set typography', etc. | 2 / 3 |
Completeness | The 'what' is reasonably covered (styling artifacts with pre-set or custom themes), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the description of what it does, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes some useful keywords like 'theme', 'styling', 'slides', 'docs', 'HTML landing pages', 'colors', 'fonts'. However, it misses common user terms like 'branding', 'design', 'look and feel', 'visual style', 'format', or file extensions. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | The theming/styling focus provides some distinctiveness, but the broad scope ('slides, docs, reportings, HTML landing pages, etc.') and generic terms like 'styling' could overlap with brand-specific styling skills, presentation skills, or HTML/CSS skills. The mention of '10 pre-set themes' adds some uniqueness but not enough to fully distinguish it. | 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 is reasonably well-structured with good progressive disclosure, delegating details to supporting files. However, it suffers from redundancy between sections (Purpose and Theme Details repeat the same points) and lacks concrete, actionable guidance on how to actually apply a theme to an artifact — no code examples, no template snippets, no specific commands. The workflow is clear at a high level but missing validation/review checkpoints.
Suggestions
Remove the redundant 'Theme Details' section or merge its content with 'Purpose' to eliminate repetition and improve conciseness.
Add a concrete example showing what a theme file looks like (e.g., a snippet of JSON/YAML with hex codes and font names) and how to apply it to an artifact (e.g., CSS variables, HTML style attributes, or slide template modifications).
Add an explicit validation/review step after applying the theme, such as 'Show the user a preview of the styled artifact and ask for confirmation before finalizing'.
Structure the 'Create your Own Theme' section as a numbered workflow with explicit steps, similar to the main usage instructions.
| 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 workflow (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 'Apply the theme' step is vague — no executable guidance on how styling is applied. | 2 / 3 |
Workflow Clarity | Steps are listed in a reasonable 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 review of the styled artifact before finalizing. The 'Create your Own Theme' section also lacks structured steps. | 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. Content is well-organized into logical sections. | 3 / 3 |
Total | 9 / 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
7cc63f3
- 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.