Improve/skill review optimization#180
Open
yogesh-tessl wants to merge 2 commits intoReScienceLab:mainfrom
Open
Improve/skill review optimization#180yogesh-tessl wants to merge 2 commits intoReScienceLab:mainfrom
yogesh-tessl wants to merge 2 commits intoReScienceLab:mainfrom
Conversation
## What Hey @Jing-yilin 👋 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 | |-------|--------|-------|--------| | awn | 59% | 94% | +35% | | archive | 90% | 97% | +7% | | seo-geo | 94% | 94% | 0% | | twitter | 92% | 92% | 0% | | reddit | 97% | 97% | 0% (unchanged) | ## Why The `awn` skill scored 59% because it was missing a "Use when..." trigger clause and had no getting-started workflow — agents couldn't reliably select it or follow a sequenced onboarding path. The other skills were already strong but had minor gaps flagged by the review. ## How <details> <summary>Changes made</summary> **awn (59% → 94%, +35%)** - Rewrote description to include explicit "Use when..." trigger clause with natural user phrases (send messages, peer-to-peer, join worlds, discover agents) - Added numbered "Getting Started" workflow (start daemon → verify → discover → join → send) with validation steps - Consolidated duplicate Usage section and Quick Reference table into a single "Command Reference" table - Removed redundant Architecture diagram and verbose per-command sections to reduce token cost - Kept World Actions, Data Directory, Configuration, Error Handling, and Rules sections intact **archive (90% → 97%, +7%)** - Added inline example of a complete archive entry with YAML frontmatter (tags, category, related fields) so agents can execute without reading references/TEMPLATE.md first - Added sample MEMORY.md entry showing the expected one-line format **seo-geo (94% → 94%)** - Removed verbose "Use this for" annotations and separator lines after each audit command — agents infer usage from context - Consolidated Quick Reference intro paragraph and Key Insight callout into the workflow directly **twitter (92% → 92%)** - Added Error Handling table covering 401/429 errors and empty responses with specific fixes </details> I kept this PR focused on the 3 skills with the biggest improvements to keep the diff reviewable. Happy to follow up with the rest in a separate PR if you'd like. ## Checklist - [x] `npm run build` succeeds (no build files changed) - [x] `node --test test/*.test.mjs` passes (no test files changed) - [ ] New tests added for new functionality — N/A (skill docs only) - [x] No secrets or sensitive data in the diff - [x] Commit message follows conventional commits (`feat:`, `fix:`, etc.) --- 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 @Jing-yilin 👋
The Agent World Network protocol for connecting AI agents through shared worlds is an ambitious multi-agent coordination layer and the star-office-world pixel-art dashboard built on top of it shows you're not just designing specs but shipping tangible implementations. Nice to see the AWN gateway, signed peer protocol, and append-only ledger approach. 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:Changes made
awn (59% → 94%, +35%)
archive (90% → 97%, +7%)
seo-geo (94% → 94%)
twitter (92% → 92%)
I kept this PR focused on the 3 skills with the biggest improvements to keep the diff reviewable. Happy to follow up with the rest in a separate PR if you'd like.
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 🙏