feat: improve skill scores for turbo-laravel#160
Closed
popey wants to merge 1 commit intohotwired-laravel:2.xfrom
Closed
feat: improve skill scores for turbo-laravel#160popey wants to merge 1 commit intohotwired-laravel:2.xfrom
popey wants to merge 1 commit intohotwired-laravel:2.xfrom
Conversation
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 🙏
Collaborator
|
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! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hullo @tonysm 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
All skills
developing-with-turbo-basics (+5%)
developing-with-turbo-drive (+1%)
developing-with-turbo-frames (+6%)
developing-with-turbo-streams (+6%)
developing-with-turbo-tests (no change)
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 🙏