War Room Debug
v1.0.0Facilitates coordinated crisis response using multiple agents to assess, investigate, fix, and document critical production issues efficiently.
⭐ 0· 82·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The SKILL.md describes a crisis-response protocol (roles, cadence, resolution) that matches the skill name and description. There are no unexpected env vars, binaries, or install steps required for this stated purpose.
Instruction Scope
The instructions are high-level and appropriate for a coordination protocol, but they are deliberately open-ended: roles like “Investigator” are told to ‘gather logs, data, reproduction steps’ and the protocol references a ‘shared state file’ without specifying storage, paths, or access controls. That openness is reasonable for a playbook but gives agents broad discretion to read/collect system logs or other sensitive data unless you constrain their access.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing will be written to disk or downloaded during install — lowest-risk delivery method.
Credentials
The skill declares no required environment variables or credentials, which is proportionate. However, the operational tasks it describes (collecting logs, implementing fixes) typically require elevated access in real use; the skill does not request or document those privileges, so you should plan access control externally.
Persistence & Privilege
always:false and no install/config changes are requested. The skill does not request persistent presence or attempt to modify other skills or system-wide settings.
Assessment
This skill is a protocol (playbook) rather than executable code — that makes it low-risk, but you should decide how to apply it safely: (1) limit which agents or users are allowed to act as Investigator/Fixer and give them only the minimum permissions they need to gather logs or perform changes; (2) choose and secure the ‘shared state file’ location (access controls, retention, encryption) to avoid leaking sensitive incident data; (3) require explicit human approval for any production writes or rollbacks performed by automated agents; (4) test the protocol in staging to confirm what data agents will read/write; and (5) audit agent actions during incidents. If you want the skill to actually collect logs or apply fixes, plan how to provide those credentials/paths out-of-band and document the exact scopes/permissions required.Like a lobster shell, security has layers — review code before you run it.
agentsvk97f6hnbw8ffzk6mfnkncnak6183c0r1debuggingvk97f6hnbw8ffzk6mfnkncnak6183c0r1latestvk97f6hnbw8ffzk6mfnkncnak6183c0r1troubleshootingvk97f6hnbw8ffzk6mfnkncnak6183c0r1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.