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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill theme-factory55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 skill's theming capabilities and lists artifact types, but lacks explicit trigger guidance ('Use when...') which is critical for skill selection. The language is somewhat generic and could benefit from more specific action verbs and natural user keywords to improve discoverability.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'apply theme', 'style my presentation', 'change colors', 'visual design', or 'make it look professional'
Include more natural user keywords such as 'design', 'branding', 'visual style', 'color scheme', 'typography', and 'formatting'
Specify concrete actions beyond 'apply' - e.g., 'customize color palettes, apply typography styles, switch between light/dark modes'
| 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 like color schemes, typography adjustments, or layout modifications. | 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. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this is weaker than that threshold. | 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', or 'visual appearance'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of '10 pre-set themes' and specific artifact types provides some distinction, but 'styling artifacts' is broad enough to potentially overlap with brand-specific styling skills, CSS skills, or general document formatting skills. | 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 workflow steps and good organization. However, it lacks concrete implementation details - no code examples, no sample theme file structure, and no validation steps for ensuring themes are applied correctly. The content would benefit from executable examples showing how to actually read and apply theme specifications.
Suggestions
Add a concrete example of a theme file structure from the themes/ directory showing the actual format (JSON, YAML, etc.) with hex codes and font names
Include a specific example of applying a theme to an artifact, showing before/after or the actual transformation process
Add validation steps to the Application Process, such as checking font availability or verifying color contrast ratios
Remove redundant descriptions between Purpose and Theme Details sections to improve conciseness
| 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 workflow but lacks concrete implementation details. No code examples for applying themes, no specific file paths for theme files, and no examples of what theme application looks like in practice. | 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 or handling cases where fonts aren't available. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. References external files appropriately (theme-showcase.pdf, themes/ directory) without deep nesting. Content is well-organized for a skill of this scope. | 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 | |
- 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.