Skip to content

feat: improve skill scores for turbo-laravel#160

Closed
popey wants to merge 1 commit intohotwired-laravel:2.xfrom
popey:improve/skill-review-optimization
Closed

feat: improve skill scores for turbo-laravel#160
popey wants to merge 1 commit intohotwired-laravel:2.xfrom
popey:improve/skill-review-optimization

Conversation

@popey
Copy link

@popey popey commented Mar 17, 2026

Hullo @tonysm 👋

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

Skill Before After Change
developing-with-turbo-basics 81% 86% +5%
developing-with-turbo-drive 89% 90% +1%
developing-with-turbo-frames 90% 96% +6%
developing-with-turbo-streams 90% 96% +6%
developing-with-turbo-tests 94% 94%
Changes made

All skills

  • Converted frontmatter description from YAML chevron to standard quoted string format for better tooling compatibility

developing-with-turbo-basics (+5%)

  • Replaced vague "Basics of developing with Turbo Laravel" opening with specific actions: "Implements Turbo Streams, configures Turbo Frames, and integrates Hotwire patterns"
  • Removed conceptual "Philosophy: HTML Over the Wire" section — Claude already understands these concepts, and this was adding ~100 tokens of non-actionable context
  • Trimmed the Turbo Drive explanation down to just the IMPORTANT callout directing to the sub-skill

developing-with-turbo-drive (+1%)

  • Condensed the introductory paragraph and "How It Works" section — removed explanations of fetch requests, History API, and DOM replacement that Claude already knows
  • Trimmed Navigation Types to focus on Turbo-specific behaviors only

developing-with-turbo-frames (+6%)

  • Added a "Quick Start" workflow section with a clear 4-step implementation sequence
  • Added an IMPORTANT callout about frame ID matching (a common pitfall that causes silent failures)

developing-with-turbo-streams (+6%)

  • Added a "Quick Start" workflow section with a 5-step sequence covering both HTTP streams and broadcasting setup
  • Added an IMPORTANT troubleshooting callout for when broadcasts aren't received (channel auth, Echo config, WebSocket connection)

developing-with-turbo-tests (no change)

  • Added a Troubleshooting section for assertTurboStream() and broadcast assertion failures — score held steady at 94% as this was already high-quality

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 @tonysm 👋

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

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| developing-with-turbo-basics | 81% | 86% | +5% |
| developing-with-turbo-drive | 89% | 90% | +1% |
| developing-with-turbo-frames | 90% | 96% | +6% |
| developing-with-turbo-streams | 90% | 96% | +6% |
| developing-with-turbo-tests | 94% | 94% | — |

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

**All skills**
- Converted frontmatter description from YAML chevron to standard quoted string format for better tooling compatibility

**developing-with-turbo-basics** (+5%)
- Replaced vague "Basics of developing with Turbo Laravel" opening with specific actions: "Implements Turbo Streams, configures Turbo Frames, and integrates Hotwire patterns"
- Removed conceptual "Philosophy: HTML Over the Wire" section — Claude already understands these concepts, and this was adding ~100 tokens of non-actionable context
- Trimmed the Turbo Drive explanation down to just the IMPORTANT callout directing to the sub-skill

**developing-with-turbo-drive** (+1%)
- Condensed the introductory paragraph and "How It Works" section — removed explanations of fetch requests, History API, and DOM replacement that Claude already knows
- Trimmed Navigation Types to focus on Turbo-specific behaviors only

**developing-with-turbo-frames** (+6%)
- Added a "Quick Start" workflow section with a clear 4-step implementation sequence
- Added an IMPORTANT callout about frame ID matching (a common pitfall that causes silent failures)

**developing-with-turbo-streams** (+6%)
- Added a "Quick Start" workflow section with a 5-step sequence covering both HTTP streams and broadcasting setup
- Added an IMPORTANT troubleshooting callout for when broadcasts aren't received (channel auth, Echo config, WebSocket connection)

**developing-with-turbo-tests** (no change)
- Added a Troubleshooting section for assertTurboStream() and broadcast assertion failures — score held steady at 94% as this was already high-quality

</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 🙏
@tonysm
Copy link
Collaborator

tonysm commented Mar 17, 2026

Sorry, don't see anything fundamental changed in the skills, so won't merge. Let me know if you run them on your Hotwired apps for a while and notice a significant improvement. Thanks!

@tonysm tonysm closed this Mar 17, 2026
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.

2 participants