Skip to content

Improve/skill review optimization - #1

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

Improve/skill review optimization#1
yogesh-tessl wants to merge 2 commits into
ozrwayne:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl

Copy link
Copy Markdown

Hey @rolandwonglonam 👋

Solving the WeChat duplicate file problem with content hashing instead of filename matching is the right approach. Anyone who's had their storage eaten by document(1).pdf through document(7).pdf knows the pain. The bilingual SKILL.md with Chinese trigger words, is a nice touch for the actual user base. Wanted to suggest some improvements to the SKILL.md

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

score_card
Changes made

Frontmatter (required for skill validation):

  • Added YAML frontmatter with name: wechat-dedup and a detailed description field
  • Added explicit "Use when..." clause with natural trigger terms (find duplicates, clean up WeChat folders, deduplicate PDF/Word files, free up storage)

Description improvements (100%, up from 83%):

  • Expanded description to cover the two-phase fingerprinting approach and quarantine safety mechanism
  • Added "Use when..." clause covering three common user scenarios (+1 completeness dimension)

Content improvements (77%, up from 35%):

  • Replaced generic feature description and trigger words section with a concrete 7-step workflow including an explicit user confirmation checkpoint before file moves
  • Added executable Python code example showing the core find_duplicates() two-phase algorithm with inline comments
  • Added error handling section documenting behavior for missing paths, permission errors, and quarantine directory failures
  • Removed redundant trigger words section and technical implementation library list (not actionable for Claude)
  • Consolidated safety mechanisms into a focused section with clear guarantees

Honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

I also added a lightweight GitHub Action that auto-reviews any skill.md changed in a PR (includes min permissions, uses a pinned action version, only posts a review comment).

This means that it gives you and your contributors an instant quality signal before you have to review yourself (no signup, no tokens needed).

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 - @yogesh-tessl (https://github.com/yogesh-tessl) - if you hit any snags.

Thanks in advance 🙏

Hey @rolandwonglonam 👋

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

![score_card](score_card.png)

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| wechat-dedup | 67% | 90% | +23% |

> **Note:** The original SKILL.md had no YAML frontmatter, which caused validation to fail outright (10% score). I added frontmatter (`name` + `description`) to establish a proper baseline of 67%, then optimized from there.

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

**Frontmatter (required for skill validation):**
- Added YAML frontmatter with `name: wechat-dedup` and a detailed `description` field
- Added explicit "Use when..." clause with natural trigger terms (find duplicates, clean up WeChat folders, deduplicate PDF/Word files, free up storage)

**Description improvements (100%, up from 83%):**
- Expanded description to cover the two-phase fingerprinting approach and quarantine safety mechanism
- Added "Use when..." clause covering three common user scenarios (+1 completeness dimension)

**Content improvements (77%, up from 35%):**
- Replaced generic feature description and trigger words section with a concrete 7-step workflow including an explicit user confirmation checkpoint before file moves
- Added executable Python code example showing the core `find_duplicates()` two-phase algorithm with inline comments
- Added error handling section documenting behavior for missing paths, permission errors, and quarantine directory failures
- Removed redundant trigger words section and technical implementation library list (not actionable for Claude)
- Consolidated safety mechanisms into a focused section with clear guarantees

</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 - [@yogesh-tessl](https://github.com/yogesh-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