From 32d7bc7fcb52f02b0add992df700d17625a9210b Mon Sep 17 00:00:00 2001 From: Alan Pope Date: Wed, 11 Mar 2026 15:26:31 +0000 Subject: [PATCH] feat: improve skill scores for react-doctor MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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% | — |
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](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 🙏 --- .ami/skills/remotion-best-practices/SKILL.md | 22 +++++++++----------- skills/react-doctor/SKILL.md | 6 ++++-- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/.ami/skills/remotion-best-practices/SKILL.md b/.ami/skills/remotion-best-practices/SKILL.md index 2f4684a..1abc49d 100644 --- a/.ami/skills/remotion-best-practices/SKILL.md +++ b/.ami/skills/remotion-best-practices/SKILL.md @@ -1,27 +1,25 @@ --- name: remotion-best-practices -description: Best practices for Remotion - Video creation in React +description: Remotion video creation patterns for React — compositions, animations, rendering, captions, and audio. Use when building programmatic videos, configuring frame rates and resolutions, adding transitions, embedding media assets, or troubleshooting Remotion render issues. metadata: tags: remotion, video, react, animation, composition --- ## When to use -Use this skills whenever you are dealing with Remotion code to obtain the domain-specific knowledge. +Use this skill whenever working with Remotion code — creating compositions, rendering video, adding animations, handling captions/subtitles, embedding audio/video assets, or troubleshooting render issues. -## Captions +## Quick start -When dealing with captions or subtitles, load the [./rules/subtitles.md](./rules/subtitles.md) file for more information. +For common tasks, start with these rules: -## Using FFmpeg +1. **New video project**: [compositions.md](rules/compositions.md) → [assets.md](rules/assets.md) → [animations.md](rules/animations.md) +2. **Add captions/subtitles**: [subtitles.md](rules/subtitles.md) → [display-captions.md](rules/display-captions.md) +3. **Audio work**: [audio.md](rules/audio.md) → [audio-visualization.md](rules/audio-visualization.md) +4. **Scene transitions**: [transitions.md](rules/transitions.md) → [timing.md](rules/timing.md) +5. **FFmpeg operations** (trimming, silence detection): [ffmpeg.md](rules/ffmpeg.md) -For some video operations, such as trimming videos or detecting silence, FFmpeg should be used. Load the [./rules/ffmpeg.md](./rules/ffmpeg.md) file for more information. - -## Audio visualization - -When needing to visualize audio (spectrum bars, waveforms, bass-reactive effects), load the [./rules/audio-visualization.md](./rules/audio-visualization.md) file for more information. - -## How to use +## Reference Read individual rule files for detailed explanations and code examples: diff --git a/skills/react-doctor/SKILL.md b/skills/react-doctor/SKILL.md index 8cc27cf..5c49f0a 100644 --- a/skills/react-doctor/SKILL.md +++ b/skills/react-doctor/SKILL.md @@ -1,6 +1,6 @@ --- name: react-doctor -description: Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project. +description: Runs react-doctor to lint, type-check, and scan React components for security, performance, and correctness issues. Use when validating changes, checking for errors, running diagnostics, or auditing a React codebase before shipping. version: 1.0.0 --- @@ -16,4 +16,6 @@ npx -y react-doctor@latest . --verbose --diff ## Workflow -Run after making changes to catch issues early. Fix errors first, then re-run to verify the score improved. +1. Run react-doctor after making changes. +2. Fix **errors** first (security, correctness), then **warnings** (performance, architecture). +3. Re-run to verify the score improved. Aim for 80+ on a healthy codebase.