feat: improve nuxt-users skill score to 100%#192
Open
rohan-tessl wants to merge 1 commit into
Open
Conversation
Hey @rrd108 👋 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 | |-------|--------|-------|--------| | nuxt-users | 94% | 100% | +6% | <details> <summary>Changes summary</summary> - **Removed redundant "When to use this skill" section** — the YAML description already covers trigger terms comprehensively, so this section was duplicating context without adding value - **Consolidated CLI fallback explanation** — the `loadNuxt` / `DB_*` fallback behavior was repeated across three sections (config reference, CLI commands, edge cases); consolidated into a single production note in the CLI section - **Replaced verbose edge cases with a troubleshooting table** — swapped the 6-item numbered list for a compact symptom/fix table, removing entries that restated earlier config guidance (password validation, Google OAuth) - **Trimmed unnecessary explanatory phrases** — removed padding like "This skill helps you work with..." (redundant with description), "required for protected routes" (evident from context), and "if needed for older setups" - **Reduced line count from 165 → 141** while preserving all actionable content </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 - [@rohan-tessl](https://github.com/rohan-tessl) - if you hit any snags. Thanks in advance 🙏
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
1 participant
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.
Hey @offgrid-ing 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:This PR optimizes the single
SKILL.mdin the repo — covering all skills present.Changes summary
talk to another agent,inter-agent messages,agent-to-agent communication,message another AI) — description score jumped from 68% to 100%arpc doctorconfirmation after webhook configurationHonest 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 - @rohan-tessl - if you hit any snags.
Thanks in advance 🙏