feat: improve find-skills skill score from 73% to 97%#56
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @ebursztein 👋 31 skills covering everything from VM sandboxing to benchmarking to initrd repacking — really impressive breadth for a project this deep. The `dev-testing-vm` skill scoring a perfect 100% out of the gate is rare to see. 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 | |-------|--------|-------|--------| | find-skills | 73% | 97% | +24% | **Focused on `find-skills`** — it had the most improvement headroom at 73% (all other skills scored 80%+). **Description improvements:** - Rewrote from vague "helps users discover and install" to specific concrete actions: "searches the skills.sh registry, compares options by install count and source reputation, and runs installation commands" - Kept the natural trigger phrases ("how do I do X", "find a skill for X") that were already well-chosen **Content improvements (biggest impact — Content went from 42% to 92%):** - Cut redundant "When to Use This Skill" section (frontmatter description already covers trigger conditions) - Removed "What is the Skills CLI?" explainer (Claude knows what package managers are) - Consolidated the 6-step hand-holding workflow into a tight 4-step sequence: Search → Verify Quality → Present/Install → Verify Installation - Added a missing post-install verification step with troubleshooting guidance (the original had no error recovery after `npx skills add`) - Replaced the verbose common categories table and search tips with inline search examples - Net result: 143 lines → 71 lines, same actionable content, better token efficiency 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.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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 @ebursztein 👋
really impressive breadth for a project this deep. 31 skills covering everything from VM sandboxing to benchmarking to initrd repacking. The
dev-testing-vmskill scoring a perfect 100% out of the gate is rare to see.ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:Focused on
find-skillsas it had the most improvement headroom at 73% (all other skills scored 80%+).Changes Summary
Description improvements:
Content improvements (biggest impact - Content went from 42% to 92%):
npx skills add)quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.
If you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.