Skip to content

feat: optimize windows-protocols skill score (76% → 100%) + add Tessl review CI#10

Open
rohan-tessl wants to merge 2 commits intoawakecoding:masterfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: optimize windows-protocols skill score (76% → 100%) + add Tessl review CI#10
rohan-tessl wants to merge 2 commits intoawakecoding:masterfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

@rohan-tessl rohan-tessl commented Mar 27, 2026

Hey @awakecoding 👋

I ran your skills through tessl skill review at work and found some targeted improvements.

image

Here's the full before/after:

Skill Before After Change
windows-protocols 76% 100% +24%

Your repo has one skill, and it was already solid — strong actionability and workflow clarity. The changes focus on filling in the gaps the review flagged: a more concrete description with specific protocol names, reduced redundancy, and better progressive disclosure.

Changes summary
  • Description: Added concrete action verbs (find packet structures, trace message flows, extract structure definitions) and specific protocol trigger terms (SMB, NTLM, Kerberos, RDP, DFS, MS-SMB2, MS-NLMP, MS-RDPBCGR) so agents match this skill more reliably
  • Consolidated navigation sections: Merged the overlapping "Navigation Strategy" and "Navigation Workflow" into a single streamlined section
  • Progressive disclosure: Moved detailed Protocol Clusters by Domain and Canonical Spec Structure subsections to a new REFERENCE.md, keeping short summaries with links in SKILL.md
  • Tightened content: Streamlined Outlier Handling and Quick Discovery Patterns to reduce redundancy while preserving all actionable guidance
  • Line count: 177 → 124 lines (leaner SKILL.md with detail in REFERENCE.md)

Tessl Skill Review GitHub Action

This PR also adds a lightweight GitHub Action (.github/workflows/skill-review.yml) that automatically reviews skill quality on future PRs:

  • What runs: On PRs that change **/SKILL.md, the workflow runs tesslio/skill-review and posts one comment with Tessl scores and feedback (updated on new pushes)
  • Zero extra accounts: Contributors don't need a Tessl login — only the default GITHUB_TOKEN is used to post the comment
  • Non-blocking by default: The check is feedback-only unless you add fail-threshold — no surprise red CI
  • Not a build replacement: This is review automation for skill markdown, not a substitute for your existing convert-and-publish pipeline
  • Optional gate: Add with: fail-threshold: 70 later if you want PRs to fail on low scores
  • Why only one skill edited here: This repo has one skill, so that's what this PR covers. After merge, any future SKILL.md changes get automatic review comments

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 and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.

Thanks in advance 🙏

- Expanded description with concrete action verbs and specific protocol
  names (SMB, NTLM, Kerberos, RDP, MS-SMB2, MS-NLMP, MS-RDPBCGR)
- Consolidated redundant Navigation Strategy and Navigation Workflow sections
- Moved detailed Protocol Clusters and Canonical Spec Structure subsections
  to REFERENCE.md for progressive disclosure
- Tightened Outlier Handling and Quick Discovery Patterns for conciseness
- Added REFERENCE.md with full domain-to-protocol mapping and heading variants

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| windows-protocols | 76% | 100% | +24% |
Adds .github/workflows/skill-review.yml that runs tesslio/skill-review
on PRs touching **/SKILL.md. Posts one PR comment with scores and
feedback using only GITHUB_TOKEN (no extra accounts needed).
Non-blocking by default — feedback-only unless fail-threshold is set.
@rohan-tessl rohan-tessl marked this pull request as ready for review March 27, 2026 06:28
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