Conversation
Hullo @magicseek 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | nblm | 68% | 94% | +26% | <details> <summary>Changes made</summary> - **Rewrote frontmatter description** with explicit "Use when..." clause and natural trigger terms (NotebookLM URL, research notes, uploaded documents, citation-backed answers) — directly improved all four description dimensions from 57% to 100% - **Removed ~300 lines of redundant documentation** — commands were documented three times (Commands table, Command Routing section, and Extended Documentation). Consolidated to the authoritative Command Routing section - **Preserved critical operational notes** — run.py wrapper requirement, Smart Add auto-discovery, follow-up mechanism, and Z-Library integration kept as a concise section - **Added proper reference links** to existing `references/` files (api_reference.md, troubleshooting.md, usage_patterns.md) for progressive disclosure instead of inlining everything - **Resolved line count warning** — reduced from 622 lines to 318 lines, clearing the "SKILL.md is long" validation warning </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 @magicseek 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. The majority of change is a significant deletion of redundant guidance, which is accessible in other reference files within the repo.Here's the before/after:
Changes made
references/files (api_reference.md, troubleshooting.md, usage_patterns.md) for progressive disclosure instead of inlining everythingHonest 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 🙏