Skip to content

feat: improve skill review scores for 5 lowest-scoring skills#98

Open
rohan-tessl wants to merge 1 commit into
doodledood:mainfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: improve skill review scores for 5 lowest-scoring skills#98
rohan-tessl wants to merge 1 commit into
doodledood:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

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

Hey @doodledood 👋

I ran your skills through tessl skill review at work and found some targeted improvements.

image

Here's the full before/after:

Skill Before After Change
clean-slop 38% 89% +51%
investigate-bug 36% 74% +38%
audit-ux 39% 74% +35%
review-prompt 38% 69% +31%
update-claude-md 18% 18% +0%*

*update-claude-md contains the reserved word "claude" in its name, which causes the tessl validator to fail deterministically and skip the LLM judge entirely. The content improvements are genuine (expanded description with "Use when..." clause, structured best-practices sections, verification checklist) but the score can't reflect them. You may want to consider renaming (e.g. update-project-instructions) or accept the validation trade-off — totally your call.

This PR is intentionally scoped to the 5 lowest-scoring skills. More skills can be improved in follow-ups or via automated review on future PRs.

Changes summary

All 5 skills received:

  • Expanded frontmatter descriptions with specific concrete actions and explicit "Use when..." trigger clauses
  • Removed unknown context: fork frontmatter keys (caused validation warnings on 3 skills)

investigate-bug: Added structured workflow (gather symptoms → identify scope → invoke consultant → relay findings), expected output format with root cause, execution flow, blast radius, and regression test plan sections.

review-prompt: Added 10-Layer Architecture reference table, structured output description (assessment, score, strengths, issues table with AUTO_FIXABLE/NEEDS_USER_INPUT tags), clarified read-only constraint.

clean-slop: Added four concrete slop categories with examples (useless comments, verbose docs, filler phrases, unnecessary patterns), scope rules (file paths vs git diff), decision rule for remove/keep, and output format description.

audit-ux: Added 4-step workflow (gather references → identify changes → systematic review → report findings), five issue categories with specific examples, and structured output format description.

update-claude-md: Restructured best practices into scannable sections (structure, length budget table, progressive disclosure, do/don't lists, examples), added verification checklist.

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

Thanks in advance 🙏

Hey @doodledood 👋

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 |
|-------|--------|-------|--------|
| clean-slop | 38% | 89% | +51% |
| investigate-bug | 36% | 74% | +38% |
| audit-ux | 39% | 74% | +35% |
| review-prompt | 38% | 69% | +31% |
| update-claude-md | 18% | 18% | +0%* |

*`update-claude-md` contains the reserved word "claude" in its name, which causes
the tessl validator to fail deterministically and skip the LLM judge entirely.
The content improvements are genuine but the score can't reflect them.

This PR is intentionally scoped to the 5 lowest-scoring skills. More skills can
be improved in follow-ups or via automated review on future PRs.

Changes:
- Expanded frontmatter descriptions with "Use when..." trigger clauses
- Removed unknown `context: fork` frontmatter keys (3 skills)
- investigate-bug: structured workflow, expected output format
- review-prompt: 10-Layer Architecture table, output description
- clean-slop: slop categories, scope rules, decision rule
- audit-ux: 4-step workflow, issue categories, output format
- update-claude-md: restructured best practices, verification checklist
@rohan-tessl rohan-tessl marked this pull request as ready for review April 2, 2026 07:59
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