Skip to content

feat: improve skill scores for Personal_AI_Infrastructure#975

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

feat: improve skill scores for Personal_AI_Infrastructure#975
rohan-tessl wants to merge 1 commit intodanielmiessler:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link

Hey @danielmiessler 👋

I ran your skills through tessl skill review at work and found some targeted improvements. Here's the full before/after:

image

Here's the full before/after:

Skill Before After Change
utilities 0% 91% +91%
security/recon 68% 93% +25%
utilities/create-cli 68% 93% +25%
security/prompt-injection 71% 93% +22%
utilities/pai-upgrade 59% 80% +21%
security/sec-updates 70% 88% +18%
utilities/aphorisms 68% 86% +18%
content-analysis 64% 81% +17%
investigation 64% 81% +17%
thinking 74% 91% +17%
scraping 74% 88% +14%
thinking/council 74% 88% +14%
utilities/evals 81% 95% +14%
security 83% 96% +13%
utilities/documents/pdf 75% 86% +11%
utilities/prompting 81% 89% +8%
research 76% 84% +8%
utilities/parser 75% 83% +8%
media 79% 86% +7%
telos 70% 77% +7%
investigation/private-investigator 79% 85% +6%
utilities/documents 81% 83% +2%
thinking/science 72% 74% +2%
thinking/be-creative 76% 77% +1%

Note: All 48 skill names were converted from PascalCase to kebab-case (e.g. Agents → agents, ExtractWisdom → extract-wisdom) to pass validation. The "before" scores shown above are after the name fix — original scores were 0% across the board due to the name format failing validation.

Changes summary

Across all improved skills:

  • Converted all 48 skill names from PascalCase to kebab-case to pass tessl skill review validation
  • Removed verbose voice notification boilerplate (condensed to single-line curl commands)
  • Removed redundant "When to Activate" sections (triggers already covered by frontmatter descriptions)
  • Consolidated duplicate routing/trigger tables into single unified tables
  • Added validation checkpoints where workflows lacked them
  • Removed unnecessary ASCII art diagrams, version history, and philosophy sections
  • Trimmed utilities description from 2004 chars to under 1024 to pass validation

Largest improvements:

  • security/recon: Cut from 514 to ~110 lines (78% reduction)
  • utilities/create-cli: Cut from 352 to ~100 lines (72% reduction)
  • security/prompt-injection: Consolidated verbose authorization sections
  • utilities/pai-upgrade: Cut from 493 to ~145 lines (70% reduction)
  • utilities/aphorisms: Cut from 370 to ~85 lines (77% reduction)
  • utilities/prompting: Added missing workflow section and completed Core Components listing
  • utilities/documents: Removed redundant Document Type Details section

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

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 |
|-------|--------|-------|--------|
| utilities | 0% | 91% | +91% |
| security/recon | 68% | 93% | +25% |
| utilities/create-cli | 68% | 93% | +25% |
| security/prompt-injection | 71% | 93% | +22% |
| utilities/pai-upgrade | 59% | 80% | +21% |
| security/sec-updates | 70% | 88% | +18% |
| utilities/aphorisms | 68% | 86% | +18% |
| content-analysis | 64% | 81% | +17% |
| investigation | 64% | 81% | +17% |
| thinking | 74% | 91% | +17% |
| scraping | 74% | 88% | +14% |
| thinking/council | 74% | 88% | +14% |
| utilities/evals | 81% | 95% | +14% |
| security | 83% | 96% | +13% |
| utilities/documents/pdf | 75% | 86% | +11% |
| utilities/prompting | 81% | 89% | +8% |
| research | 76% | 84% | +8% |
| utilities/parser | 75% | 83% | +8% |
| media | 79% | 86% | +7% |
| telos | 70% | 77% | +7% |
| investigation/private-investigator | 79% | 85% | +6% |
| agents | 81% | 84% | +3% |
| utilities/documents | 81% | 83% | +2% |
| thinking/science | 72% | 74% | +2% |
| thinking/be-creative | 76% | 77% | +1% |

Note: All 48 skill names were converted from PascalCase to kebab-case (e.g.
Agents → agents, ExtractWisdom → extract-wisdom) to pass validation. The
"before" scores shown above are after the name fix — original scores were 0%
across the board due to the name format failing validation.

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

Across all improved skills:
- Converted all 48 skill names from PascalCase to kebab-case to pass
  tessl skill review validation
- Removed verbose voice notification boilerplate (condensed to single-line
  curl commands)
- Removed redundant "When to Activate" sections (triggers already covered
  by frontmatter descriptions)
- Consolidated duplicate routing/trigger tables into single unified tables
- Added validation checkpoints where workflows lacked them
- Removed unnecessary ASCII art diagrams, version history, and philosophy
  sections
- Trimmed utilities description from 2004 chars to under 1024 to pass
  validation

Largest improvements:
- security/recon: Cut from 514 to ~110 lines (78% reduction)
- utilities/create-cli: Cut from 352 to ~100 lines (72% reduction)
- security/prompt-injection: Consolidated verbose authorization sections
- utilities/pai-upgrade: Cut from 493 to ~145 lines (70% reduction)
- utilities/aphorisms: Cut from 370 to ~85 lines (77% reduction)
- utilities/prompting: Added missing workflow section and completed
  Core Components listing
- utilities/documents: Removed redundant Document Type Details section

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