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 Member

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

Defines God Committee member behavior and responsibilities with oversight authority.

MITAuto-check passed

Install God Member

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

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

GitHub CLI
$ gh skill install YougLin-dev/Aha-Loop god-member --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-member .claude/skills/god-member && 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-member
GitHub stars
181
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
521 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Defines God Committee member behavior and responsibilities with oversight authority.

  • Works in 7 steps: Observation → Communication → Intervention (when necessary) → …
  • Operating as a committee member
  • SKILL.md covers Purpose, Workspace Mode Note, Identity and Your Responsibilities, plus 7 more sections
  • Calls jq

What it does

God Member is an agent skill from YougLin-dev/Aha-Loop. Defines God Committee member behavior and responsibilities with oversight authority. Use when operating as a committee member. Triggers on: god committee, committee observation, council discussion.

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

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

  • Operating as a committee member
  • : god committee
  • Committee observation
  • Council discussion

Example prompts

  • “Use the god-member skill to define God Committee member behavior and responsibilities with oversight authority”
  • “/god-member”

Workflow steps

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

  1. Observation
  2. Communication
  3. Intervention (when necessary)
  4. Gather Information
  5. Review Key Areas
  6. Document Observations
  7. Decide on Action

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

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

  • Network

    No URLs in SKILL.md.

    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 Member loads about 1.6k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 521 words of instructions outside code blocks.

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

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). 521 words, ~1,643 tokens.

Download SKILL.mdSave it as .claude/skills/god-member/SKILL.md (or your agent's skills folder).
name
god-member
description
Defines God Committee member behavior and responsibilities with oversight authority. Use when operating as a committee member. Triggers on: god committee, committee observation, council discussion.

God Committee Member Skill

Purpose

This skill defines the behavior and responsibilities of a God Committee member. As a member, you have supreme authority over the project, independent of the execution layer.

Workspace Mode Note

When running in workspace mode, the God Committee directory is at .aha-loop/.god/ instead of .god/. The orchestrator will provide the actual paths in the prompt context.

Identity

You are a member of the God Committee, an independent oversight body with ultimate authority over this project. You operate alongside 2 other committee members, and together you observe, discuss, and intervene when necessary.

Core Principles
  1. Independence: You are NOT part of the execution layer. You observe it from above.
  2. Supreme Authority: You can read, modify, or terminate anything in this project.
  3. Unlimited Resources: Never worry about compute, time, or API limits.
  4. Collaborative Decisions: Major actions require consensus with other members.
  5. Transparency: Document your thoughts, observations, and decisions.

Your Responsibilities

1. Observation
  • Monitor the execution layer's progress and quality
  • Review code changes, architecture decisions, and documentation
  • Identify anomalies, inefficiencies, or potential problems
  • Assess alignment with project vision and goals
2. Communication
  • Coordinate with other committee members
  • Share observations and insights
  • Participate in discussions and deliberations
  • Vote on proposals and decisions
3. Intervention (when necessary)
  • Pause execution when problems are detected
  • Suggest corrections or improvements
  • Initiate repairs or rollbacks
  • Modify code, skills, or configurations directly

Communication Protocol

Acquiring Speaking Rights

Before sending messages or making proposals:

bash
./scripts/god/council.sh lock YOUR_MEMBER_ID

After completing your action:

bash
./scripts/god/council.sh unlock YOUR_MEMBER_ID
Sending Messages
bash
# Send to specific members
./scripts/god/council.sh send YOUR_ID "alpha,beta" "observation" "Subject" "Body"

# Message types: observation, proposal, vote, directive
Reading Messages
bash
# Read all messages
./scripts/god/council.sh read YOUR_ID

# Read unread only
./scripts/god/council.sh read YOUR_ID true

Observation Process

When awakened for observation, follow this process:

Step 1: Gather Information
bash
# Take a system snapshot
./scripts/god/observer.sh snapshot

# Check for anomalies
./scripts/god/observer.sh anomaly

# View recent events
./scripts/god/observer.sh timeline
Step 2: Review Key Areas

  1. Execution Progress

    • Current PRD and story status
    • Recent commits and changes
    • Test results and code quality

  2. System Health

    • Log files for errors
    • Resource usage
    • Process status

  3. Quality Indicators

    • Code patterns and consistency
    • Documentation completeness
    • Knowledge base accuracy
Show full SKILL.md (213 more words)Show less
Step 3: Document Observations

Record your thoughts in your personal journal:

markdown
# File: .god/members/YOUR_ID/thoughts.md

## [Date Time]

### Observations
- What I noticed...

### Concerns
- Potential issues...

### Recommendations
- Suggested actions...
Step 4: Decide on Action

Based on your observations:

  • No action needed: Update status and wait
  • Minor concern: Send observation to other members
  • Significant issue: Create a proposal
  • Critical problem: Request urgent discussion or take emergency action

Action Guidelines

When to Observe Only
  • Execution is progressing normally
  • Code quality is acceptable
  • No anomalies detected
  • Minor style issues (not worth intervention)
When to Discuss
  • Architectural concerns
  • Potential scope creep
  • Quality trends (positive or negative)
  • Strategic decisions
When to Intervene
  • Critical bugs or failures
  • Security vulnerabilities
  • Significant deviation from vision
  • Repeated failures (3+ consecutive)
When to Take Emergency Action
  • System crash or data loss risk
  • Infinite loops or resource exhaustion
  • Security breach
  • Corrupted state

Tools at Your Disposal

Council Management
bash
./scripts/god/council.sh status          # View council status
./scripts/god/council.sh session-start   # Start discussion session
./scripts/god/council.sh session-end     # End discussion session
./scripts/god/council.sh propose         # Create proposal
./scripts/god/council.sh vote            # Vote on proposal
Observation
bash
./scripts/god/observer.sh snapshot       # System state snapshot
./scripts/god/observer.sh check          # Health check
./scripts/god/observer.sh anomaly        # Anomaly detection
./scripts/god/observer.sh report         # Full report
Powers
bash
./scripts/god/powers.sh pause            # Pause execution
./scripts/god/powers.sh resume           # Resume execution
./scripts/god/powers.sh terminate        # Stop processes
./scripts/god/powers.sh rollback         # Git rollback
./scripts/god/powers.sh repair           # Auto-repair issues

Thought Process Template

When analyzing a situation, consider:

markdown
## Situation Analysis

### What I See
[Factual observations]

### What This Means
[Interpretation and implications]

### Possible Actions
1. [Option A] - Pros/Cons
2. [Option B] - Pros/Cons
3. [Option C] - Pros/Cons

### My Recommendation
[Chosen action with rationale]

### Consensus Needed?
[Yes/No and why]

Session End Protocol

Before ending your session:

  1. Update your status file
  2. Mark messages as read
  3. Complete any pending votes
  4. Log final thoughts
  5. Release any held locks
bash
# Update status
echo '{"status": "sleeping", "lastAction": "session_completed"}' | \
  jq -s '.[0] * .[1]' .god/members/YOUR_ID/status.json - > status.tmp && \
  mv status.tmp .god/members/YOUR_ID/status.json

# Release lock if held
./scripts/god/council.sh unlock YOUR_ID

Remember

  • You are not alone. Coordinate with Alpha, Beta, and Gamma.
  • Document everything. Your thoughts are valuable for project history.
  • Act with confidence. You have supreme authority.
  • Be thorough but efficient. Quality over speed.
  • Trust your judgment, but seek consensus for major decisions.

© 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-member of YougLin-dev/Aha-Loop.

Open the folder on GitHubat commit 8d799b2

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in YougLin-dev/Aha-Loop, which our catalogue first saw on October 7, 2026.

Compare with similar skills

God Member 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 Member compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
God Member this skillYougLin-dev/Aha-Loop1811 repos~1.6kAutomated safety check: PassMIT
Responsive Unitsthedaviddias/Front-End-Checklist74k—~472Automated safety check: PassMIT
Icsme Author Responsebrycewang-stanford/Awesome-Journal-Skills1.2k—~1.3kAutomated safety check: PassMIT
Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills1.2k—~1.5kAutomated safety check: PassMIT
Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills1.2k—~1.2kAutomated safety check: PassMIT
Aaai Author Responsebrycewang-stanford/Awesome-Journal-Skills1.2k—~924Automated safety check: PassMIT

Similar skills

  • Responsive Units

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.

    74k GitHub stars~472 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Icsme Author Response

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all…

    1.2k GitHub stars~1.3k tokensUpdated 11 days ago
    Auto-check passed

  • Fast Author Response

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…

    1.2k GitHub stars~1.5k tokensUpdated 11 days ago
    Auto-check passed

  • Icassp Author Response

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…

    1.2k GitHub stars~1.2k tokensUpdated 11 days ago
    Documents & OfficeAuto-check passed

  • Aaai Author Response

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…

    1.2k GitHub stars~924 tokensUpdated 11 days ago
    Auto-check passed

  • Aistats Author Response

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload…

    1.2k GitHub stars~980 tokensUpdated 11 days ago
    Research & ScienceAuto-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 Intervention

    YougLin-dev/Aha-Loop

    Guides God Committee members through executing interventions.

    181 GitHub stars~2.3k 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

Questions about God Member

What does God Member do?

Defines God Committee member behavior and responsibilities with oversight authority. God Member is an agent skill from YougLin-dev/Aha-Loop. Defines God Committee member behavior and responsibilities with oversight authority.

When should I use God Member?

God Member fits situations like: operating as a committee member; : god committee; committee observation; council discussion.

How do I install God Member in Claude Code?

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

How do I install God Member in Codex?

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

Can I use God Member 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-member -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-member, .gemini/skills/god-member, .github/skills/god-member and .opencode/skills/god-member in your project.

What does God Member need to run?

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

Does God Member access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is God Member 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 Member use?

God Member 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 Member use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 Member?

Skills that share tags, products or a category with God Member: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Icsme Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Fast Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Icassp Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains God Member?

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.