القائمة
Run chaos engineering experiments using Chaos Monkey, Litmus, or Gremlin
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/a5c-ai/babysitter --skill chaos-runnerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
| name | chaos-runner |
| description | Run chaos engineering experiments using Chaos Monkey, Litmus, or Gremlin |
| allowed-tools | ["Bash","Read","Write","Glob"] |
| graph | {"domains":["domain:software-engineering"],"specializations":["specialization:software-architecture"],"skillAreas":["skill-area:chaos-engineering"],"roles":["role:sre","role:architect"],"workflows":["workflow:incident-response"],"topics":["topic:chaos-engineering","topic:circuit-breakers"]} |
Runs chaos engineering experiments using Chaos Monkey, Litmus, or Gremlin including failure injection scenarios, blast radius control, and experiment analysis.
{
"type": "object",
"required": ["experiment"],
"properties": {
"experiment": {
"type": "object",
"properties": {
"name": { "type": "string" },
"type": {
"type": "string",
"enum": ["pod-kill", "network-latency", "cpu-stress", "memory-stress", "disk-fill", "node-drain"]
},
"target": {
"type": "object",
"properties": {
"namespace": { "type": "string" },
"labelSelector": { "type": "object" },
"percentage": { "type": "number" }
}
},
"duration": { "type": "string" }
}
},
"framework": {
"type": "string",
"enum": ["litmus", "gremlin", "chaos-monkey", "toxiproxy"],
"default": "litmus"
},
"steadyState": {
"type": "object",
"properties": {
"probes": { "type": "array" },
"assertions": { "type": "array" }
}
},
"options": {
"type": "object",
"properties": {
"dryRun": {
"type": "boolean",
"default": true
},
"autoRollback": {
"type": "boolean",
"default": true
},
"notifyOnFailure": {
"type": "boolean",
"default": true
}
}
}
}
}
{
"type": "object",
"properties": {
"experimentId": {
"type": "string"
},
"status": {
"type": "string",
"enum": ["passed", "failed", "aborted"]
},
"steadyStateValidation": {
"type": "object",
"properties": {
"before": { "type": "boolean" },
"during": { "type": "boolean"
{
kind: 'skill',
skill: {
name: 'chaos-runner',
context: {
experiment: {
name: 'pod-failure-test',
type: 'pod-kill',
target: {
namespace: 'production',
labelSelector: { app: 'api-service' },
percentage: 50
},
duration: '5m'
},
framework: 'litmus',
steadyState: {
probes: [{ type: 'http', endpoint: '/health' }],
assertions: [{ metric: 'error_rate', operator: '<', value: 0.01 }]
},
options: {
dryRun: false,
autoRollback: true
}
}
}
}