Skip to content

feat: improve skill descriptions and content across 121 skills#23

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

feat: improve skill descriptions and content across 121 skills#23
rohan-tessl wants to merge 1 commit intoalsk1992:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link

Hey @alsk1992 👋

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
acp 0% 96% +96%
ticks 0% 93% +93%
public 0% 75% +75%
features 30% 89% +59%
percolator 37% 94% +57%
token-security 30% 86% +56%
routing 36% 90% +54%
integrations 40% 90% +50%
ledger 37% 86% +49%
shield 35% 83% +48%

Average score: 53% → 87% (+34%) across all 121 skills

What changed
  • Added missing YAML frontmatter to 3 skills (acp, ticks, public) that were failing validation with 0% scores
  • Improved all 121 skill descriptions with concrete action verbs, domain-specific trigger terms, and "Use when..." routing clauses so agents can reliably select the right skill
  • Expanded thin skill content for 8 skills with very sparse docs (features, ledger, shield, token-security, meteora-dbc, meteora, orca, percolator) — added workflow sections, command examples, and reference tables
  • Standardized frontmatter format — all descriptions now use quoted strings, all names are kebab-case
  • Preserved all domain expertise — specialized terminology, command references, API details, and platform-specific knowledge untouched

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 @alsk1992 👋

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 |
|-------|--------|-------|--------|
| acp | 0% | 96% | +96% |
| ticks | 0% | 93% | +93% |
| public | 0% | 75% | +75% |
| features | 30% | 89% | +59% |
| percolator | 37% | 94% | +57% |
| token-security | 30% | 86% | +56% |
| routing | 36% | 90% | +54% |
| integrations | 40% | 90% | +50% |
| ledger | 37% | 86% | +49% |
| shield | 35% | 83% | +48% |

**Average score: 53% → 87% (+34%) across all 121 skills**

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

- Added missing YAML frontmatter to 3 skills (acp, ticks, public) that were failing validation with 0% scores
- Improved all 121 skill descriptions with concrete action verbs, domain-specific trigger terms, and "Use when..." routing clauses so agents can reliably select the right skill
- Expanded thin skill content for 8 skills with very sparse docs (features, ledger, shield, token-security, meteora-dbc, meteora, orca, percolator) — added workflow sections, command examples, and reference tables
- Standardized frontmatter format — all descriptions now use quoted strings, all names are kebab-case
- Preserved all domain expertise — specialized terminology, command references, API details, and platform-specific knowledge untouched

</details>

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