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.

2.04x

Quality

53%

Does it follow best practices?

Impact

100%

2.04x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/theme-factory/SKILL.md

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

Quality

Content

52%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 has a clear, well-sequenced workflow with good structural organization, but its guidance is largely high-level and lacks the concrete specifics (theme file format, how styling is applied per artifact type) needed to be fully actionable. Some duplicated bullets slightly hurt conciseness.

Suggestions

Specify the theme file format and include one example theme definition so the 'apply the theme' step is executable.

Remove the duplicated theme-detail bullets between the Purpose and Theme Details sections.

Add concrete application specifics per artifact type (e.g., how colors/fonts map onto slides vs. HTML), since 'apply the specified colors and fonts' is currently abstract.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the Purpose and Theme Details sections repeat the same bullets ("cohesive color palette with hex codes", "complementary font pairings"), so it could be tightened.	3 / 5
Actionability	Guidance stays high-level ("read the corresponding theme file", "apply the specified colors and fonts") without specifying the theme file format or how styling is concretely applied to different artifact types, leaving key execution details missing.	2 / 5
Workflow Clarity	Usage Instructions and Application Process give a clear sequenced workflow with an explicit confirmation checkpoint ("Wait for selection: Get explicit confirmation"), with only minor validation gaps.	4 / 5
Progressive Disclosure	Well-organized into labeled sections with one-level-deep references to theme-showcase.pdf and the themes/ directory, though some redundancy between sections keeps it just below the ideal.	4 / 5
	Total	13 / 20 Passed

Description

53%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 communicates a clear purpose and niche but lacks an explicit "Use when..." trigger clause, which caps its completeness. Specificity and trigger terms are adequate but not comprehensive, and typos ("reportings", "has been creating") slightly undercut polish.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., 'Use when styling slides, docs, or HTML pages, or when the user asks to apply a theme').

Fix typos ("reportings" → "reports", "has been creating" → "has been created") and tighten the artifact list.

Dimension	Reasoning	Score
Specificity	Names the domain (theming artifacts) and two concrete actions ("apply to any artifact", "generate a new theme on-the-fly"), matching the 1-2 concrete actions anchor rather than the several-actions level above.	3 / 5
Completeness	Has a clear "what" (toolkit for styling artifacts with themes) but no "Use when..." trigger clause, so per the missing-trigger guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Contains natural terms like "theme", "styling", "slides", "docs", and "HTML landing pages", but misses common synonyms and variations a user might say, fitting the partial-coverage anchor.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (applying curated themes to artifacts) with only minor overlap risk against general document-styling skills, fitting the mostly-distinct anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/theme-factory/SKILL.md
Commit: a9fa86d

Reviewed: about 18 hours 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.