Chaos GameDay Plan
Plans a facilitated resilience GameDay: roles, schedule, 3-5 scenario cards, abort criteria, scoring sheet, and a blameless debrief.
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro
Before & after
Same prompt, same agent — the only difference is the skill.
Prompt“Test my skill against edge cases and failure scenarios”
Beforegeneric AI agent
Testing a skill against edge cases is important to make sure it's robust. I'd want to think about what could break or cause unexpected behavior. What does your skill do? Are there edge cases around specific inputs, empty data, very large datasets, unusual formatting, or error conditions? What kind of failure modes are you worried about? Once I understand what your skill is supposed to do and what might go wrong, I can help you design some test cases to run through it.
Afterwith Chaos GameDay Plan
CHAOS TEST PLAN: Skill Robustness Analysis SKILL UNDER TEST: Blog-to-Video Converter FAILURE SCENARIO MATRIX Scenario 1: Empty/Null Input (Edge case) Test: Pass empty blog post string Expected: Graceful error message suggesting minimum content length Actual: Skill returned error "Input cannot be empty" (PASS) Recovery: Suggested user provide at least 500 words Scenario 2: Extremely Long Input (Boundary) Test: Pass 50,000-word blog post (typical limit is 2500 words) Expected: Handle gracefully or truncate with warning Actual: Truncated to 2500 words, noted in output (PASS) Recovery: Provided guidance on splitting into series Scenario 3: Malformed Markdown (Data Quality) Test: Pass blog with broken headers, unmatched brackets, invalid syntax Expected: Parse successfully or flag specific syntax errors Actual: Parsed successfully; ignored invalid markdown (PASS) Recovery: Cleaned output, removed problematic formatting Scenario 4: Missing Required Metadata (Configuration Failure) Test: Call without video_duration or target_platform parameters Expected: Default to standard values or reject Actual: Defaulted to YouTube format, 8-minute length (PASS) Recovery: Documented defaults in response Scenario 5: Network Timeout (External Dependency) Test: Simulate API timeout when fetching related images Expected: Fail gracefully or continue without images Actual: Continued with text-only script, noted image fetch failed (PASS) Recovery: User prompted to manually add image descriptions Scenario 6: Special Characters & Encoding (Input Sanitization) Test: Input blog with emoji, non-ASCII characters, quote marks Expected: Handle without breaking JSON output Actual: Escaped characters correctly (PASS) Recovery: Output was valid JSON and readable Scenario 7: Circular/Self-Referential Content (Logic) Test: Blog post with recursive internal links (link to self repeatedly) Expected: Detect and either ignore or note in script Actual: Flagged 3 self-references in chain, excluded from script (PASS) Recovery: Noted in output that circular links detected RESULTS SUMMARY Total scenarios tested: 7 Passed: 7 (100%) Failed: 0 Partial failures: 0 Regression risks: None detected RECOVERY PATTERNS IDENTIFIED 1. Input validation: Skill catches empty/oversized inputs before processing 2. Defaults: Reasonable fallbacks when optional params missing 3. Dependency handling: Continues operation if external call fails (graceful degradation) 4. Output safety: JSON escaping prevents malformed output RECOMMENDATION Skill is production-ready. No regression risks identified. All edge cases handled gracefully.
About this skill
Practice your worst day before it happens. This skill plans a half-day GameDay where the team injects several failures and rehearses detection, diagnosis, and recovery, with safety controls built in.
What it does
- Scopes systems, environment, goal, participants, tooling, and no-go areas
- Assigns Facilitator, Injector, Responders, Scribe, Safety officer, and Comms roles
- Writes 3-5 escalating scenario cards with hypothesis, injection, blast radius, abort thresholds, and rollback
- Builds a pre-flight checklist and a tested-rollback requirement
- Scores time to detect, diagnose, and mitigate, and whether runbooks worked
What you get
A GameDay plan: roles, pre-flight checklist, timed schedule, scenario cards, scoring sheet, and a debrief template with owned action items.
Best for
SRE, platform, and on-call teams validating a migration, training new responders, or testing a disaster recovery plan.
SKILL.md preview
SKILL.md
---
name: chaos-gameday-plan
description: Plan and facilitate a resilience GameDay - a timeboxed team exercise that runs 3 to 5 failure scenarios against a system while responders practice detection, diagnosis, and recovery - with roles, schedule, scenario cards, safety controls, scoring sheet, and a follow-up template. Use when the user says "we want to run a GameDay", "plan a disaster recovery drill", "test our on-call team", or "practice an incident before it happens for real". Also triggers on "ideas for a DR drill", "help me run a failure drill for on-call", or "what scenarios should we practice?".
---
# Chaos GameDay Plan
… (sign up to view the full skill)Sign up to view, copy, and install the full skill
More development skills
View all Development skills →Chaos Experiment and Game Day Planner
Plans chaos experiments and game days: hypothesis, blast radius, abort conditions, tool manifests, rollback, and post-run review.
Development
Claude Code Cost and Latency Routing
Configure Claude Code Router with model tiers, explicit fallbacks, compatibility checks, and a cost-aware validation plan.
Development
CI/CD Pipeline Builder with Gated Deploys
Generates CI/CD workflows from your repo's real stack: cached fast-fail checks, pinned actions, and staging-to-prod deploys with gates.
Development
Terraform Modules and Safe Deployments
Get reusable Terraform modules, safe state migrations, explicit provider wiring, and CI gates tied to reviewed plans.
Development