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.
56
33%
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
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...'), reducing its utility for skill selection. It uses second person voice ('you can apply') which violates the third-person convention, and the action verbs are too generic to clearly distinguish this skill from other styling or document-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'theme', 'style', 'brand colors', 'visual design', 'look and feel', 'color scheme', 'typography'.
Rewrite in third person voice: e.g., 'Applies pre-set or custom visual themes to artifacts...' instead of 'you can apply'.
List more specific actions such as 'applies color palettes, sets font families, adjusts layout styling' to increase specificity and distinctiveness.
| 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 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, making it a weak 1-2. The description only implies when to use it. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'theme', 'styling', 'slides', 'docs', 'HTML landing pages', 'colors', 'fonts', but misses common user phrases like 'brand', 'look and feel', 'design', 'visual style', 'format'. Also uses second person ('you can apply') which is noted but scored under specificity. | 2 / 3 |
Distinctiveness Conflict Risk | The theming/styling niche is somewhat specific, but terms like 'slides', 'docs', 'reportings' could overlap with presentation-creation or document-editing skills. The mention of '10 pre-set themes' adds some distinctiveness but not enough to fully differentiate. | 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 workflow for applying themes to artifacts but suffers from significant verbosity and redundancy — the same three bullet points about what themes include appear three times. Actionability is weakened by the lack of any concrete examples of theme file format or how theme application actually works in practice. The workflow is clear but lacks validation steps for ensuring proper application.
Suggestions
Remove the redundant 'Theme Details' section entirely since it repeats the Purpose section verbatim, and consolidate the theme description into a single concise block.
Add a concrete example of a theme file's structure (e.g., a snippet showing the JSON/YAML format with hex codes and font names) so Claude knows exactly what to read and apply.
Add a validation step after theme application, such as 'Verify contrast ratios meet accessibility standards' or 'Show the user a preview slide before applying to all slides.'
Make the 'Create your Own Theme' section more actionable with specific guidance on color harmony rules or font pairing principles to follow.
| 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). The theme list descriptions add little actionable value beyond the theme names themselves. | 1 / 3 |
Actionability | The workflow steps are concrete enough (show PDF, ask user, apply theme), and it references specific file paths (themes/ directory, theme-showcase.pdf). However, there's no executable code, no example of what a theme file looks like, no concrete example of 'applying' a theme (e.g., CSS properties, HTML attributes, or slide XML modifications). The 'Create your Own Theme' section is particularly vague. | 2 / 3 |
Workflow Clarity | The usage instructions provide a clear 4-step sequence, and the application process adds another sequence. However, there are no validation checkpoints — no step to verify the theme was applied correctly, no feedback loop for contrast/readability issues mentioned in step 3 of the application process, and no error handling for missing theme files or invalid selections. | 2 / 3 |
Progressive Disclosure | References to themes/ directory and theme-showcase.pdf suggest appropriate content splitting, but no bundle files are provided to verify these exist. The SKILL.md itself contains redundant inline content (theme details repeated) that could be trimmed since the detail lives in the referenced files. The structure is reasonable but the navigation signals could be clearer with actual links. | 2 / 3 |
Total | 7 / 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 | |
d065ead
Table of Contents
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.