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.
62
45%
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
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 provides a reasonable overview of the theming capability and mentions the 10 pre-set themes, but lacks explicit trigger guidance which is critical for skill selection. The artifact types listed help with specificity, but the description would benefit from natural user keywords and a clear 'Use when...' clause.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'theme', 'style', 'branding', 'colors', 'fonts', 'visual design', or 'look and feel'
Include more natural user phrases such as 'make it look professional', 'apply company branding', 'change the color scheme', or 'format with a theme'
Specify the concrete actions more clearly (e.g., 'applies color palettes, typography, and visual styling') rather than just 'apply themes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (styling artifacts with themes) and lists artifact types (slides, docs, reportings, HTML landing pages), but actions are limited to 'apply' and 'generate' without detailing specific styling operations. | 2 / 3 |
Completeness | Describes what the skill does (apply themes to artifacts) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'slides', 'docs', 'HTML landing pages', 'themes', 'colors/fonts', but missing common user phrases like 'style', 'design', 'branding', 'look and feel', 'formatting'. | 2 / 3 |
Distinctiveness Conflict Risk | The theme/styling focus provides some distinction, but 'artifacts' is very broad and could overlap with presentation skills, document formatting skills, or web design skills without clearer boundaries. | 2 / 3 |
Total | 7 / 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.
This skill provides a reasonable overview of a theming system with clear organization and appropriate references to external files. However, it lacks concrete implementation details - no examples of theme file contents, no code for applying themes, and no validation steps to ensure successful application. The workflow is understandable but would benefit from more actionable specifics.
Suggestions
Add a concrete example of a theme file's structure (e.g., show the JSON/YAML format with actual hex codes and font names)
Include specific file paths and naming conventions for the themes/ directory (e.g., 'themes/ocean-depths.json')
Add a validation step after theme application: 'Verify the theme was applied correctly by checking [specific elements] and ask user for confirmation before finalizing'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the theme details section repeats information already stated in the Purpose section (color palettes, font pairings, visual identity). Could be tightened. | 2 / 3 |
Actionability | Provides a clear process but lacks concrete implementation details. No code examples for how to actually apply themes, no file path specifics for the themes/ directory structure, and no examples of what theme files contain or how to read them. | 2 / 3 |
Workflow Clarity | Steps are listed clearly for both showing themes and applying them, but lacks validation checkpoints. No guidance on verifying theme application was successful, no error handling for missing theme files, and no feedback loop for user approval after application. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. Appropriately references external files (theme-showcase.pdf, themes/ directory) without deeply nesting. The overview is concise and points to detailed materials in the themes/ directory. | 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.