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 ./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 applying visual themes to artifacts and mentions the availability of pre-set and custom 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. The description is functional but would benefit from clearer trigger guidance and more natural user keywords.
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 design for slides, documents, or pages.'
Switch from second person ('you can apply') to 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 'branding', 'visual style', 'look and feel', 'design template', 'color scheme', or 'typography'.
| 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 artifact types listed. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 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 terms like 'slides', 'docs', 'HTML landing pages' could overlap with skills for creating those artifact types. The mention of '10 pre-set themes' adds some uniqueness, but without clearer trigger boundaries it could still conflict with presentation or document creation 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 structure and progressive disclosure, appropriately pointing to external theme files and a visual showcase PDF. However, it suffers from redundancy between sections (Purpose vs Theme Details), lacks concrete actionable guidance on how to actually apply theme styling to artifacts, and is missing validation/review checkpoints after theme application.
Suggestions
Remove the redundant 'Theme Details' section or merge it with 'Purpose' — the same three bullet points appear in both places.
Add concrete, actionable guidance on how to apply a theme to an artifact — e.g., show an example of reading a theme file and applying its hex codes/fonts to HTML or slide markup.
Add a validation/review step after theme application, such as showing the user a preview of the styled artifact and asking for confirmation before finalizing.
| 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 performed. | 2 / 3 |
Workflow Clarity | The steps are listed in a reasonable sequence (show showcase → ask → wait → apply), and the application process has steps, 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. | 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. | 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
- ComposioHQ/awesome-claude-skills
- Commit
362d354
- 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.