Skip to content

feat: improve skill scores across 17 skills - #1

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

feat: improve skill scores across 17 skills#1
rohan-tessl wants to merge 1 commit into
rohunj:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl

Copy link
Copy Markdown

Hey @rohunj 👋

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
frontend-design 59% 96% +37%
react-best-practices 77% 100% +23%
pdf 79% 94% +15%
prd 84% 96% +12%
docx 85% 93% +8%
sast-semgrep 86% 93% +7%
web-design-guidelines 81% 86% +5%
edge-cases 84% 89% +5%
sca-trivy 89% 93% +4%
bugs-to-stories 84% 85% +1%
compound-engineering 80% 81% +1%
agent-browser 94% 94%
story-quality 89% 89%
test-and-break 89% 89%

Changes summary:

Across all skills:

  • Standardized frontmatter descriptions to quoted strings with third-person voice and explicit "Use when..." clauses
  • Expanded trigger terms to include natural language variations users would actually say

frontend-design (+37%):

  • Added concrete CSS code examples (font pairing, color palette, staggered animations)
  • Added structured 4-step workflow with validation checklist
  • Removed motivational language, added responsive layout and accessibility sections

react-best-practices (+23%):

  • Added 3 inline code examples for highest-impact rules
  • Added 6-step optimization workflow and validation checkpoint

pdf (+15%):

  • Added validation steps after every critical operation
  • Consolidated redundant CLI examples, trimmed verbosity

prd (+12%):

  • Listed concrete PRD components in description
  • Removed meta-section, condensed example PRD

docx (+8%), sast-semgrep (+7%), web-design-guidelines (+5%), edge-cases (+5%):

  • Description improvements, trigger terms, removed unnecessary sections
  • Added validation steps and error handling guidance

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 — if you hit any snags.

Thanks in advance 🙏

Hey @rohunj 👋

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 |
|-------|--------|-------|--------|
| frontend-design | 59% | 96% | +37% |
| react-best-practices | 77% | 100% | +23% |
| pdf | 79% | 94% | +15% |
| prd | 84% | 96% | +12% |
| docx | 85% | 93% | +8% |
| sast-semgrep | 86% | 93% | +7% |
| web-design-guidelines | 81% | 86% | +5% |
| edge-cases | 84% | 89% | +5% |
| sca-trivy | 89% | 93% | +4% |
| bugs-to-stories | 84% | 85% | +1% |
| compound-engineering | 80% | 81% | +1% |
| agent-browser | 94% | 94% | — |
| story-quality | 89% | 89% | — |
| test-and-break | 89% | 89% | — |

Changes summary:

Across all skills:
- Standardized frontmatter descriptions to quoted strings with third-person voice and explicit "Use when..." clauses
- Expanded trigger terms to include natural language variations users would actually say

frontend-design (+37%):
- Added concrete CSS code examples (font pairing, color palette, staggered animations)
- Added structured 4-step workflow with validation checklist
- Removed motivational language, added responsive layout and accessibility sections

react-best-practices (+23%):
- Added 3 inline code examples for highest-impact rules
- Added 6-step optimization workflow and validation checkpoint

pdf (+15%):
- Added validation steps after every critical operation
- Consolidated redundant CLI examples, trimmed verbosity

prd (+12%):
- Listed concrete PRD components in description
- Removed meta-section, condensed example PRD

docx (+8%), sast-semgrep (+7%), web-design-guidelines (+5%), edge-cases (+5%):
- Description improvements, trigger terms, removed unnecessary sections
- Added validation steps and error handling guidance

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