Skip to content

feat: improve theme-creator skill score from 54% to 90%#3

Open
yogesh-tessl wants to merge 1 commit into
Automattic:trunkfrom
yogesh-tessl:improve/skill-review-optimization
Open

feat: improve theme-creator skill score from 54% to 90%#3
yogesh-tessl wants to merge 1 commit into
Automattic:trunkfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl

@yogesh-tessl yogesh-tessl commented May 18, 2026

Copy link
Copy Markdown

Hey @glendaviesnz 👋

truly impressive. 8 skills spanning the full WordPress creation flow, from site-creator and theme-creator through to auditing. The plugin-creator and block-creator skills in particular are going to save people a lot of setup time.

ran your skills through tessl skill review at work and found some targeted improvements for the theme-creator skill. Here's the before/after:

Skill Before After Change
theme-creator 54% 90% +36%
What changed in theme-creator
  • Expanded frontmatter description - added concrete actions (theme.json configuration, block templates, template parts, global styles) and a full "Use when..." clause with natural trigger terms (FSE theme, full site editing, block-based theme, Gutenberg templates)
  • Added functions.php bootstrap example - copy-paste-ready snippet for enqueueing style.css and editor styles, replacing the previous prose-only instruction
  • Added full-width section block markup pattern - concrete HTML example showing the strict outer/inner shell pattern with align:"full" and align:"wide", replacing verbose bullet-point descriptions
  • Trimmed layout rules - consolidated 10 bullet points into 4 focused rules plus the concrete example, cutting redundancy while preserving all guidance
  • Removed Ownership section - this was meta-documentation that restated what the workflow already conveys; the skill delegation references to studio and auditing are preserved inline

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

If you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

Hey @glendaviesnz 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements for the `theme-creator` skill. Here's the full before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| theme-creator | 54% | 90% | +36% |
| auditing | 68% | 68% | — |
| block-creator | 72% | 72% | — |
| design-previews-creator | 68% | 68% | — |
| plugin-creator | 89% | 89% | — |
| site-creator | 63% | 63% | — |
| studio | 61% | 61% | — |
| wordpress-creator | 82% | 82% | — |

<details>
<summary>What changed in <code>theme-creator</code></summary>

- **Expanded frontmatter description** — added concrete actions (theme.json configuration, block templates, template parts, global styles) and a full "Use when..." clause with natural trigger terms (FSE theme, full site editing, block-based theme, Gutenberg templates)
- **Added `functions.php` bootstrap example** — copy-paste-ready snippet for enqueueing `style.css` and editor styles, replacing the previous prose-only instruction
- **Added full-width section block markup pattern** — concrete HTML example showing the strict outer/inner shell pattern with `align:"full"` and `align:"wide"`, replacing verbose bullet-point descriptions
- **Trimmed layout rules** — consolidated 10 bullet points into 4 focused rules plus the concrete example, cutting redundancy while preserving all guidance
- **Removed Ownership section** — this was meta-documentation that restated what the workflow already conveys; the skill delegation references to `studio` and `auditing` are preserved inline

</details>

I also stress-tested your `plugin-creator` skill against a few real-world task evals and it held up really well on REST endpoint scaffolding with capability checks and nonce verification. Kudos for that.

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch — just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me — [@yogesh-tessl](https://github.com/yogesh-tessl) — if you hit any snags.

Thanks in advance 🙏
@yogesh-tessl

Copy link
Copy Markdown
Author

hey @glendaviesnz 👋, just a friendly follow-up in case this got buried, happy to help move it forward!
Totally fine if there's a process, just wanted to keep it visible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant