Improve/skill review optimization#150
Open
yogesh-tessl wants to merge 2 commits into
Open
Conversation
Hey @rkmahale17 👋 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 | |-------|--------|-------|--------| | rulcode-development | 10% | 80% | +70% | | visualization-creation-or-update (.agents) | 53% | 90% | +37% | | security-scan | 53% | 97% | +44% | | visualization-creation-or-update (.claude) | 53% | 90% | +37% | | integration-react-native | 52% | 95% | +43% | > Note: Three skills (visualization-creation-or-update x2 and security-scan) originally scored 18% because their name fields were not in kebab-case, which blocked the LLM judge entirely. I fixed the names to get meaningful baseline scores (53%) before optimizing further. The table above uses the revised baselines. Changes made: Root SKILL.md (10% → 80%) - Added proper YAML frontmatter with name and description fields (was completely missing) - Restructured from a README/vision document into a proper skill with clear workflow steps - Added "Use when..." trigger clause covering algorithm problems, visualizations, DSA pages, and UI changes - Added concrete dev commands (npm install, npm run dev, npm run build, npm run lint) - Reduced from 153 lines to 45 focused lines visualization-creation-or-update — .agents/skills/SKILL.md (53% → 90%) - Fixed name from "Visualization Creation or Update" to kebab-case - Expanded description with explicit "Use when..." clause and natural trigger terms - Reorganized 8 implementation rules into clear categories: code display, layout, interaction, commentary - Added explicit verification checklist with checkboxes - Removed meta-trigger text from body (moved to description) security-scan (53% → 97%) - Fixed name from "Security Scan" to kebab-case - Expanded description with "Use when..." clause covering audit, secret detection, credential scan, vulnerability check, leaked tokens - Added concrete fallback grep patterns for when the main scan script is unavailable - Added severity table with example findings per level - Removed meta-description opening and Keywords line from body - Added specific remediation examples visualization-creation-or-update — .agents/skills/visualization/SKILL.md (53% → 90%) - Same improvements as the .agents/skills/ version (these are companion skills) - Fixed name, expanded description, reorganized rules, added verification checklist integration-react-native (52% → 95%) - Expanded description from 49 to 264 chars with concrete actions - Added "Use when..." clause with natural triggers (analytics, session recording, feature flags) - Added inline PostHogProvider code example for immediate actionability - Added concrete error capture snippet - Added verification section with 3 specific checkpoints - Streamlined reference file list 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 🙏
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.
Hey @rkmahale17 👋
Skills spread across .claude/skills/ and .agents/skills/ with dedicated integration paths for React Native and React Router. You're clearly thinking about multi-agent compatibility from the ground up. The structured algorithm index on rulcode.com with 40+ patterns across 8 categories is impressively comprehensive for an interview prep platform. Wanted to suggest a few improvements to the SKILL.md.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
Root SKILL.md (10% → 80%)
visualization-creation-or-update — .agents/skills/SKILL.md (53% → 90%)
security-scan (53% → 97%)
visualization-creation-or-update - .agents/skills/visualization/SKILL.md (53% → 90%)
integration-react-native (52% → 95%)
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 🙏