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.

1.43x

Quality

41%

Does it follow best practices?

Impact

73%

1.43x

Average score across 5 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/anthropic-theme-factory/SKILL.md

Quality

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

50%

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 redundancy and lack of concrete, actionable detail. The theme list and process steps are clear, but the skill never shows what a theme definition actually looks like or how to concretely apply it, making it more descriptive than instructive. Tightening the content, adding a sample theme spec, and including a verification step would significantly improve it.

Suggestions

Include a concrete example of a theme file's structure (e.g., a sample JSON/YAML with hex codes and font names) so Claude knows exactly what format to read and apply.

Remove the duplicated bullet list between 'Purpose' and 'Theme Details' sections — define theme components once.

Add a verification/review step after applying a theme (e.g., 'Show the user a preview of the styled artifact and ask for confirmation before finalizing').

In the 'Create your Own Theme' section, provide a template or example of the expected output format for a custom theme definition.

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 'distinct visual identity suitable for different contexts and audiences' add little value. However, it's not egregiously verbose.	2 / 3
Actionability	The skill provides a clear process (show PDF, ask user, apply theme) but lacks concrete, executable details. There are no code examples, no sample theme file format, no specific instructions on how to 'apply' colors/fonts to an artifact. The 'Create your Own Theme' section is especially vague — no structure or example for what a custom theme definition looks like.	2 / 3
Workflow Clarity	The workflow steps are listed and sequenced (show showcase → ask → wait → apply), but there are no validation checkpoints. After applying a theme, there's no step to verify the result with the user or check for contrast/readability issues programmatically. The application process section lists 'ensure proper contrast and readability' but provides no mechanism for doing so.	2 / 3
Progressive Disclosure	The skill references external files (theme-showcase.pdf, themes/ directory) which is good progressive disclosure, but the references are not clearly linked (no file paths with markdown links) and the inline content repeats what should be deferred to the theme files. The 'Create your Own Theme' section could benefit from being a separate reference document.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: boisenoise/skills-collections
Commit: 431bfad

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.