feat: improve 15 skill definitions via tessl skill review#13
Open
popey wants to merge 1 commit intobrianlovin:mainfrom
Open
feat: improve 15 skill definitions via tessl skill review#13popey wants to merge 1 commit intobrianlovin:mainfrom
popey wants to merge 1 commit intobrianlovin:mainfrom
Conversation
Hullo @brianlovin 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | sentry | 60% | 100% | +40% | | simplify | 59% | 89% | +30% | | deslop | 74% | 100% | +26% | | rams | 81% | 100% | +19% | | skill-creator | 76% | 93% | +17% | | workflow | 80% | 96% | +16% | | bun | 86% | 100% | +14% | | playwriter | 83% | 96% | +13% | | favicon | 76% | 89% | +13% | | find-skills | 84% | 93% | +9% | | react-doctor | 91% | 100% | +9% | | knip | 81% | 89% | +8% | | agent-browser | 90% | 96% | +6% | | tdd | 88% | 93% | +5% | | chrome-webstore-release-blueprint | 89% | 89% | 0% | Average score improved from 80% to 95% (+15% overall). Skills not modified: electron-wrapper (already 100%), fix-sentry-issues (already 96%, no improvements found), reclaude (blocked by reserved word in name field). Changes include: expanded frontmatter descriptions with trigger terms and "Use when" clauses, added concrete before/after code examples, structured workflows with validation steps, removed redundant explanatory text, extracted verbose sections to reference files, and added error handling guidance. 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. If you want to run reviews, evals and optimizations yourself, just npm install @tessl/cli then run tessl skill review path/to/your/SKILL.md, and click here to find out more: https://tessl.io/registry/skills/submit
Author
|
Seems my colleague also reached out to you via #14 Apologies for the duplication of work here. We meant well, and didn't intend to cause extra effort on your part. Just trying to help 🙏 |
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.
Hullo @brianlovin 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements.Here's the before/after in text form:
Average score improved from 80% to 95% (+15% overall).
Skills not modified: electron-wrapper (already 100%), fix-sentry-issues (already 96%, no improvements found), reclaude (blocked by reserved word in name field).
Changes include: expanded frontmatter descriptions with trigger terms and "Use when" clauses, added concrete before/after code examples, structured workflows with validation steps, removed redundant explanatory text, extracted verbose sections to reference files, and added error handling guidance.
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.
If you want to run reviews, evals and optimizations yourself, just
npm install @tessl/clithen runtessl skill review path/to/your/SKILL.md, and click here to find out more: https://tessl.io/registry/skills/submit