Skip to content

feat: improve SKILL.md quality 45% → 90% + add Tessl skill review action#2

Open
rohan-tessl wants to merge 2 commits into0xAstroAlpha:mainfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: improve SKILL.md quality 45% → 90% + add Tessl skill review action#2
rohan-tessl wants to merge 2 commits into0xAstroAlpha:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

Hey @0xAstroAlpha 👋

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
office-design-toolkit 45% 90% +45%

This PR covers your 1 skill in the repo.

What changed in office-design-toolkit
  • Description rewritten with concrete action verbs, an explicit "Use when..." clause, and natural trigger terms covering all four file types (DOCX, PPTX, XLSX, PDF)
  • SKILL.md reduced from 1,004 → ~354 lines (65% reduction) — heavy inline content moved to reference files
  • New reference files added: references/pptx-design-guide.md (PPTX color palettes, typography, layouts) and references/design-skills-reference.md (10-theme table, canvas fonts, design philosophy)
  • Progressive disclosure applied: SKILL.md gives actionable quick-start content inline and points to reference files for details
  • Removed duplicated content (full 10-theme definitions, Vietnamese section headers, sprint status metadata)

Tessl Skill Review GitHub Action ✅

I've also included a GitHub Action (.github/workflows/skill-review.yml) that automatically reviews any SKILL.md changed in future PRs and posts scores as a PR comment.

What this gives you:

  • 🔍 Automatic tessl skill review runs on every PR touching SKILL.md
  • 💬 One updated PR comment with scores and improvement feedback
  • 🔓 Zero extra accounts — contributors don't need a Tessl login; only GITHUB_TOKEN is used
  • Non-blocking by default — feedback-only, no surprise red CI (add fail-threshold: 70 later if you want a hard gate)
  • 📈 Covers future skills incrementally as contributors edit them

Want automatic AI optimization on every SKILL.md change? 🚀

The action I've added gives you review scores on PRs. We also have a more powerful variant — tesslio/skill-review-and-optimize — that can:

  • Run AI-powered optimization suggestions on every SKILL.md PR (requires adding TESSL_API_TOKEN as a repo secret)
  • Let contributors accept suggested improvements by commenting /apply-optimize
  • Still works in review-only mode with zero secrets

Interested? Tick the box and I'll raise a follow-up PR:

  • Yes please! Add the tesslio/skill-review-and-optimize action so every SKILL.md PR gets AI optimization suggestions + the /apply-optimize flow
  • No thanks — the review scores action is enough for now

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 🙏

Ran tessl skill review and found targeted improvements to the skill.

Before/After:
| Skill | Before | After | Change |
|-------|--------|-------|--------|
| office-design-toolkit | 45% | 90% | +45% |

Changes:
- Rewrote frontmatter description with action verbs, 'Use when...' clause,
  and natural trigger terms (create/edit DOCX, PPTX, XLSX, PDF)
- Reduced SKILL.md from 1004 → ~354 lines (65% reduction)
- Moved heavy content (theme definitions, palettes, fonts) to references/
- Added progressive disclosure: concise overview → reference files for details
- Split pptx-design-guide.md and design-skills-reference.md as new references
Adds tesslio/skill-review GitHub Action that runs on any PR touching
SKILL.md and posts a score comment — no Tessl account needed for contributors,
only GITHUB_TOKEN.

Optional: add 'fail-threshold: 70' to gate PRs on score quality.
@rohan-tessl rohan-tessl marked this pull request as ready for review April 14, 2026 08:10
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