ClawHub

Chaos Cognitive Resilience

v1.0.0

Design and test cognitive systems to gracefully recover from errors and overloads using chaos engineering principles and resilience metrics.

⭐ 0· 49·0 current·0 all-time
by@kingofzhao
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name and description (cognitive resilience via chaos engineering) match the SKILL.md content. No unexpected binaries, env vars, or config paths are requested. The lack of install or credentials is proportionate for a guidance/playbook.
✓
Instruction Scope
SKILL.md contains conceptual frameworks, metrics (CRI), and procedural phases for testing and hardening cognitive systems. It does not instruct the agent to read system files, access environment variables, call external endpoints, or execute commands. There is no scope creep in the written instructions.
✓
Install Mechanism
There is no install spec and no code files. Because this is instruction-only, nothing is written to disk or downloaded by the skill itself.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. That is appropriate for a conceptual playbook; there are no disproportionate or unexplained secrets requested.
✓
Persistence & Privilege
always is false and the skill does not request permanent presence or privileged modifications. Autonomous invocation is allowed by platform default but this skill's content does not enable privileged actions.
Assessment
This is a conceptual playbook (no code, no installs, no credentials) and is coherent with its stated purpose. Risks are operational rather than immediate: if you implement its experiments, run chaos injections only in isolated/test environments, avoid exposing real user data or PII, limit blast radius of tests, and add monitoring/kill-switches. Also note the skill's source/homepage are unknown — treat it as third‑party guidance and review any concrete test harness or scripts you build from it before running in production.

Like a lobster shell, security has layers — review code before you run it.

latestvk97az0n7ttq3267qr13ynec2hh841k08

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments