feat: improve skill scores for dojoengine/book#480
Open
rohan-tessl wants to merge 2 commits intodojoengine:mainfrom
Open
feat: improve skill scores for dojoengine/book#480rohan-tessl wants to merge 2 commits intodojoengine:mainfrom
rohan-tessl wants to merge 2 commits intodojoengine:mainfrom
Conversation
Hey 👋 @kariy 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 | |-------|--------|-------|--------| | dojo-vrf | 0% | 90% | +90% | | dojo-review | 66% | 100% | +34% | | dojo-system | 66% | 94% | +28% | | dojo-world | 71% | 100% | +29% | | dojo-model | 74% | 86% | +12% | This PR intentionally caps changes to five skills to keep it reviewable. The included GitHub Action workflow (see below) will surface Tessl feedback on future `SKILL.md` changes automatically. <details> <summary>Changes summary</summary> **dojo-vrf (0% → 90%)** - Added missing YAML frontmatter (name, description, allowed-tools) — this was the sole reason for the 0% score - Expanded description with specific trigger terms (dice rolls, shuffling cards, loot drops) - Added verification and related skills sections **dojo-review (66% → 100%)** - Removed unnecessary "When to Use", "What This Skill Does", "Quick Start" sections - Added explicit 4-step review workflow with verification - Streamlined code examples while preserving all ❌/✅ patterns - Added structured review checklist **dojo-system (66% → 94%)** - Consolidated duplicate content (imports, world access, events were explained multiple times) - Added import reference table for quick lookup - Removed redundant "When to Use", "What This Skill Does", "Quick Start" sections - Added safe subtraction pattern in the stateless design example - Added verification section **dojo-world (71% → 100%)** - Replaced verbose permission explanations with a clear hierarchy diagram and role comparison table - Consolidated CLI commands into a single reference block - Added troubleshooting table for common permission errors - Removed redundant intro sections - Added verification section **dojo-model (74% → 86%)** - Removed "When to Use", "What This Skill Does", "Quick Start" sections - Expanded description with additional trigger terms (composite keys, singletons, data schemas) - Added field types reference table - Added verification section </details> ## 🤖 Tessl Skill Review GitHub Action This PR also adds `.github/workflows/skill-review.yml` — a lightweight GitHub Action that automatically reviews skills on future PRs. <details> <summary>How it works and why it helps</summary> - **What runs:** On PRs that change `**/SKILL.md`, the workflow runs [`tesslio/skill-review`](https://github.com/tesslio/skill-review) and posts **one** comment with Tessl scores and feedback (updated on new pushes). - **Zero extra accounts:** Contributors do **not** need a Tessl login — only the default **`GITHUB_TOKEN`** is used to post the comment. - **Non-blocking by default:** The check is **feedback-only** — no surprise red CI. Add `fail-threshold: 70` later if you want a hard gate. - **Not a build replacement:** This is review automation for skill markdown only — it doesn't touch your docs build pipeline. - **Why only five skills edited here:** This PR caps manual optimization so it stays reviewable. After merge, **every PR that touches `SKILL.md`** gets automatic review comments, so the rest of the library improves incrementally. </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 🙏
|
@rohan-tessl is attempting to deploy a commit to the cartridge Team on Vercel. A member of the Team first needs to authorize it. |
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 👋 @kariy
I ran your skills through
tessl skill reviewat work and found some targeted improvements.Here's the full before/after:
This PR intentionally caps changes to five skills to keep it reviewable. The included GitHub Action workflow (see below) will surface Tessl feedback on future
SKILL.mdchanges automatically.Changes summary
dojo-vrf (0% → 90%)
dojo-review (66% → 100%)
dojo-system (66% → 94%)
dojo-world (71% → 100%)
dojo-model (74% → 86%)
🤖 Tessl Skill Review GitHub Action
This PR also adds
.github/workflows/skill-review.yml— a lightweight GitHub Action that automatically reviews skills on future PRs.How it works and why it helps
**/SKILL.md, the workflow runstesslio/skill-reviewand posts one comment with Tessl scores and feedback (updated on new pushes).GITHUB_TOKENis used to post the comment.fail-threshold: 70later if you want a hard gate.SKILL.mdgets automatic review comments, so the rest of the library improves incrementally.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 and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.
Thanks in advance 🙏