Skip to content

feat: optimize skill-dev skill (86% → 90%)#2

Open
rohan-tessl wants to merge 1 commit into
hao-cyber:masterfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: optimize skill-dev skill (86% → 90%)#2
rohan-tessl wants to merge 1 commit into
hao-cyber:masterfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

@rohan-tessl rohan-tessl commented Apr 24, 2026

Hullo 👋 @hao-cyber

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-dev 86% 90% +4%

Score Card

Changes made
  • Added explicit lifecycle flow with numbered stages and validation gates (create → use → reflect → evaluate → maturity check → publish), with fail-loop-back mechanism
  • Added concrete examples to Degrees of Freedom — replaced abstract descriptions with specific examples at each freedom level (e.g., sys.exit(1) for low freedom)
  • Added Quick Example section showing a real reflect → evaluate → publish workflow with executable commands (grep, run_eval.py, publish.py)
  • Removed redundant "Concise is Key" subsection — its guidance overlapped with Writing Guidelines
  • Tightened Writing Guidelines — consolidated into four crisp bullets with a litmus test

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 - @popey - if you hit any snags.

Thanks in advance 🙏

Hullo 👋 @hao-cyber

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-dev | 86% | 90% | +4% |

<details>
<summary>Changes made</summary>

- **Added explicit lifecycle flow** with numbered stages and validation gates (create → use → reflect → evaluate → maturity check → publish), with fail-loop-back mechanism
- **Added concrete examples to Degrees of Freedom** — replaced abstract descriptions with specific examples at each freedom level (e.g., `sys.exit(1)` for low freedom)
- **Added Quick Example section** showing a real reflect → evaluate → publish workflow with executable commands (`grep`, `run_eval.py`, `publish.py`)
- **Removed redundant "Concise is Key" subsection** — its guidance overlapped with Writing Guidelines
- **Tightened Writing Guidelines** — consolidated into four crisp bullets with a litmus test

</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 - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@rohan-tessl rohan-tessl marked this pull request as ready for review April 24, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant