Skip to content

feat: improve skill review scores for 5 skills#9

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

feat: improve skill review scores for 5 skills#9
rohan-tessl wants to merge 1 commit intojaktestowac:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

Hey @jaktestowac πŸ‘‹

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
prd-generator 47% 90% +43%
tech-debt-analysis (plugin) 61% 90% +29%
code-review 67% 90% +23%
designing-test-data 77% 93% +16%
creating-prompts 77% 87% +10%

This PR intentionally covers 5 of 20 skills to keep the contribution focused and reviewable β€” more can be improved in follow-ups or via automated review on future PRs.

Changes summary

prd-generator (47% β†’ 90%)

  • Rewrote frontmatter description as a quoted string with explicit "Use when" triggers
  • Added argument-hint and user-invocable fields
  • Stripped all emoji from headings
  • Condensed from ~302 lines to ~133 lines β€” removed explanatory text, tightened phases, compacted PRD output schema into a numbered reference
  • Added operating principles and common failure modes sections
  • Preserved all domain expertise (strategy classification, structured discovery, AI/ML requirements, stakeholder alignment)

tech-debt-analysis (plugin) (61% β†’ 90%)

  • Rewrote description with "Use when" triggers and natural search terms
  • Added argument-hint and user-invocable fields
  • Removed emoji from headings, condensed from ~234 to ~138 lines
  • Compacted output schema while keeping all 6 report sections
  • Added a concrete inline debt item example (TD-042 payment test flakiness)
  • Merged self-review and quality rules into tight sections

code-review (67% β†’ 90%)

  • Replaced generic description with trigger-specific text mentioning PRs, diffs, and merge sign-off
  • Added argument-hint and user-invocable fields
  • Removed "Prompt Pattern" section (agent identity anti-pattern)
  • Added 4-phase workflow: Scope β†’ Review β†’ Categorize β†’ Verdict
  • Added concrete inline example showing a null-check finding with before/after TypeScript

creating-prompts (77% β†’ 87%)

  • Made description more action-specific with concrete trigger phrases
  • Added inline .prompt.md example after Phase 3 (complements existing resource files)
  • Compacted Phase 2 frontmatter guidance
  • Added two new trigger phrases to "When to Use"

designing-test-data (77% β†’ 93%)

  • Expanded description with granular actions and natural trigger synonyms (mock data, sample data, dummy records)
  • Added concrete User Registration data pack example table
  • Inlined minimal test data catalog template structure
  • Consolidated failure modes into design rules
  • Action-verb "When to Use" bullets

Want your remaining skills optimised too? πŸš€

This PR covers 5 of your 20 skills to keep the contribution focused and reviewable. We have tooling that can go further:

  • Optimize remaining 15 skills automatically (same AI-powered pass as above)
  • Add a GitHub Action β€” tesslio/skill-review-and-optimize β€” that automatically reviews (and optionally optimizes) any SKILL.md changed in future PRs. Review mode works with zero secrets; maintainers can add TESSL_API_TOKEN for AI suggestions and the /apply-optimize comment flow.

Interested? Just tick the box below and we'll raise a follow-up PR:

  • Yes please! Raise a follow-up PR: optimize the remaining 15 skills + add the Tessl skill-review-and-optimize GitHub Action
  • No thanks β€” happy with the 5 skills in this PR

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 @jaktestowac πŸ‘‹

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 |
|-------|--------|-------|--------|
| prd-generator | 47% | 90% | +43% |
| tech-debt-analysis (plugin) | 61% | 90% | +29% |
| code-review | 67% | 90% | +23% |
| designing-test-data | 77% | 93% | +16% |
| creating-prompts | 77% | 87% | +10% |

This PR intentionally covers 5 of 20 skills to keep the contribution focused and reviewable β€” more can be improved in follow-ups or via automated review on future PRs.

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

**prd-generator** (47% β†’ 90%)
- Rewrote frontmatter description as a quoted string with explicit "Use when" triggers
- Added `argument-hint` and `user-invocable` fields
- Stripped all emoji from headings
- Condensed from ~302 lines to ~133 lines β€” removed explanatory text, tightened phases, compacted PRD output schema into a numbered reference
- Added operating principles and common failure modes sections
- Preserved all domain expertise (strategy classification, structured discovery, AI/ML requirements, stakeholder alignment)

**tech-debt-analysis (plugin)** (61% β†’ 90%)
- Rewrote description with "Use when" triggers and natural search terms
- Added `argument-hint` and `user-invocable` fields
- Removed emoji from headings, condensed from ~234 to ~138 lines
- Compacted output schema while keeping all 6 report sections
- Added a concrete inline debt item example (TD-042 payment test flakiness)
- Merged self-review and quality rules into tight sections

**code-review** (67% β†’ 90%)
- Replaced generic description with trigger-specific text mentioning PRs, diffs, and merge sign-off
- Added `argument-hint` and `user-invocable` fields
- Removed "Prompt Pattern" section (agent identity anti-pattern)
- Added 4-phase workflow: Scope β†’ Review β†’ Categorize β†’ Verdict
- Added concrete inline example showing a null-check finding with before/after TypeScript

**creating-prompts** (77% β†’ 87%)
- Made description more action-specific with concrete trigger phrases
- Added inline `.prompt.md` example after Phase 3 (complements existing resource files)
- Compacted Phase 2 frontmatter guidance
- Added two new trigger phrases to "When to Use"

**designing-test-data** (77% β†’ 93%)
- Expanded description with granular actions and natural trigger synonyms (mock data, sample data, dummy records)
- Added concrete User Registration data pack example table
- Inlined minimal test data catalog template structure
- Consolidated failure modes into design rules
- Action-verb "When to Use" bullets

</details>

## Want your remaining skills optimised too? πŸš€

This PR covers **5 of your 20 skills** to keep the contribution focused and reviewable. We have tooling that can go further:

- **Optimize remaining 15 skills** automatically (same AI-powered pass as above)
- **Add a GitHub Action** β€” [tesslio/skill-review-and-optimize](https://github.com/tesslio/skill-review-and-optimize) β€” that automatically reviews (and optionally optimizes) any `SKILL.md` changed in future PRs. Review mode works with zero secrets; maintainers can add `TESSL_API_TOKEN` for AI suggestions and the `/apply-optimize` comment flow.

Interested? Just tick the box below and we'll raise a follow-up PR:

- [ ] **Yes please!** Raise a follow-up PR: optimize the remaining 15 skills + add the Tessl skill-review-and-optimize GitHub Action
- [ ] **No thanks** β€” happy with the 5 skills in this PR

---

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 - [@rohan-tessl](https://github.com/rohan-tessl) - if you hit any snags.

Thanks in advance πŸ™
@rohan-tessl rohan-tessl marked this pull request as ready for review April 20, 2026 09:49
@Freudenberger Freudenberger self-assigned this Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants