Improve/skill review optimization#28
Open
yogesh-tessl wants to merge 2 commits intocoinset-org:mainfrom
Open
Conversation
Hey @cameroncooper 👋 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 | |-------|--------|-------|--------| | coinset-cli | 5% | 90% | +85% | The big jump is because the SKILL.md was missing YAML frontmatter entirely, which caused the reviewer to skip all LLM evaluation. Once that was fixed, I also made a couple of structural improvements. <details> <summary>Changes made</summary> - **Added YAML frontmatter** with a kebab-case `name` field and a detailed `description` including domain-specific trigger terms and a "Use when..." clause - **Moved reference tables to separate files** — the conditions opcode reference and known puzzle mod hashes now live in `references/conditions.md` and `references/puzzle-hashes.md`, linked from the main skill. This improves progressive disclosure and reduces token cost for the agent - **Added validation checkpoints to workflows** — key workflows like "get puzzle and solution" and "trace coin lineage" now include verification steps and error recovery guidance </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 @cameroncooper 👋
Clean CLI design. The auto-pretty-printing with positional args for required params and flags for optional ones makes the Chia RPC accessible without reading the full node docs. Nice touch including the Homebrew tap alongside go install. 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:The big jump is because the SKILL.md was missing YAML frontmatter entirely, which caused the reviewer to skip all LLM evaluation. Once that was fixed, I also made a couple of structural improvements.
Changes made
namefield and a detaileddescriptionincluding domain-specific trigger terms and a "Use when..." clausereferences/conditions.mdandreferences/puzzle-hashes.md, linked from the main skill. This improves progressive disclosure and reduces token cost for the agentHonest 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 🙏