Individual skill
shadowtrace-ctf-workspace
Resume or initialize an evidence-first CTF workspace using explicit state files and reproducible checkpoints.
skills/shadowtrace-arena-ctf-workspace/SKILL.md
Source commit b6785d53ca5133974b6d9c987f13f606df28cc38
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 125
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- integrity-protection Repository topic
- macos Repository topic
- persona Repository topic
- prompt-injection Repository topic
- workbuddy Repository topic
- automation Repository topic
- codex Repository topic
- codex-cli Repository topic
- no-dependencies Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,093 bytes
Read excerpt
# ShadowTrace CTF Workspace
Use this pack when a task mentions a CTF, challenge attachment, flag, sandbox,
or an existing challenge directory.
## Workflow
1. Inspect the workspace with `workspace_status`.
2. Read existing state files before proposing a new path.
3. Inventory artifacts without executing them.
4. Record facts separately from hypotheses.
5. Choose one narrow proof path and define its success signal.
6. Update the state only after evidence changes.