Skip to content
TrustedSkillsbeta
Back to all skills

Chaos Engineer

Checked
jeffallan·vlatest·security·MIT

The Chaos Engineer skill simulates disruptive events to proactively identify vulnerabilities and strengthen system resilience – a vital tool for robust deployments.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jeffallan/claude-skills --skill chaos-engineer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jeffallan

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jeffallan/claude-skills at 1be15d8064.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1be15d8064
Manifest
skills/chaos-engineer/SKILL.md
Scanned
6 files, 2,077 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows you to simulate chaotic events and test system resilience. It can introduce failures, delays, or resource constraints to observe how a system responds. The goal is to proactively identify weaknesses and improve overall stability before real-world incidents occur.

When to use it

  • Testing critical infrastructure: Simulate network outages or database slowdowns to assess application behavior under stress.
  • Validating disaster recovery plans: Inject failures to verify that backup systems activate correctly and data can be restored.
  • Performance optimization: Introduce resource limitations (CPU, memory) to identify bottlenecks and optimize system performance.
  • Security hardening: Simulate denial-of-service attacks or unauthorized access attempts to evaluate security controls.

Key capabilities

  • Failure injection
  • Delay simulation
  • Resource constraint modeling
  • Resilience testing

Example prompts

  • "Simulate a 50% packet loss on the network connection for 60 seconds."
  • "Introduce a 2x slowdown to database queries for the next hour."
  • "Reduce available memory by 30% and monitor application performance."

Tips & gotchas

This skill requires a good understanding of the system being tested. Incorrect configurations or unrealistic simulations can lead to misleading results, so proceed with caution in production environments.