competition-web-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CTF web, API, SSR, frontend, queue-backed app, and routing challenges. Use when the user asks to inspect a site or API, follow real browser requests, debug auth or session flow, trace uploads or workers, find hidden routes, or explain why frontend and backend behavior diverge under sandbox-internal routing. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
70
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
3 findings: 1 critical severity, 2 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
This repository includes an explicit exploit write-up and ready-to-run code (Python and JavaScript) that forges admin cookies by reusing URL access tokens as HMAC keys, enabling privilege escalation and unauthorized access.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill explicitly instructs the agent to "inspect" and "record exact ... headers, cookies, and body" and to preserve "exact requests and responses," which requires capturing and outputting sensitive secrets (tokens, cookies, API keys) verbatim.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
I scanned the skill and reference files for literal, high-entropy values that could be usable credentials. The only candidate is the long, random-looking access token string shown inline in the cookie HMAC key reuse reference. It is not a generic placeholder (e.g., YOUR_API_KEY) and appears as a concrete token in a URL example, so it meets the definition of a high-entropy literal that could be reused as a secret. Other values in the docs are placeholders (e.g., "从URL提取的token", "已知的token"), example JSON like {"admin":true}, or configuration names — all of which I ignored per the rules.
- Repository
- zhaoxuya520/reverse-skill
- Commit
6aa1362
- Audited
- Security analysis
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.