CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-custom-protocol-replay

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover custom framing, build a replay harness, satisfy sequence or checksum rules, replay a captured session, or prove the smallest message order that reaches an accepted branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A well-structured, lean instruction-only skill with excellent progressive disclosure and conciseness. Actionability and workflow clarity are solid but stop just short of the top anchor due to the absence of concrete examples and explicit validation checkpoints.

Suggestions

Add one short worked example (e.g., a minimal handshake→command transcript with the decisive mutation marked) to lift actionability toward fully copy-paste-ready guidance.

Make the verification loop explicit in the Workflow — e.g., a 'Validate: confirm the replay reaches the accepted branch; if rejected, revert to the last accepted state and change one field' checkpoint — to strengthen workflow clarity.

Cross-reference the specific reference sections (state-machine checklist, transcript checklist, evidence packaging) inline at the matching Workflow steps so navigation is even tighter.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — tight bullet lists with no explanation of concepts Claude already knows, and each section (Quick Start, Workflow, What To Preserve) earns its place.

5 / 5

Actionability

Concrete, specific instructional guidance ('identify client and server roles, session boundaries, and reset conditions'; 'recover framing, lengths, delimiters, sequence numbers, checksums, nonces') is actionable, though no executable examples or tooling are given (acceptable for an instruction-only skill, but keeps it just short of fully copy-paste ready).

4 / 5

Workflow Clarity

A clear three-phase sequence plus a five-step Quick Start is present, with acceptance-as-validation and a one-change-at-a-time mutation loop, but validation is goal-oriented rather than framed as explicit validate→fix→retry checkpoints.

4 / 5

Progressive Disclosure

The body is an overview that clearly signals a single one-level-deep reference ('Load `references/custom-protocol-replay.md`…'), which exists and holds the detailed checklists, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, specific description with clear what/when structure and good distinctiveness. Trigger-term quality is the only slight weakness, where a few phrases are more specification-like than natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction' — giving comprehensive coverage of the workflow rather than vague language.

5 / 5

Completeness

Explicitly answers 'what' (a CTF-sandbox workflow for protocol recovery and replay) and 'when' with concrete 'Use when…' trigger phrases, satisfying the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like 'decode an unknown protocol', 'build a replay harness', and 'replay a captured session' are present, but some triggers ('satisfy sequence or checksum rules', 'prove the smallest message order…') lean technical and a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear CTF niche with distinct protocol-replay triggers and an explicit boundary ('Use only after `$ctf-sandbox-orchestrator`…has…routed here'), minimizing conflict with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
Reviewed

Table of Contents

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.