CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-runtime-routing

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution. Use when the user asks which host or container serves a route, why a public-looking domain still belongs to the sandbox, how headers or proxies change behavior, or how a route resolves across proxy, container, and worker boundaries. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

70

Quality

88%

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

78%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 instructional skill body with a clear sequenced workflow and proper progressive disclosure into a real reference file. It could tighten the opening redundancy and add a few more concrete illustrative examples to lift actionability.

Suggestions

Trim the redundant restatement of downstream-specialization gating in the opening paragraph since it already appears in the description and the first numbered line.

Add one short concrete route-map example (e.g., example.com -> nginx vhost -> container :8080 -> worker) to make the Quick Start map tangible rather than schematic.

Cross-link the validation concept ('Prove one route resolution end-to-end') explicitly to the reference's Verification Pattern so the feedback loop is unmistakable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding tutorials on what proxies or headers are; only minor redundancy in the opening lines restating the downstream-specialization point already in the description.

4 / 5

Actionability

Provides concrete procedural guidance such as 'client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker' and 'Re-run the same request with one routing input changed at a time'; no code, but the skill is instruction-only so its absence is not penalized.

4 / 5

Workflow Clarity

A clear 5-step Quick Start and a 3-phase Workflow are present with validation concepts (prove one route end-to-end before broadening, change one input at a time, distinguish routing from auth logic); this is investigative rather than destructive work, so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals one-level-deep references to the real bundle file 'references/runtime-routing.md' (and a sibling skill for smuggling cases), with the bulk detail appropriately split into the reference.

5 / 5

Total

17

/

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 that clearly delineates a narrow routing niche, states concrete capabilities, and pairs them with natural trigger phrases. The only minor gap is slightly less comprehensive coverage of synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete routing actions — reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (CTF-sandbox workflow for reverse proxies, Host headers, etc.) and 'when' (Use when the user asks which host or container serves a route...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('which host or container serves a route', 'why a public-looking domain still belongs to the sandbox', 'how headers or proxies change behavior'), but a few common synonyms or phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche scoped to a specific orchestrator and explicitly gates usage ('Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions'), minimizing conflict with other 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.

Validation — 16 / 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.