feat: optimize cls-certify skill score from 71% to 94%#1
Open
rohan-tessl wants to merge 1 commit into
Open
Conversation
Hey @CatREFuse 👋 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 | |-------|--------|-------|--------| | cls-certify | 71% | 94% | +23% | <details> <summary>Changes made</summary> ### SKILL.md (~72% size reduction, 1069 → 294 lines) - **Restructured frontmatter**: Moved `version`, `build`, `batch_mode`, `output_dir`, `scan_mode` into `metadata` block with proper string values — resolves all 3 validation warnings - **Extracted scoring matrix**: Created `references/scoring-matrix.md` with the full deduction table, rating standards, intent verification rules, and agent context injection guidelines — previously inline across multiple sections - **Condensed six-dimension detection**: Replaced verbose inline regex patterns, concept explanations, and detection examples with concise summaries pointing to existing reference files (`threat-patterns.md`, `sensitive-data-patterns.md`, `api-classification.md`, etc.) - **Added validation checkpoints**: Explicit "验证点" gates between phases (verify JSON outputs exist, confirm classification tier, check score results before continuing) - **Removed redundant content**: Eliminated inline explanations of well-known concepts (SQL injection, eval(), GDPR requirements) that the LLM already understands - **Consolidated HTML rendering details**: Replaced inline placeholder injection rules and SVG coordinate calculations with a pointer to `references/report-data-protocol.md` - **Preserved all workflow functionality**: Every phase, bash command, tool invocation, and decision point is intact — just more concise and actionable </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 - [@rohan-tessl](https://github.com/rohan-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
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 @CatREFuse 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
SKILL.md (~72% size reduction, 1069 → 294 lines)
version,build,batch_mode,output_dir,scan_modeintometadatablock with proper string values — resolves all 3 validation warningsreferences/scoring-matrix.mdwith the full deduction table, rating standards, intent verification rules, and agent context injection guidelines — previously inline across multiple sectionsthreat-patterns.md,sensitive-data-patterns.md,api-classification.md, etc.)references/report-data-protocol.mdHonest 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 🙏