Skip to content

feat: improve skill scores for roopik#84

Open
yogesh-tessl wants to merge 1 commit intoRoopikLabs:developfrom
yogesh-tessl:improve/skill-review-optimization
Open

feat: improve skill scores for roopik#84
yogesh-tessl wants to merge 1 commit intoRoopikLabs:developfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl
Copy link
Copy Markdown

Hey @HumbleBee14 👋

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
accessibility 87% 94% +7%
fix-errors 90% 100% +10%
unit-tests 89% 95% +6%
integration-tests 90% 100% +10%
memory-leak-audit 97% 97%
What changed

accessibility (+7%)

  • Narrowed the Use when trigger clause to explicitly mention accessibility context (ARIA, screen readers, keyboard navigation) - prevents false activation on general UI work
  • Removed duplicate import lines in the help dialog code example
  • Trimmed sections 6–7 (keyboard navigation, ARIA labels) to VS Code-specific guidance only - general WAI-ARIA knowledge Claude already has
  • Moved advanced IInstantiationService pattern to a separate EXAMPLES.md for progressive disclosure

fix-errors (+10%)

  • Tightened the "do NOT fix at the crash site" section - same message, fewer words
  • Condensed the data flow tracing guidance for better conciseness

unit-tests (+6%)

  • Moved compilation prerequisite to the top so it's seen before any test commands
  • Consolidated the duplicate "bare file paths" and --run sections into one
  • Replaced the vague "conceptual example" for runTests with a concrete tool invocation showing exact parameters
  • Removed redundant compilation section at the bottom

integration-tests (+10%)

  • Removed the Examples section that duplicated commands already shown under each option
  • Cross-referenced the unit-tests skill in the "Distinction from unit tests" section instead of re-explaining

I kept this PR focused on the 4 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 @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 - @yogesh-tessl - if you hit any snags.

Thanks in advance 🙏

Hey @HumbleBee14 👋

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 |
|-------|--------|-------|--------|
| accessibility | 87% | 94% | +7% |
| fix-errors | 90% | 100% | +10% |
| unit-tests | 89% | 95% | +6% |
| integration-tests | 90% | 100% | +10% |
| memory-leak-audit | 97% | 97% | — |

<details>
<summary>What changed</summary>

**accessibility** (+7%)
- Narrowed the `Use when` trigger clause to explicitly mention accessibility context (ARIA, screen readers, keyboard navigation) — prevents false activation on general UI work
- Removed duplicate import lines in the help dialog code example
- Trimmed sections 6–7 (keyboard navigation, ARIA labels) to VS Code-specific guidance only — general WAI-ARIA knowledge Claude already has
- Moved advanced `IInstantiationService` pattern to a separate EXAMPLES.md for progressive disclosure

**fix-errors** (+10%)
- Tightened the "do NOT fix at the crash site" section — same message, fewer words
- Condensed the data flow tracing guidance for better conciseness

**unit-tests** (+6%)
- Moved compilation prerequisite to the top so it's seen before any test commands
- Consolidated the duplicate "bare file paths" and `--run` sections into one
- Replaced the vague "conceptual example" for `runTests` with a concrete tool invocation showing exact parameters
- Removed redundant compilation section at the bottom

**integration-tests** (+10%)
- Removed the Examples section that duplicated commands already shown under each option
- Cross-referenced the `unit-tests` skill in the "Distinction from unit tests" section instead of re-explaining

</details>

I kept this PR focused on the 4 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 @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