Add a maintainers script to safely promote high-confidence legacy risk labels from unknown to concrete values, cover it with tests, and regenerate the canonical skill artifacts and plugin copies. This reduces the legacy unknown backlog without forcing noisy classifications that still need manual review.
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
---
|
|
name: protocol-reverse-engineering
|
|
description: "Comprehensive techniques for capturing, analyzing, and documenting network protocols for security research, interoperability, and debugging."
|
|
risk: safe
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Protocol Reverse Engineering
|
|
|
|
Comprehensive techniques for capturing, analyzing, and documenting network protocols for security research, interoperability, and debugging.
|
|
|
|
## Use this skill when
|
|
|
|
- Working on protocol reverse engineering tasks or workflows
|
|
- Needing guidance, best practices, or checklists for protocol reverse engineering
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to protocol reverse engineering
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|