competition-template-render-path

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hydration data, compare template gating with handler enforcement, explain preview or hidden-route rendering, or connect render pipeline behavior to the decisive branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%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.

A well-structured, actionable investigation skill with clean progressive disclosure to a single verified reference. Its main weakness is mild cross-section redundancy and implicit rather than explicit validation checkpoints in the main body.

Suggestions

De-duplicate the 'Record host/route params/preview toggles' and 'Compare template gating with enforcement' guidance between Quick Start and the Workflow section so each token earns its place.

Add an explicit validation checkpoint in the Reduce phase, e.g., 'Confirm the decisive branch by reproducing it; if the success/failure pair does not isolate the branch, return to step 1' to create a feedback loop.

Surface the reproduction-as-proof step as a numbered checkpoint rather than embedding it in Quick Start, so the verification loop is unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no SSR/hydration concept explanations), but 'Record host, route params, preview toggles ...' and 'Compare template gating with ... enforcement' recur across both Quick Start and the Workflow section, so it could be tightened.	2 / 3
Actionability	As an instruction-only investigation skill it gives concrete procedural guidance (map the render chain in order, record specific fields, compare three gating layers, reduce to smallest request-to-render branch) rather than vague direction, which the rubric rewards for non-code skills.	3 / 3
Workflow Clarity	There is a clear three-phase sequence (map, trace, reduce) and a reproduction step, but validation checkpoints and error-recovery feedback loops are implicit rather than explicit, fitting the 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	Well-organized sections (Quick Start, Workflow, Read This Reference, What To Preserve) with a single clearly signaled one-level-deep reference to `references/template-render-path.md` (a real file) for the checklists, matching the clear-overview anchor.	3 / 3
	Total	10 / 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, specific description with explicit capability enumeration, natural trigger terms, and clear what/when coverage. The upstream-scoping clause effectively limits conflict risk.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions such as 'inspect SSR or template routes', 'trace render context or hydration data', 'compare template gating with handler enforcement', and 'connect render pipeline behavior to the decisive branch', matching the multiple-concrete-actions anchor.	3 / 3
Completeness	It states both what the skill does ('CTF-sandbox workflow for SSR, template rendering, route loaders ...') and an explicit 'Use when the user asks to ...' trigger, satisfying both the what and the when.	3 / 3
Trigger Term Quality	The 'Use when the user asks to ...' clause covers natural user phrasings (inspect routes, trace render context, compare gating, explain preview rendering) that a user in this niche would actually say, achieving good coverage.	3 / 3
Distinctiveness Conflict Risk	The narrow SSR/template-render niche plus the explicit 'Use only after `$ctf-sandbox-orchestrator` ... routed here' scoping makes it clearly distinguishable and unlikely to trigger for the wrong skill.	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: zhaoxuya520/reverse-skill
Path: CTF-Sandbox-Orchestrator/competition-template-render-path/SKILL.md
Commit: 6aa1362

Reviewed: 7 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.