Skip to content

feat: improve skill scores for react-doctor#104

Open
popey wants to merge 1 commit intomillionco:mainfrom
popey:improve/skill-review-optimization
Open

feat: improve skill scores for react-doctor#104
popey wants to merge 1 commit intomillionco:mainfrom
popey:improve/skill-review-optimization

Conversation

@popey
Copy link

@popey popey commented Mar 11, 2026

Hullo @aidenybai 👋

I ran your skills through tessl skill review at work and found some targeted improvements.

score_card

Here's the before/after:

Skill Before After Change
react-doctor 64% 94% +30%
remotion-best-practices 48% 93% +45%
animation-best-practices 94% 94%
Changes made

react-doctor (skills/react-doctor/SKILL.md)

  • Expanded frontmatter description with specific actions (lint, type-check, scan) and explicit "Use when..." trigger clause
  • Added prioritisation guidance to the workflow (errors before warnings, 80+ target score)

remotion-best-practices (.ami/skills/remotion-best-practices/SKILL.md)

  • Rewrote frontmatter description with concrete capabilities (compositions, animations, rendering, captions, audio) and "Use when..." clause
  • Expanded the "When to use" section with specific trigger scenarios
  • Added a "Quick start" section with sequenced rule paths for common tasks (new project, captions, audio, transitions, FFmpeg)
  • Renamed "How to use" to "Reference" for clearer navigation

animation-best-practices — already scoring 94%, left untouched.

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 and ask it to optimize your skill. Ping me - @popey - if you hit any snags.

Thanks in advance 🙏

Hullo @aidenybai 👋

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

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| react-doctor | 64% | 94% | +30% |
| remotion-best-practices | 48% | 93% | +45% |
| animation-best-practices | 94% | 94% | — |

<details>
<summary>Changes made</summary>

**react-doctor** (`skills/react-doctor/SKILL.md`)
- Expanded frontmatter description with specific actions (lint, type-check, scan) and explicit "Use when..." trigger clause
- Added prioritisation guidance to the workflow (errors before warnings, 80+ target score)

**remotion-best-practices** (`.ami/skills/remotion-best-practices/SKILL.md`)
- Rewrote frontmatter description with concrete capabilities (compositions, animations, rendering, captions, audio) and "Use when..." clause
- Expanded the "When to use" section with specific trigger scenarios
- Added a "Quick start" section with sequenced rule paths for common tasks (new project, captions, audio, transitions, FFmpeg)
- Renamed "How to use" to "Reference" for clearer navigation

**animation-best-practices** — already scoring 94%, left untouched.

</details>

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 - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@vercel
Copy link

vercel bot commented Mar 11, 2026

@popey is attempting to deploy a commit to the Million Team on Vercel.

A member of the Team first needs to authorize it.

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