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

85%

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

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 tight, well-organized instruction-only skill that defers detail to a real one-level reference and gives concrete investigation checklists. It loses a little to mild intro/Quick-Start redundancy and the absence of an explicit error-recovery feedback loop.

Suggestions

Remove or trim the opening paragraph that re-states the `$ctf-sandbox-orchestrator` dependency already specified in the frontmatter description, since it costs tokens without adding new guidance.

Merge the overlapping 'Map the render chain' guidance in Quick Start step 1 and Workflow section 1 so the sequencing lives in one place.

Add an explicit verification/feedback checkpoint in the Workflow (e.g., 'If the reproduced branch does not prove the decisive behavior, widen the recorded context and re-reduce') to close the validation gap.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explaining of what SSR or hydration is), but the opening paragraph re-states the orchestrator dependency already in the description and Quick Start step 1 overlaps with Workflow step 1, leaving minor trims.	4 / 5
Actionability	Guidance is concrete and actionable for an investigation skill — enumerated items to record ('host, path, route match, loader, template, layout, hydration blob, and client boot chunk') and explicit comparisons to make — with the detailed checklist deferred to the reference, leaving only minor gaps.	4 / 5
Workflow Clarity	A clear sequenced process exists (5-step Quick Start plus 3 numbered Workflow phases) with verification-style steps like 'Reproduce the smallest request-to-render branch that proves the decisive behavior', but there is no explicit validate/fix/retry feedback loop.	4 / 5
Progressive Disclosure	The body is a clear overview with a single well-signaled one-level reference — 'Load `references/template-render-path.md` for the render checklist, hydration checklist, and evidence packaging' — and that file exists and holds the detail, keeping navigation easy.	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, well-structured description that explicitly covers what, when, and routing boundaries with concrete trigger verbs. The only weakness is moderately specialized jargon in the trigger terms, leaving a little room for more natural phrasing.

Dimension	Reasoning	Score
Specificity	The 'Use when...' clause lists multiple concrete verbs over a comprehensive domain set — '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' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	It explicitly states both what ('CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps') and when ('Use when the user asks to inspect SSR or template routes, trace render context or hydration data...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'inspect SSR or template routes', 'trace render context or hydration data', and 'preview or hidden-route rendering' give good keyword coverage, but the terms are fairly specialized jargon and a few common variations are absent, sitting just below the comprehensive synonym anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (SSR/template render-path investigation) and adds an explicit boundary — 'Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here' — minimizing conflict with sibling skills.	5 / 5
	Total	19 / 20 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: 7e2097f

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