Skip to content

Improve/skill review optimization#1

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

Improve/skill review optimization#1
yogesh-tessl wants to merge 2 commits intoOrangeViolin:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl
Copy link
Copy Markdown

Hey @OrangeViolin 👋

'Good skills are summarised, not designed'. The observe → summarize → improve → verify loop with OTF/JIT/Bootstrap mechanics is a disciplined methodology for skill evolution. Each round's notes becoming fuel for the next round is an elegant self-reinforcing cycle. 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 summary

Description (90% → 100%)

  • Added concrete action verbs (观察输出、提炼错误模式、针对性重写指令、验证改进效果) so the description specifies how the evolutionary methodology works, not just that it improves skills
  • Converted description to quoted string format per frontmatter best practices

Content (77% → 85%)

  • Trimmed motivational/philosophical text that Claude doesn't need (blockquote philosophy, "不要追求完美" paragraph, "这是最关键的一步" preambles) - improves conciseness without losing actionable guidance
  • Extracted Bootstrap compression details and special scenarios (quick mode, skill-creator handoff, non-convergence troubleshooting) into references/bootstrap.md and references/special-scenarios.md - keeps the core workflow focused while preserving all content one link away

Domain preservation: All OTF/JIT/Bootstrap methodology concepts, Chinese trigger terms, directory structures, and convergence table retained as-is.

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 @OrangeViolin 👋

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-evolve | 86% | 94% | +8% |

![Score Card](score_card.png)

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

**Description (90% → 100%)**
- Added concrete action verbs (观察输出、提炼错误模式、针对性重写指令、验证改进效果) so the description specifies *how* the evolutionary methodology works, not just that it improves skills
- Converted description to quoted string format per frontmatter best practices

**Content (77% → 85%)**
- Trimmed motivational/philosophical text that Claude doesn't need (blockquote philosophy, "不要追求完美" paragraph, "这是最关键的一步" preambles) — improves conciseness without losing actionable guidance
- Extracted Bootstrap compression details and special scenarios (quick mode, skill-creator handoff, non-convergence troubleshooting) into `references/bootstrap.md` and `references/special-scenarios.md` — keeps the core workflow focused while preserving all content one link away

**Domain preservation**: All OTF/JIT/Bootstrap methodology concepts, Chinese trigger terms, directory structures, and convergence table retained as-is.

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