Skip to content

feat: improve hello-world skill score (47% → 90%)#123

Closed
yogesh-tessl wants to merge 1 commit into
github:mainfrom
yogesh-tessl:improve/skill-review-optimization
Closed

feat: improve hello-world skill score (47% → 90%)#123
yogesh-tessl wants to merge 1 commit into
github:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl
Copy link
Copy Markdown

@yogesh-tessl yogesh-tessl commented May 18, 2026

Hey @DanWahlin 👋

a hands-on Copilot CLI course at 2.5k stars that teaches skills through a real Python book collection app is a great learning design. The 4 sample skills (hello-world through pytest-gen) build up nicely in complexity, and mirroring them in both .github/skills/ and samples/ gives students both the working version and a reference to study.

ran your skills through tessl skill review at work and found some targeted improvements for the hello-world skill. Here's the before/after:

Skill Before After Change
hello-world 47% 90% +43%

I focused on hello-world since it had the most improvement headroom and is the first skill beginners encounter when learning the skills system, making it more actionable directly helps the onboarding experience.

Changes made to hello-world
  • Description: Replaced vague "minimal skill example" with specific actions (verify setup, demonstrate format) and added natural trigger terms (testing skills configuration, validating skill loading, creating a new skill template, how skills work)
  • Content: Replaced abstract "what it does" framing with concrete instructions (3-step workflow), a copy-paste response template showing exactly what output to produce, and expanded example prompts
  • Kept it minimal: The skill stays under 40 lines - still a "hello world" in spirit, just one that actually tells the agent what to do

Both .github/skills/ and samples/skills/ copies are updated to stay in sync.


quick 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.

If you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

Hey @DanWahlin 👋

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

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| hello-world | 47% | 90% | +43% |
| code-checklist | 69% | 69% | — |
| pytest-gen | 82% | 82% | — |
| commit-message | 96% | 96% | — |

I focused on `hello-world` since it had the most improvement headroom and is the first skill beginners encounter when learning the skills system — making it more actionable directly helps the onboarding experience.

<details>
<summary>Changes made to <code>hello-world</code></summary>

- **Description**: Replaced vague "minimal skill example" with specific actions (verify setup, demonstrate format) and added natural trigger terms (`testing skills configuration`, `validating skill loading`, `creating a new skill template`, `how skills work`)
- **Content**: Replaced abstract "what it does" framing with concrete instructions (3-step workflow), a copy-paste response template showing exactly what output to produce, and expanded example prompts
- **Kept it minimal**: The skill stays under 40 lines — still a "hello world" in spirit, just one that actually tells the agent what to do

Both `.github/skills/` and `samples/skills/` copies are updated to stay in sync.

</details>

I also stress-tested your `commit-message` skill against a few real-world task evals and it held up really well on multi-scope conventional commits with body formatting and footer references. Kudos for that.

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 🙏
@DanWahlin
Copy link
Copy Markdown
Collaborator

Thank you for the PR. This skill is kept intentionally simple so we’re not looking to change it right now. Thank you.

@DanWahlin DanWahlin closed this May 20, 2026
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.

2 participants