protocol-reverse-engineering

Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/protocol-reverse-engineering/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is appropriately concise and well-sectioned, but its instructions are generic and lack the concrete tooling, commands, and dissection examples that make protocol reverse engineering actionable. The referenced playbook path is also missing from the bundle, weakening progressive disclosure.

Suggestions

Replace abstract steps with concrete, executable guidance: name specific capture/dissection tools (e.g. tcpdump, tshark, Wireshark dissectors) and show a short worked example of capture-to-dissection-to-documentation.

Define the real protocol-RE workflow as a numbered sequence with validation checkpoints (e.g. verify a captured packet decodes cleanly before documenting field semantics).

Create the referenced resources/implementation-playbook.md (or fix the path) so the one-level-deep reference actually resolves.

Dimension	Reasoning	Score
Conciseness	The ~24-line body is lean and assumes Claude's competence, e.g. 'Clarify goals, constraints, and required inputs' with no padding or re-explanation of basic concepts, matching the lean-and-efficient anchor.	3 / 3
Actionability	Guidance is abstract — 'Apply relevant best practices and validate outcomes' and 'Provide actionable steps and verification' describe rather than instruct, with no concrete tools (tcpdump/tshark/Wireshark), commands, or dissection examples, matching the vague/abstract anchor.	1 / 3
Workflow Clarity	A generic four-item list is present but it is not tied to the actual protocol-RE sequence (capture → dissect → document) and lacks explicit validation checkpoints, matching the 'steps listed but validation gaps' anchor rather than the fully sequenced anchor above.	2 / 3
Progressive Disclosure	The body signals a one-level-deep reference to 'resources/implementation-playbook.md', but that referenced directory/file does not exist in the bundle, so the navigation is broken rather than cleanly resolving as the top anchor requires.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that states concrete capabilities and pairs them with explicit natural-language triggers, clearly answering both what the skill does and when to use it. It is distinctive within its niche and uses appropriate third-person voice.

Dimension	Reasoning	Score
Specificity	Names three concrete capabilities — 'packet analysis, protocol dissection, and custom protocol documentation' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('packet analysis, protocol dissection, and custom protocol documentation') and when ('Use when analyzing network traffic...'), matching the anchor for clear what-and-when with explicit triggers.	3 / 3
Trigger Term Quality	Natural user-facing triggers — 'analyzing network traffic, understanding proprietary protocols, or debugging network communication' — give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	A clear niche (protocol reverse engineering) with distinct network-traffic/proprietary-protocol triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/protocol-reverse-engineering/SKILL.md
Commit: e63f7dd

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.