The theme-factory skill, reviewed

What it tells the agent to do

1. Show theme-showcase.pdf to the user without modifying it
2. Ask which of the 10 themes to apply and wait for explicit confirmation
3. Read the chosen theme's file from the themes/ directory
4. Apply its colors and fonts consistently across the artifact, keeping contrast readable
5. If no preset fits, generate a named custom theme from the user's description and show it for review
6. Once the custom theme is approved, apply it the same way

Lines worth reading

Straight from the file, with why each one matters.

1. line 3There are 10 pre-set themes with colors/fonts

   The trigger. It says what the skill offers but never says 'use when', so the agent has to infer the moment.

2. line 23Do not make any modifications to it; simply show the file for viewing.

   A sharp guardrail. It stops an eager agent from 'improving' the showcase PDF.

3. line 25Get explicit confirmation about the chosen theme

   A good habit. The agent asks before restyling your whole deck, not after.

4. line 10professional font and color themes themes

   Curated with care, proofread with less. The 'reportings' and 'has been creating' in the description agree.

5. line 59Give the theme a similar name describing what the font/color combinations represent.

   Custom themes get evocative names like the presets. Expect a 'Rainy Tuesday' sooner or later.

Watch out for

Nothing risky that Kin could see in SKILL.md. Scripts beside it were not read.

The scorecard

• TriggerSays when to use it
  6/10

  Says what it does and names artifacts, but has no 'use when' and has typos.

• FocusOne clear job
  8/10

  One job: theme an artifact. Line 14 narrows it to slide decks, which muddles the scope a bit.

• LeanLight to load
  8/10

  Short, with theme data pushed to themes/. The feature list is repeated twice.

• ConcreteSteps you can follow
  5/10

  Clear pick-then-apply flow, but no theme file format, no example and no done check.

• SafeSafe to run
  10/10

  No commands, network calls or secrets. It only reads local theme files.

How it could be better

1. Add a clear 'use when' to the description

   The agent decides on the description alone, so it should name the request words and the moment to reach for the skill.

   Add

   description: Apply a consistent color palette and font pairing to slides, documents, reports or HTML pages. Use when the user asks to theme, style, restyle or make an artifact look professional or on-brand. Offers 10 preset themes and can create a custom theme from a description.

   Copy

2. Show the theme file format and one example

   Without knowing what a theme file holds, the agent can't tell how to map colors to titles, backgrounds and accents.

   Add

   ## Theme file format
   Each file in themes/ looks like:
   ```
   name: <Theme Name>
   colors:
     primary: <#hex>
     secondary: <#hex>
     accent: <#hex>
     background: <#hex>
     text: <#hex>
   fonts:
     heading: <font>
     body: <font>
   ```
   Use primary for titles, background for slide fills, text for body copy and accent for highlights.

   Copy

3. Define what done looks like

   'Ensure proper contrast' is advice the model already has; a checkable rule makes it real.

   Add

   ## Check before finishing
   - Body text vs background contrast is at least 4.5:1
   - Every slide or section uses only the theme's colors and two fonts
   - Tell the user which theme was applied and list any element you could not restyle

   Copy

4. Remove the duplicated feature list

   Lines 14-17 and 45-48 say the same thing, which costs context and adds nothing.

   Add

   ## Theme Details
   Each theme's full spec lives in `themes/<theme-name>.<ext>`. Read only the chosen one.

   Copy