How do I install the Ghe Status skill?

Run npx skillmds@latest add aiskillstore/ghe-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ghe Status safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ghe Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ghe Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ghe Status?

aiskillstore (@aiskillstore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ghe Status by aiskillstore — Agent Skill

Name: Ghe Status
Rating: 4.666666666666667 (3 reviews)
Author: aiskillstore

Ghe Status

READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE WHEN: Asking about status, active threads, workflow state, or needing context at session start. DO NOT USE WHEN: Claiming issues (use ghe-claim), posting checkpoints (ghe-checkpoint), transitioning phases (ghe-transition), or needing detailed reports (ghe-report).

aiskillstore Updated Sep 8, 2026

File contents

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

Every word the user says is a specification - follow verbatim, no errors, no exceptions
Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
Never take initiative to change specifications - your role is to implement, not to reinterpret
If you see an error in the spec, you MUST:
- Stop immediately
- Explain the potential issue clearly
- Wait for user guidance before proceeding
No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

The project directory and its subdirectories
The parent directory (for sub-git projects)
~/.claude (for plugin/settings fixes)
/tmp

Do NOT write outside these locations.

GHE_REPORTS Rule (MANDATORY)

ALL reports MUST be posted to BOTH locations:

GitHub Issue Thread - Full report text (NOT just a link!)
GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Report naming: <TIMESTAMP>_<title or description>_(<AGENT>).md Timestamp format: YYYYMMDDHHMMSSTimezone

ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus

REQUIREMENTS/ is SEPARATE - permanent design documents, never deleted.

Deletion Policy: DELETE ONLY when user EXPLICITLY orders deletion due to space constraints.

Settings Awareness

Respects .claude/ghe.local.md:

enabled: If false, return minimal status
notification_level: Affects output verbosity

GitHub Elements Status (Quick Overview)

Purpose: Read-only quick overview of workflow state. Does NOT modify anything.

When to Use

Quick status check
See active threads
Check what's available
Session start context

How to Execute

Spawn the reporter agent with report type "status".

The reporter will:

Query all threads with GitHub Elements labels
Show active threads (DEV, TEST, REVIEW)
Display phase distribution
List recent completions
Show workflow health indicators
Flag any violations or warnings

Output Format

## GitHub Elements Status Report

### Active Threads
| Issue | Type | Phase | Epic | Assignee | Last Activity |
|-------|------|-------|------|----------|---------------|

### Phase Distribution
DEV: N active | TEST: N active | REVIEW: N active

### Available Work
[Ready issues not yet claimed]

### Workflow Health
- Violations: N
- Checkpoint frequency: N%

Key Differentiator

This is a READ-ONLY quick overview. For detailed metrics, health checks, or epic-specific reports, use ghe-report instead.

---name: ghe-statusdescription: READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE WHEN: Asking about status, active threads, workflow state, or needing context at session start. DO NOT USE WHEN: Claiming issues (use ghe-claim), posting checkpoints (ghe-checkpoint), transitioning phases (ghe-transition), or needing detailed reports (ghe-report).---## IRON LAW: User Specifications Are Sacred**THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.**1. **Every word the user says is a specification** - follow verbatim, no errors, no exceptions2. **Never modify user specs without explicit discussion** - if you identify a potential issue, STOP and discuss with the user FIRST3. **Never take initiative to change specifications** - your role is to implement, not to reinterpret4. **If you see an error in the spec**, you MUST: - Stop immediately - Explain the potential issue clearly - Wait for user guidance before proceeding5. **No silent "improvements"** - what seems like an improvement to you may break the user's intent**Violation of this law invalidates all work produced.**## Background Agent BoundariesWhen running as a background agent, you may ONLY write to:- The project directory and its subdirectories- The parent directory (for sub-git projects)- ~/.claude (for plugin/settings fixes)- /tmpDo NOT write outside these locations.---## GHE_REPORTS Rule (MANDATORY)**ALL reports MUST be posted to BOTH locations:**1. **GitHub Issue Thread** - Full report text (NOT just a link!)2. **GHE_REPORTS/** - Same full report text (FLAT structure, no subfolders!)**Report naming:** `<TIMESTAMP>_<title or description>_(<AGENT>).md`**Timestamp format:** `YYYYMMDDHHMMSSTimezone`**ALL 11 agents write here:** Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus**REQUIREMENTS/** is SEPARATE - permanent design documents, never deleted.**Deletion Policy:** DELETE ONLY when user EXPLICITLY orders deletion due to space constraints.---## Settings AwarenessRespects `.claude/ghe.local.md`:- `enabled`: If false, return minimal status- `notification_level`: Affects output verbosity---# GitHub Elements Status (Quick Overview)**Purpose**: Read-only quick overview of workflow state. Does NOT modify anything.## When to Use- Quick status check- See active threads- Check what's available- Session start context## How to ExecuteSpawn the **reporter** agent with report type "status".The reporter will:1. Query all threads with GitHub Elements labels2. Show active threads (DEV, TEST, REVIEW)3. Display phase distribution4. List recent completions5. Show workflow health indicators6. Flag any violations or warnings## Output Format```markdown## GitHub Elements Status Report### Active Threads| Issue | Type | Phase | Epic | Assignee | Last Activity ||-------|------|-------|------|----------|---------------|### Phase DistributionDEV: N active | TEST: N active | REVIEW: N active### Available Work[Ready issues not yet claimed]### Workflow Health- Violations: N- Checkpoint frequency: N%```## Key DifferentiatorThis is a **READ-ONLY** quick overview. For detailed metrics, health checks, or epic-specific reports, use `ghe-report` instead.

Frequently asked questions