Skip to content

feat: improve skill review scores across 5 skills#1

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

feat: improve skill review scores across 5 skills#1
rohan-tessl wants to merge 2 commits into
kyopark2014:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl

@rohan-tessl rohan-tessl commented Mar 26, 2026

Copy link
Copy Markdown

Hey @kyopark2014 👋

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
notion 60% 96% +36%
skill-creator 76% 93% +17%
tavily-search 83% 100% +17%
book-search 89% 100% +11%
pdf 83% 90% +7%

This PR intentionally caps changes at 5 skills to keep it reviewable. The included workflow (below) will surface Tessl feedback on future SKILL.md changes so the rest of the library can improve incrementally.

Changes summary

notion (60% → 96%)

  • Expanded description with explicit "Use when" clause and natural trigger terms (Notion page, Notion database, add to Notion, etc.)
  • Removed unknown frontmatter key homepage
  • Added connection verification step in Setup
  • Consolidated "Get page" and "Get page content" into one section
  • Added troubleshooting table for common API errors (401, 403, 404, 429)

skill-creator (76% → 93%)

  • Expanded description with specific trigger terms (SKILL.md, skill template, package skill, agent capability, etc.)
  • Removed verbose "About Skills" and "What Skills Provide" introductory sections — the agent understands these concepts

tavily-search (83% → 100%)

  • Consolidated redundant script path warnings (was repeated 3 times, now stated once clearly)
  • Replaced verbose command-line options list with a compact table
  • Removed redundant "When to Use" section (already covered by description)
  • Removed "Examples" section that duplicated Quick Start
  • Removed troubleshooting section with obvious fixes
  • Condensed response format documentation

book-search (89% → 100%)

  • Removed "Features" section — capabilities are evident from examples
  • Removed "Implementation Notes" section — internal details unnecessary for usage
  • Moved script path warning above Quick Start for better visibility
  • Consolidated three separate usage examples into one compact block
  • Fixed Quick Start to use full path (was using relative cwd approach)

pdf (83% → 90%)

  • Consolidated Korean font registration code into a single reusable function (was repeated 3x with slight variations)
  • Moved Quick Reference table to top for immediate lookup
  • Removed verbose "Overview" section
  • Korean PDF examples now reference register_korean_font() instead of re-implementing the font logic
  • Consolidated font warnings into a concise list
  • Tightened pypdf examples (removed redundant variable assignments)

Tessl Skill Review GitHub Action

This PR also adds .github/workflows/skill-review.yml — a lightweight workflow that automatically reviews SKILL.md changes on future PRs:

  • What runs: On PRs that change **/SKILL.md, the workflow runs tesslio/skill-review and posts one comment with Tessl scores and feedback (updated on new pushes).
  • Zero extra accounts: Contributors do not need a Tessl login — only the default GITHUB_TOKEN is used to post the comment.
  • Non-blocking by default: The check is feedback-only with no surprise red CI. No fail-threshold is set unless you want a hard gate.
  • Not a build replacement: This is review automation for skill markdown, not a substitute for your own pipelines.
  • Optional gate: Add with: fail-threshold: 70 later if you want PRs to fail on low scores.
  • Why only 5 skills here: This PR caps manual optimization so it stays reviewable. After merge, every PR that touches SKILL.md gets automatic review comments, so the rest of the library can improve incrementally.

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 🙏

Optimized 5 SKILL.md files using tessl skill review:

| Skill         | Before | After | Change |
|---------------|--------|-------|--------|
| notion        | 60%    | 96%   | +36%   |
| skill-creator | 76%    | 93%   | +17%   |
| tavily-search | 83%    | 100%  | +17%   |
| book-search   | 89%    | 100%  | +11%   |
| pdf           | 83%    | 90%   | +7%    |

Key changes:
- notion: added "Use when" clause, trigger terms, verification step,
  troubleshooting table, removed unknown frontmatter key
- skill-creator: expanded description triggers, trimmed verbose intro
- tavily-search: consolidated redundant path warnings, compact options table
- book-search: removed unnecessary Features/Implementation Notes sections
- pdf: consolidated repeated Korean font code into single reusable function
Hey @hainamchung 👋

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 |
|-------|--------|-------|--------|
| agent-framework-azure-hosted-agents | 0% | 94% | +94% |
| agent-tool-builder | 7% | 96% | +89% |
| agent-memory-systems | 7% | 89% | +82% |
| agent-evaluation | 11% | 89% | +78% |
| advogado-especialista | 25% | 81% | +56% |

This PR intentionally caps changes at 5 skills to keep it reviewable. The included workflow (below) will surface Tessl feedback on future `SKILL.md` changes so the rest of the library can improve incrementally.

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

- **agent-framework-azure-hosted-agents (0% → 94%):** Fixed invalid frontmatter — the entire skill was wrapped in a ` ```skill ` code fence, causing validation to fail completely. Removed the wrapping fences and quoted the description string.
- **agent-tool-builder (7% → 96%):** Rewrote from a skeleton with persona-style description to a structured skill with clear workflow, JSON Schema design example, error handling patterns, and "Use when" trigger clause.
- **agent-memory-systems (7% → 89%):** Rewrote from placeholder content to a structured skill covering memory types (working, episodic, semantic, procedural), chunking strategies, retrieval patterns, and anti-patterns.
- **agent-evaluation (11% → 89%):** Rewrote from a skeleton to a complete evaluation framework skill with statistical testing patterns, behavioral contracts, evaluation types table, and anti-patterns.
- **advogado-especialista (25% → 81%):** Trimmed from 1,109 lines to ~90 lines by moving detailed legal modules (14 areas of Brazilian law) to `references/modulos.md` for progressive disclosure. Added proper "Use when" trigger clause with both Portuguese and English terms. Preserved all domain expertise in reference files.

</details>

## Tessl Skill Review GitHub Action

This PR also adds `.github/workflows/skill-review.yml` — a lightweight workflow that automatically reviews `SKILL.md` changes on future PRs:

- **What runs:** On PRs that change `**/SKILL.md`, the workflow runs [`tesslio/skill-review`](https://github.com/tesslio/skill-review) and posts **one** comment with Tessl scores and feedback (updated on new pushes).
- **Zero extra accounts:** Contributors do **not** need a Tessl login — only the default `GITHUB_TOKEN` is used to post the comment.
- **Non-blocking by default:** The check is feedback-only with no surprise red CI. No `fail-threshold` is set unless you want a hard gate.
- **Not a build replacement:** This is review automation for skill markdown, not a substitute for your own pipelines.
- **Optional gate:** Add `with: fail-threshold: 70` later if you want PRs to fail on low scores.
- **Why only 5 skills here:** This PR caps manual optimization so it stays reviewable. After merge, every PR that touches `SKILL.md` gets automatic review comments, so the rest of the 1,400+ skills can improve incrementally.

---

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 March 26, 2026 07:42
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