competition-linux-credential-pivot

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Linux credential artifacts, service tokens, SSH material, cloud and container secrets, socket-level trust, and host-to-host pivot chains. Use when the user asks to trace Linux auth artifacts, accepted token or key replay, socket or service-account trust edges, sudo or capability abuse, or explain lateral movement across Linux challenge nodes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./CTF-Sandbox-Orchestrator/competition-linux-credential-pivot/SKILL.md

Quality

Content

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

The content is concise, actionable, and well-structured with proper progressive disclosure to a single real reference file. Its main weakness is the absence of an explicit validation/retry feedback loop in a workflow that handles replay and pivot operations.

Suggestions

Add an explicit validation checkpoint in the Prove Replay And Pivot phase: after executing a replay, verify the gained session/privilege is real and retry with a corrected artifact if acceptance fails.

Include a few concrete command-level probes (e.g. sudo -l, ss -lnp, capability inspection) in the Map phase to lift actionability to fully executable.

Trim the opening paragraph that restates the $ctf-sandbox-orchestrator routing caveat already covered by the description.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept over-explanation and every line task-relevant; the opening paragraph lightly restates the routing caveat already in the description, a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	Specific, actionable checklist guidance (record SSH keys/kubeconfigs/sudoers/capabilities, show accepting service, compress to artifact->replay->pivot->capability) with only minor gaps in concrete command-level detail; absence of code is acceptable for an instruction-only skill.	4 / 5
Workflow Clarity	A clear 3-phase sequence with a 5-step Quick Start is present, but credential replay/pivot operations are destructive/batch-like and lack an explicit validate->fix->retry feedback loop, capping this dimension at 3 per the rubric guidance.	3 / 5
Progressive Disclosure	A well-organized ~50-line overview pointing to one real, clearly signaled, one-level-deep reference file (references/linux-credential-pivot.md, which exists) that holds the detailed checklists and replay matrix.	5 / 5
	Total	16 / 20 Passed

Description

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

The description is specific, well-triggered, and clearly distinct, explicitly addressing both what the skill does and when to use it. Minor room for improvement lies in adding a few more lay-synonym trigger terms.

Dimension	Reasoning	Score
Specificity	Multiple concrete actions are named across the domain (trace auth artifacts, accepted token/key replay, socket/service-account trust edges, sudo or capability abuse, explain lateral movement), giving comprehensive but conceptually-verb-level coverage rather than discrete enumerated operations.	4 / 5
Completeness	Explicitly answers both 'what' (workflow for Linux credential artifacts, service tokens, SSH material, cloud/container secrets, socket-level trust, pivot chains) and 'when' (Use when the user asks to trace... or explain lateral movement) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural niche terms a user would say (Linux auth artifacts, token or key replay, sudo or capability abuse, lateral movement, SSH material) with good synonym coverage, though tilted toward jargon over lay synonyms.	4 / 5
Distinctiveness Conflict Risk	A clear CTF niche with an explicit routing dependency ('Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions') minimizes conflict risk with other skills.	5 / 5
	Total	18 / 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-linux-credential-pivot/SKILL.md
Commit: 7e2097f

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