theme-factory
tessl i github:ComposioHQ/awesome-claude-skills --skill theme-factoryToolkit 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.
Validation
69%| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'you can' | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 11 / 16 Passed | |
Implementation
57%This skill provides a well-organized framework for theme application with good progressive disclosure, but lacks the concrete implementation details needed for full actionability. The workflow is clear at a high level but missing validation steps and specific guidance on how to actually read and apply theme files to artifacts.
Suggestions
Add a concrete example showing the structure of a theme file in themes/ directory and how to read/apply it
Include a validation step after theme application (e.g., 'Show the user a preview slide for approval before applying to all slides')
Remove redundant content between Purpose and Theme Details sections to improve conciseness
Add specific guidance on handling contrast/readability issues when they occur
| 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 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/apply them. | 2 / 3 |
Workflow Clarity | Steps are listed clearly for the selection process, but the application process lacks validation checkpoints. No verification step after applying themes, no guidance on what to do if contrast/readability fails, and no feedback loop for user approval of applied styling. | 2 / 3 |
Progressive Disclosure | Good structure with clear organization - overview in SKILL.md, detailed theme specs referenced in themes/ directory, and visual showcase in separate PDF. One-level-deep references are well-signaled. | 3 / 3 |
Total | 9 / 12 Passed |
Activation
33%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 a 'Use when...' clause with explicit triggers like 'Use when the user asks to style, theme, brand, or change the visual appearance of any artifact'
Include more natural trigger terms users would say: 'style', 'design', 'branding', 'visual formatting', 'color scheme', 'make it look professional'
Specify the concrete actions more clearly: 'applies color palettes, typography, and visual styling' rather than just 'apply to any artifact'
| 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 |
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.