Improve/skill review optimization#2
Open
yogesh-tessl wants to merge 2 commits into
Open
Conversation
Hey @krispuckett 👋 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 | |-------|--------|-------|--------| | skill-issue | 95% | 100% | +5% | Your skill was already in great shape — 95% out of the gate. The reviewer flagged two areas in the **Content** dimension (88% → 100%): <details> <summary>Changes made</summary> - **Added example output section** — shows the actual markdown report format the audit produces, so agents know exactly what to expect and can interpret results for the user - **Added "Acting on Results" section** — a quick reference for each recommendation type (keep/update/review/remove) with concrete next steps, including a verification note before removing skills with broken deps Both additions directly addressed the `workflow_clarity` dimension (scored 2/3 → 3/3), which wanted a clearer post-audit workflow for acting on recommendations. </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 - [@yogesh-tessl](https://github.com/yogesh-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 @krispuckett 👋
"Find the skill issues before they find you" - the HR department framing is perfect. Inventory, usage tracking, health checks, and keep/update/remove recommendations for your entire skill roster. Love that it credits Josh Puckett for immediately knowing it had to be called /skill-issue. Wanted to suggest a few improvements to the SKILL.md.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Your skill was already in great shape - 95% out of the gate. The reviewer flagged two areas in the Content dimension (88% → 100%):
Changes made
Both additions directly addressed the
workflow_claritydimension (scored 2/3 → 3/3), which wanted a clearer post-audit workflow for acting on recommendations.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.
I also added a lightweight GitHub Action that auto-reviews any skill.md changed in a PR (includes min permissions, uses a pinned action version, only posts a review comment).
This means that it gives you and your contributors an instant quality signal before you have to review yourself (no signup, no tokens needed).
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 - @yogesh-tessl (https://github.com/yogesh-tessl) - if you hit any snags.
Thanks in advance 🙏