New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

God Intervention

by YougLin-dev in YougLin-dev/Aha-Loop

Guides God Committee members through executing interventions.

MITAuto-check passedDevOps & Cloud

Install God Intervention

skills CLI
$ npx skills add YougLin-dev/Aha-Loop --skill god-intervention -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install YougLin-dev/Aha-Loop god-intervention --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/YougLin-dev/Aha-Loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/god-intervention .claude/skills/god-intervention && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
god-intervention
GitHub stars
181
Token cost
~2.3k tokens
SKILL.md length
320 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Guides God Committee members through executing interventions.

  • Works in 5 steps: Document the Intervention → Log the Event → Notify Other Members → …
  • Emergency actions
  • SKILL.md covers Purpose, Intervention Severity Levels, Pre-Intervention Checklist and Executing Interventions, plus 4 more sections
  • Calls jq, git and npm

What it does

God Intervention is an agent skill from YougLin-dev/Aha-Loop. Guides God Committee members through executing interventions. Use for repairs, rollbacks, and emergency actions. Triggers on: intervention, repair, rollback, emergency action.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. The repository describes itself as: [MVP] Aha Loop is a fully autonomous AI development system, extended from the core ideas of Ralph. It's not just an execution engine, but a complete AI development framework with… The licence is MIT.

When your agent uses it

  • Emergency actions
  • Emergency action

Example prompts

  • “Use the god-intervention skill to guide God Committee members through executing interventions”
  • “/god-intervention”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Document the Intervention
  2. Log the Event
  3. Notify Other Members
  4. Update Status
  5. Monitor for Recurrence

What it can do on your machine

Read from SKILL.md and the folder at commit 8d799b2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

God Intervention loads about 2.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 320 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from YougLin-dev/Aha-Loop at commit 8d799b2, republished under its MIT licence (© YougLin-dev). 320 words, ~2,287 tokens.

Download SKILL.mdSave it as .claude/skills/god-intervention/SKILL.md (or your agent's skills folder).
name
god-intervention
description
Guides God Committee members through executing interventions. Use for repairs, rollbacks, and emergency actions. Triggers on: intervention, repair, rollback, emergency action.

God Committee Intervention Skill

Purpose

This skill guides God Committee members through executing interventions - from minor repairs to major system modifications.

Intervention Severity Levels

Level 1: Minor Repair
  • Fix corrupted files
  • Clear stale locks
  • Truncate large logs
  • Fix permissions

Consensus Required: No

Level 2: Process Control
  • Pause execution
  • Resume execution
  • Terminate specific processes

Consensus Required: No (unless terminating all)

Level 3: Code Modification
  • Fix bugs directly
  • Update configurations
  • Modify skills
  • Add documentation

Consensus Required: Recommended

Level 4: Major Rollback
  • Revert multiple commits
  • Undo PRD progress
  • Reset system state

Consensus Required: Yes

Level 5: System Termination
  • Stop all execution
  • Archive project state
  • Full system shutdown

Consensus Required: Yes

Pre-Intervention Checklist

Before any intervention:

markdown
## Pre-Intervention Checklist

- [ ] Issue clearly identified and documented
- [ ] Evidence gathered (logs, metrics, observations)
- [ ] Impact assessment completed
- [ ] Rollback plan prepared
- [ ] Consensus obtained (if required)
- [ ] Execution layer paused (if needed)
- [ ] Backup created (if applicable)

Executing Interventions

Level 1: Minor Repairs
bash
# Clear stale locks
./scripts/god/powers.sh repair lock

# Clean up worktrees
./scripts/god/powers.sh repair worktrees

# Fix corrupted JSON files
./scripts/god/powers.sh repair json

# Truncate large logs
./scripts/god/powers.sh repair logs

# Fix script permissions
./scripts/god/powers.sh repair permissions

# Clean git state
./scripts/god/powers.sh repair git

# Run all repairs
./scripts/god/powers.sh repair all
Level 2: Process Control
Pausing Execution
bash
# Pause with reason
./scripts/god/powers.sh pause "Investigation needed: failing tests" YOUR_ID

# Check pause status
./scripts/god/powers.sh pause-status
Resuming Execution
bash
# Resume execution
./scripts/god/powers.sh resume YOUR_ID
Terminating Processes
bash
# Terminate orchestrator
./scripts/god/powers.sh terminate orchestrator YOUR_ID

# Terminate Aha Loop execution
./scripts/god/powers.sh terminate aha-loop YOUR_ID

# Terminate parallel explorer
./scripts/god/powers.sh terminate explorer YOUR_ID

# Terminate specific PID
./scripts/god/powers.sh terminate pid:12345 YOUR_ID

# Force kill (if terminate fails)
./scripts/god/powers.sh kill orchestrator YOUR_ID
Level 3: Code Modification
Direct File Edits

For simple modifications:

bash
# Append to file
./scripts/god/powers.sh modify "path/to/file" append "content" YOUR_ID

# Prepend to file
./scripts/god/powers.sh modify "path/to/file" prepend "content" YOUR_ID

# Replace file contents
./scripts/god/powers.sh modify "path/to/file" replace "new content" YOUR_ID

For complex edits, use your AI capabilities to directly edit files.

Skill Modifications
bash
# Disable a skill
./scripts/god/powers.sh modify-skill skill-name disable YOUR_ID

# Re-enable a skill
./scripts/god/powers.sh modify-skill skill-name enable YOUR_ID
Configuration Updates

Edit .god/config.json or project configurations directly:

bash
# Example: Update quorum
jq '.council.quorum = 3' .god/config.json > tmp && mv tmp .god/config.json
Level 4: Major Rollback
Git Rollback
bash
# Soft reset (keep changes staged)
./scripts/god/powers.sh rollback HEAD~3 soft YOUR_ID

# Mixed reset (keep changes unstaged)
./scripts/god/powers.sh rollback HEAD~3 mixed YOUR_ID

# Hard reset (discard all changes)
./scripts/god/powers.sh rollback HEAD~3 hard YOUR_ID

# Rollback to specific commit
./scripts/god/powers.sh rollback abc123 soft YOUR_ID
Restore from Stash
bash
./scripts/god/powers.sh restore-stash YOUR_ID
PRD Rollback

To rollback PRD progress:

  1. Update project.roadmap.json:

    bash
    jq '.prds |= map(if .id == "prd-xxx" then .status = "pending" else . end)' \
  project.roadmap.json > tmp && mv tmp project.roadmap.json

  2. Reset story status in PRD:

    bash
    jq '.stories |= map(.status = "pending")' \
  docs/prd/xxx/prd.json > tmp && mv tmp docs/prd/xxx/prd.json
Level 5: System Termination

⚠️ This requires consensus and should be rare.

bash
# Step 1: Pause everything
./scripts/god/powers.sh pause "System termination initiated" YOUR_ID

# Step 2: Terminate all processes
./scripts/god/powers.sh terminate all YOUR_ID

# Step 3: Stop awakener daemon
./scripts/god/awakener.sh stop

# Step 4: Create final state snapshot
./scripts/god/observer.sh snapshot
./scripts/god/observer.sh report

# Step 5: Archive (optional)
git tag -a "god-committee-termination-$(date +%Y%m%d)" -m "System terminated by God Committee"

# Step 6: Log final entry
./scripts/god/observer.sh event "termination" "System terminated by God Committee"

Intervention Patterns

Pattern 1: Investigate and Fix
1. Pause execution
2. Take snapshot
3. Investigate issue
4. Fix the problem
5. Verify fix
6. Resume execution
7. Monitor for recurrence
Pattern 2: Rollback and Retry
1. Pause execution
2. Take snapshot
3. Identify rollback point
4. Execute rollback
5. Clear any bad state
6. Modify approach if needed
7. Resume execution
Pattern 3: Emergency Stop and Repair
1. Terminate offending process immediately
2. Take snapshot
3. Assess damage
4. Run repairs
5. Notify other members
6. Plan recovery
7. Execute recovery
8. Resume with monitoring

Post-Intervention Protocol

After any intervention:

1. Document the Intervention
markdown
## Intervention Report

### Intervention ID
int-[timestamp]

### Type
[repair|process_control|code_modification|rollback|termination]

### Severity
[1-5]

### Triggered By
[observation|alert|proposal|emergency]

### Description
[What was done]

### Reason
[Why it was necessary]

### Steps Taken
1. [Step 1]
2. [Step 2]
3. ...

### Outcome
[Success/Partial/Failed]

### Side Effects
[Any unintended consequences]

### Follow-up Required
[Yes/No - if yes, what]

### Lessons Learned
[What we learned]
2. Log the Event
bash
./scripts/god/observer.sh event "intervention" "DESCRIPTION"
3. Notify Other Members
bash
./scripts/god/council.sh send YOUR_ID "other,members" "directive" \
  "Intervention Completed" "SUMMARY"
4. Update Status
bash
# Check intervention history
./scripts/god/powers.sh history interventions 10

# Review repair history
./scripts/god/powers.sh history repairs 10
5. Monitor for Recurrence

Set up a follow-up observation:

bash
# Trigger immediate observation
./scripts/god/awakener.sh random

# Or use a scheduled check type
./scripts/god/awakener.sh scheduled daily

Common Intervention Scenarios

Scenario: Failing Tests
bash
# 1. Check current state
./scripts/god/observer.sh check

# 2. Pause if needed
./scripts/god/powers.sh pause "Investigating test failures"

# 3. Analyze failures
cat test-results.json | jq '.failures'

# 4. Decide action:
#    - Minor fix: edit directly
#    - Major issue: rollback
#    - Need discussion: create proposal

# 5. Execute fix/rollback

# 6. Verify
npm test  # or equivalent

# 7. Resume
./scripts/god/powers.sh resume
Scenario: Stuck Process
bash
# 1. Identify stuck process
ps aux | grep -E "(aha-loop.sh|orchestrator|explorer)"

# 2. Check how long it's been running
# 3. Check for output/progress

# 4. If stuck, terminate
./scripts/god/powers.sh terminate pid:XXXXX

# 5. Clean up any locks
./scripts/god/powers.sh repair lock

# 6. Restart if appropriate
./scripts/aha-loop/orchestrator.sh --continue
Scenario: Corrupted State
bash
# 1. Stop everything
./scripts/god/powers.sh pause "Corrupted state detected"
./scripts/god/powers.sh terminate all

# 2. Assess damage
./scripts/god/powers.sh repair json  # Check for JSON issues
git status  # Check git state

# 3. Decide rollback point
git log --oneline -20

# 4. Execute rollback
./scripts/god/powers.sh rollback COMMIT_HASH hard

# 5. Run repairs
./scripts/god/powers.sh repair all

# 6. Verify
./scripts/god/observer.sh check

# 7. Resume
./scripts/god/powers.sh resume

Safety Guidelines

Always
  • ✅ Document before acting
  • ✅ Take snapshots before major changes
  • ✅ Verify after intervention
  • ✅ Notify other members of significant actions
  • ✅ Have a rollback plan
Never
  • ❌ Make major rollbacks without consensus
  • ❌ Terminate system without documentation
  • ❌ Skip verification after fixes
  • ❌ Hide interventions from other members
  • ❌ Assume fixes worked without testing

Power Status Check

Before intervention, verify your powers:

bash
./scripts/god/powers.sh status

This shows:

  • Which powers are enabled
  • Current pause status
  • Running processes

© YougLin-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/god-intervention of YougLin-dev/Aha-Loop.

Open the folder on GitHubat commit 8d799b2

Compare with similar skills

God Intervention next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

God Intervention compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
God Intervention this skillYougLin-dev/Aha-Loop181—~2.3kAutomated safety check: PassMIT
Campaign Postmortemzapier/gtm-cheat-codes342—~438Automated safety check: PassMIT
Expert TeamReJeCtAll/ExpertTeam-Codex113—~667Automated safety check: PassMIT
Implementing Patch Management For Ot Systemsmukul975/Anthropic-Cybersecurity-Skills34k—~3.2kAutomated safety check: PassApache-2.0
Prioritizing Vulnerabilities With Cvss Scoringmukul975/Anthropic-Cybersecurity-Skills34k—~1.9kAutomated safety check: PassApache-2.0
Devops Rollout Plangithub/awesome-copilot40k1 repos~999Automated safety check: PassMIT

Similar skills

  • Campaign Postmortem

    zapier/gtm-cheat-codes

    Official

    Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

    342 GitHub stars~438 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Expert Team

    ReJeCtAll/ExpertTeam-Codex

    专家团总路由器。用于 Codex CLI 的 $expert-team 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~667 tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed

  • Implementing Patch Management For Ot Systems

    mukul975/Anthropic-Cybersecurity-Skills

    Implements a structured patch management program for OT/ICS environments where IT-style patching can cause process disruption or safety hazards, covering vendor compatibility testing, risk-based…

    34k GitHub stars~3.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Prioritizing Vulnerabilities With Cvss Scoring

    mukul975/Anthropic-Cybersecurity-Skills

    The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity.

    34k GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Devops Rollout Plan

    github/awesome-copilot

    Official

    Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes

    40k GitHub starsUsed in 1 repo~999 tokens
    DevOps & CloudAuto-check passed

  • Soc Operations

    briiirussell/cybersecurity-skills

    Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst…

    413 GitHub stars~2.9k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

More from YougLin-dev/Aha-Loop

All 15 skills in this repo

  • Architect

    YougLin-dev/Aha-Loop

    Designs system architecture and selects technology stack based on vision analysis.

    181 GitHub stars~2.2k tokensUpdated 8 mo ago
    Auto-check passed

  • Doc Review

    YougLin-dev/Aha-Loop

    Reviews and cleans up outdated documentation. An agent skill from YougLin-dev/Aha-Loop.

    181 GitHub stars~1.5k tokensUpdated 8 mo ago
    Auto-check passed

  • God Consensus

    YougLin-dev/Aha-Loop

    Guides God Committee members through consensus-building for collective decisions.

    181 GitHub stars~2k tokensUpdated 8 mo ago
    Auto-check passed

  • God Member

    YougLin-dev/Aha-Loop

    Defines God Committee member behavior and responsibilities with oversight authority.

    181 GitHub stars~1.6k tokensUpdated 8 mo ago
    Auto-check passed

  • Parallel Explore

    YougLin-dev/Aha-Loop

    Guides parallel exploration of multiple implementation approaches using git worktrees.

    181 GitHub stars~1.9k tokensUpdated 8 mo ago
    Auto-check passed

  • Plan Review

    YougLin-dev/Aha-Loop

    Reviews and adjusts PRD plans based on research findings. An agent skill from YougLin-dev/Aha-Loop.

    181 GitHub stars~1.8k tokensUpdated 8 mo ago
    Auto-check passed

Categories

Questions about God Intervention

What does God Intervention do?

Guides God Committee members through executing interventions. God Intervention is an agent skill from YougLin-dev/Aha-Loop. Guides God Committee members through executing interventions.

When should I use God Intervention?

God Intervention fits situations like: emergency actions; emergency action.

How do I install God Intervention in Claude Code?

Run `npx skills add YougLin-dev/Aha-Loop --skill god-intervention -a claude-code`. Or copy the skill folder (.agents/skills/god-intervention in YougLin-dev/Aha-Loop) into .claude/skills/god-intervention in your project. Claude Code loads it when a task matches its description.

How do I install God Intervention in Codex?

Run `npx skills add YougLin-dev/Aha-Loop --skill god-intervention -a codex`. Or copy the skill folder (.agents/skills/god-intervention in YougLin-dev/Aha-Loop) into .agents/skills/god-intervention in your project. Codex loads it when a task matches its description.

Can I use God Intervention in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add YougLin-dev/Aha-Loop --skill god-intervention -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/god-intervention, .gemini/skills/god-intervention, .github/skills/god-intervention and .opencode/skills/god-intervention in your project.

What does God Intervention need to run?

Going by SKILL.md and its folder, God Intervention needs the command-line tools its instructions call (jq, git and npm).

Does God Intervention access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is God Intervention safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does God Intervention use?

God Intervention is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does God Intervention use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to God Intervention?

Skills that share tags, products or a category with God Intervention: Campaign Postmortem (zapier/gtm-cheat-codes, 342 stars), Expert Team (ReJeCtAll/ExpertTeam-Codex, 113 stars), Implementing Patch Management For Ot Systems (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Prioritizing Vulnerabilities With Cvss Scoring (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains God Intervention?

YougLin-dev (a GitHub user) maintains it in YougLin-dev/Aha-Loop, which has 181 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on February 3, 2026.

Source: YougLin-dev/Aha-Loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.