feat: improve vibegit skill score from 49% to 94%#77
Open
popey wants to merge 1 commit intomemovai:mainfrom
Open
feat: improve vibegit skill score from 49% to 94%#77popey wants to merge 1 commit intomemovai:mainfrom
popey wants to merge 1 commit intomemovai:mainfrom
Conversation
Hullo @crispyberry 👋 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 | |-------|--------|-------|--------| | vibegit | 49% | 94% | +45% | > **Note**: The original `vibegit` SKILL.md had no YAML frontmatter, which caused the reviewer to score it at 0%. I added minimal frontmatter (name + description) first to get a meaningful baseline of 49%, then optimised from there. The "before" score above reflects that corrected baseline. <details> <summary>Changes summary</summary> - **Added YAML frontmatter** with `name` (kebab-case) and a detailed `description` field including specific trigger terms and a "Use when..." clause for reliable skill selection - **Expanded description** with concrete actions (create snapshots, track file changes, view history, time-travel) and natural user trigger terms (Memov, AI code changes, track prompts) - **Added verification step** after snap commands (`history.sh --limit 1`) so users can confirm snapshots were recorded - **Removed redundant "Direct CLI Usage" section** that duplicated the script reference tables - **Removed "Benefits" section** — the agent understands version control value without explanation - **Removed "What Gets Recorded" section** — this information is implicit from the snap parameters - **Streamlined prerequisites** into a single compact code block - **Tightened "How to Use"** into a concise "Usage Modes" section - **Reduced line count** from 188 to 129 while preserving all actionable content </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 - [@popey](https://github.com/popey) - if you hit any snags. Thanks in advance 🙏
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hullo @crispyberry 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes summary
name(kebab-case) and a detaileddescriptionfield including specific trigger terms and a "Use when..." clause for reliable skill selectionhistory.sh --limit 1) so users can confirm snapshots were recordedHonest 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 - @popey - if you hit any snags.
Thanks in advance 🙏