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

46%

Does it follow best practices?

Impact

73%

1.43x

Average score across 5 eval scenarios

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./theme-factory/SKILL.md

The canonical home for this skill is theme-factory in anthropics/skills

Quality

Content

48%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured with clear, checkpointed workflows, but it is short on executable detail — no theme-file format, no application code, and the referenced bundle files (theme-showcase.pdf, themes/) do not exist. This balances a strong workflow score against weak actionability.

Suggestions

Add a concrete example of a theme file's structure (palette hex codes, font names) so Claude can read and apply a theme deterministically.

Provide an executable pattern or snippet for how to apply a theme's colors/fonts to a slide deck or HTML page, rather than the generic instruction to 'apply consistently'.

Create the referenced theme-showcase.pdf and themes/ directory so the progressive-disclosure references resolve to real files, and remove the duplicated bullet list.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned with no over-explanation of known concepts, but the color-palette/font-pairing bullets are duplicated verbatim in both Purpose and Theme Details and there is a 'themes themes' typo, leaving it at the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Guidance stays high-level ('Apply the specified colors and fonts consistently', 'generate a new theme similar to the ones above') with no concrete code, theme-file schema, or executable steps, matching the 'minimal concrete guidance; high-level hints' anchor.	2 / 5
Workflow Clarity	Both the usage and application processes are clearly numbered and include explicit checkpoints (wait for explicit confirmation; show custom theme for review), placing it just above the midpoint with only minor validation gaps.	4 / 5
Progressive Disclosure	Sections are well organized and reference theme-showcase.pdf and the themes/ directory, but neither bundle file actually exists, so the structure is present but the references are not clearly backed by real files.	3 / 5
	Total	12 / 20 Passed

Description

45%Weight 40%Scale 1-5

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 skill's purpose reasonably well and lists artifact types, but it lacks a 'Use when…' trigger clause, uses second-person voice, and relies on the generic term 'artifacts'. These keep most dimensions at the midpoint.

Suggestions

Add an explicit 'Use when…' clause naming natural trigger phrases (e.g., 'Use when styling a slide deck, doc, or landing page with a cohesive color and font theme, or when the user asks to theme an artifact').

Rewrite in third person and remove the generic word 'artifacts' in favor of the concrete types already listed ('slides, docs, reports, HTML landing pages').

Fix typos ('reportings', 'has been creating') and tighten the action list to concrete, specific capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain (styling artifacts with a theme) and only two concrete actions ('apply to any artifact', 'generate a new theme on-the-fly'); it uses second person ('you can apply'), which per guidelines reduces the score by one from a clear anchor-3 fit.	2 / 5
Completeness	It gives a clear 'what' (apply or generate themes for artifacts) but provides no 'when'/Use-when guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords appear ('slides, docs, reportings, HTML landing pages', 'theme', 'colors/fonts') but there is no natural trigger phrase and common synonyms are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The theme/color/font framing gives it a recognizable niche, but the generic term 'artifacts' keeps it from anchor 4 because it could overlap with general styling/formatting skills.	3 / 5
	Total	11 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: theme-factory/SKILL.md
Commit: be2a406

Reviewed: 3 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.