competition-queue-worker-drift

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. 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 well-structured, lean instruction skill with a clear workflow and a properly signaled one-level reference. The main improvement is reducing the redundancy between the Quick Start and Workflow sections and making verification steps more explicit.

Suggestions

De-duplicate the record-keeping items shared between Quick Start step 3 and Workflow section 1 so each section adds distinct value.

Add an explicit verification checkpoint (e.g., a labeled "Verify" step confirming the async boundary is isolated) to strengthen workflow_clarity.

Soften a few abstract directives like "Reproduce the smallest enqueue-to-side-effect flow" with a concrete example of the expected output artifact.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining basic concepts, but Quick Start step 3 ("Record queue name, message shape, worker config, retry policy") overlaps the Workflow section's "Record queue names, topics, cron schedules..." and could be tightened.	4 / 5
Actionability	Concrete, specific instruction-only guidance ("Map the async chain first: enqueue point, queue payload, worker consumer, retries, and final side effect") with minor abstraction ("Reproduce the smallest enqueue-to-side-effect flow"), appropriate for a tracing skill where code absence is not penalized.	4 / 5
Workflow Clarity	A clear five-step Quick Start and three-phase Workflow sequence are present, with step 5 ("Reproduce the smallest enqueue-to-side-effect flow that proves the decisive async drift") acting as a proof checkpoint; it is a tracing rather than destructive/batch skill, so no cap applies, though explicit verify checkpoints are not called out separately.	4 / 5
Progressive Disclosure	The body is a concise overview with a single clearly signaled one-level reference ("Load `references/queue-worker-drift.md`"), and that file exists and holds the detailed checklists, giving easy navigation.	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-scoped downstream-skill description: it states concrete capabilities, gives explicit "Use when" triggers, and is clearly distinguished from sibling skills via upstream gating. Slight room to soften jargon and add a few plainer synonyms for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("trace a queue payload", "inspect async job execution", "explain worker-only behavior", "follow retries or dead-letter handling", "connect an enqueued item to a later file, cache, email, or privilege-bearing side effect") alongside the domain list, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ("CTF-sandbox workflow for queues, async workers, cron jobs...") and when ("Use when the user asks to trace a queue payload, inspect async job execution...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ("queue payload", "async job execution", "retries", "dead-letter handling", "cron jobs") that users would plausibly say, but the phrasing leans technical and misses a few common synonyms or simpler variations.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (worker-only config drift, payload-to-side-effect chains) with distinct triggers and an explicit upstream-gating clause ("Use only after `$ctf-sandbox-orchestrator`"), minimizing conflict risk.	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-queue-worker-drift/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.