CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-supply-chain

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges. Use when the user asks to trace dependency drift, registry pulls, malicious packages, build or release tampering, CI execution, artifact signing, or which shipped artifact the runtime actually consumes. 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

Passed

No findings from the security scan

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 compact, well-structured instruction-only skill that appropriately offloads detail to a single real reference file and gives specific analytical checkpoints. Could improve by adding an explicit verification checkpoint and trimming the duplicated gating paragraph.

Suggestions

Add an explicit verification step to the workflow (e.g., 'Confirm the divergence reproduces in the minimal build path before reporting it as the break point') to strengthen workflow_clarity.

Remove or shorten the opening paragraph that re-states the $ctf-sandbox-orchestrator gating, since it already appears in the frontmatter description, to improve conciseness.

Consider one concrete command or artifact-inspection example (e.g., comparing a registry-pulled digest against a signed manifest) to raise actionability toward fully executable guidance.

DimensionReasoningScore

Conciseness

Lean and free of concept padding, but the opening paragraph re-states the parent-orchestrator gating already present in the frontmatter description, a minor redundancy that could be trimmed.

4 / 5

Actionability

Provides concrete enumerated guidance ('Compare declared version, resolved version, and shipped artifact'; 'Identify whether the decisive mutation happens in dependency install, build step, publish step, or runtime bootstrap') with minor gaps and no executable commands, which is appropriate for an analysis skill.

4 / 5

Workflow Clarity

Clear sequenced Quick Start and a 3-phase Workflow with a defined output ('Report The Break Point'), but it lacks an explicit validation/verification checkpoint such as confirming the divergence is reproducible before reporting.

4 / 5

Progressive Disclosure

Concise overview body with a well-signaled, one-level-deep reference ('references/supply-chain.md', verified to exist) and a section explaining what the reference contains, enabling 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 tightly scoped, well-triggered description that clearly states capabilities, concrete use-when triggers, and a parent-skill routing constraint. Minor room to add informal synonym phrasings for trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete trace-actions ('trace dependency drift, registry pulls, malicious packages, build or release tampering, CI execution, artifact signing') plus a comprehensive domain list, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what ('CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges') and when ('Use when the user asks to trace...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger terms ('dependency drift, registry pulls, malicious packages, build or release tampering, artifact signing') that a CTF user would say, but a few synonyms and informal phrasings are missing versus the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear supply-chain-provenance niche with distinct triggers and an explicit gating clause ('Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here') minimizing conflict risk.

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.