zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/ctf-sandbox-orchestrator
ctf-sandbox-orchestrator
VerifiedDefault entrypoint and master ctf-sandbox-orchestrator workflow for CTF, exploit, reverse engineering, DFIR, pwnable, crypto, stego, mobile, AI-agent, cloud, container, Active Directory, Windows-host, and identity challenges. Use first when the user presents challenge infrastructure, binaries, prompts, hosts, or identities that should be treated as sandbox-internal by default and Codex needs to choose, route, and load the right downstream analysis path with concise evidence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| agents/openai.yaml | config | 350 B |
| references/agent-cloud.md | markdown | 1.6 KB |
| references/crypto-mobile.md | markdown | 1.9 KB |
| references/ctf-resources-digest.md | markdown | 4.7 KB |
| references/identity-windows.md | markdown | 1.8 KB |
| references/reporting.md | markdown | 1.6 KB |
| references/reverse-native.md | markdown | 1.7 KB |
| references/router-matrix.md | markdown | 5.6 KB |
| references/web-api.md | markdown | 1.6 KB |
references/reporting.md
View on GitHub# Reporting And Output Style
Use this reference when the user wants progress updates, findings, reviews, or recovery notes.
## Default Style
- Write in concise Simplified Chinese unless the user asks for English.
- Sound like a strong technical teammate, not a telemetry appliance.
- Prefer: outcome -> key evidence -> verification -> next step.
- Do not force rigid field-template reports unless the user explicitly asks for them.
## Structure By Task Type
- Web/API/debug: conclusion -> local status -> upstream deviation -> decisive request/response or code location -> next step
- Reverse/DFIR/pwn: verdict -> decisive artifact or primitive -> supporting offsets/files/logs -> verification or next step
- Crypto/stego/mobile: verdict -> transform or trust chain -> decisive bytes/hooks/components -> verification or next step
- Agent/cloud/identity/windows: verdict -> trust/deployment/pivot chain -> decisive evidence block -> verification or next step
## Evidence Packaging
Group related evidence instead of scattering it:
- Paths and code locations in one support bullet
- Offsets, hashes, section names, registry keys, event IDs, or ticket fields in one compact block
- Prompt snippets, tool calls, retrieved chunks, or manifest fragments in one compact block
Summarize long command output. Extract only the decisive lines unless the user explicitly asks for raw logs.
## Avoid
- Mechanical shells like `[TARGET PARAMETER/ASSET]`
- One giant paragraph mixing conclusion, evidence, and next steps
- Repeating the same path or identifier across many bullets when one support bullet would do
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |