Skip to content

Improve/skill review optimization#4

Open
yogesh-tessl wants to merge 2 commits into
jzOcb:mainfrom
yogesh-tessl:improve/skill-review-optimization
Open

Improve/skill review optimization#4
yogesh-tessl wants to merge 2 commits into
jzOcb:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl
Copy link
Copy Markdown

Hey 👋 @jzOcb

"Prompts are suggestions. Code is law." is a great tagline, and the table of real incidents (model name dots-vs-hyphens, missing browser.profiles.color, silently wiped Telegram channels) makes the case for the skill better than any abstract pitch could. The auto-rollback after a 30s gateway health check is the right safety net. Wanted to suggest a few improvements to the SKILL.md.

I ran your skills through tessl skill review at work and found some targeted improvements. Here's the full before/after:

score_card
Changes made
  • Removed storytelling sections ("The Problem" incident table, "Why This Matters" anecdote, "Philosophy") that consumed tokens without adding actionable guidance
  • Consolidated real failure modes into a concise bullet list at the top - keeps the safety context without the narrative
  • Extracted the full "Checks Performed" validation table into a new CHECKS.md reference file for progressive disclosure
  • Added a link from SKILL.md to CHECKS.md so the detail is still accessible when needed
  • Tightened the intro to lead with what the skill does rather than background motivation
  • Kept all executable commands, mandatory workflow, and critical warnings intact

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 🙏

Hey 👋 @jzOcb

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after:

![Skill Review Score Card](score_card.png)

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| config-guard | 83% | 92% | +9% |

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

- Removed storytelling sections ("The Problem" incident table, "Why This Matters" anecdote, "Philosophy") that consumed tokens without adding actionable guidance
- Consolidated real failure modes into a concise bullet list at the top — keeps the safety context without the narrative
- Extracted the full "Checks Performed" validation table into a new `CHECKS.md` reference file for progressive disclosure
- Added a link from SKILL.md to CHECKS.md so the detail is still accessible when needed
- Tightened the intro to lead with what the skill does rather than background motivation
- Kept all executable commands, mandatory workflow, and critical warnings intact

</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 🙏
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