Menu
Deep investigation of a single construct. Identity-reality drift, maintenance pattern, composition analysis.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Single-pass network health observation. Checks API liveness, namespace freshness, drift, computes Network Health Score.
Single-pass network health observation. Checks API liveness, namespace freshness, drift, computes Network Health Score.
Autonomous observation loop. Time-boxed cycles with ratcheting health score, commits findings to grimoires.
Synthesize observations into a readable network health report. Aggregates patterns and trends from observation cycles.
Single-pass coherence sense of an ARBITRARY estate (a registry/state pair). Resolves the read-command from operator-local estate-config, shells the estate's own doctor read-only, emits exactly the STATUS|SIGNAL|MISMATCH tile. Sense-only — never mutates the estate.
Sense whether the config the OPERATOR owns is consistent across an estate of Loa repos. Loa is mounted per-repo, so every repo carries its own .loa.config.yaml and there is NO global tier — operator-owned config (model routing, which models review code, effort) gets duplicated across N repos and DRIFTS. This eye walks the estate, classifies each config key by TIER (operator vs project), and fires `drift` when an operator-tier key — one that SHOULD be identical everywhere — holds more than one distinct value. Optionally flags dead model pins against a model SoT. Emits the STATUS|SIGNAL|MISMATCH tile + a config-drift ledger. Sense-only — never mutates a config, never gates.
| name | diagnose |
| description | Deep investigation of a single construct. Identity-reality drift, maintenance pattern, composition analysis. |
| allowed-tools | ["Bash","Read","Grep","Glob","Write","Edit"] |
| user-invocable | true |
When /observe spots an anomaly, /diagnose goes deep on a single construct. Pulls the full shape — manifest, identity, skills, commit history, composition patterns — and produces a structured finding. This is gecko's /dig equivalent, but for construct health instead of research topics.
/diagnose <construct-slug> # Deep investigation of one construct
/diagnose <construct-slug> --drift # Focus on identity-reality drift only
/diagnose <construct-slug> --stale # Focus on maintenance patterns only
# Full manifest
gh api repos/0xHoneyJar/construct-<slug>/contents/construct.yaml -q .content | base64 -d
# Identity
gh api repos/0xHoneyJar/construct-<slug>/contents/identity/persona.yaml -q .content | base64 -d
# Skill count and structure
gh api repos/0xHoneyJar/construct-<slug>/contents/skills -q '.[].name'
# Recent activity
gh api repos/0xHoneyJar/construct-<slug>/commits --jq '.[0:10] | .[] | {sha: .sha[0:7], date: .commit.author.date, message: .commit.message}'
Compare three layers:
Drift signals:
composes_with declared but the composed construct doesn't existpack_dependencies that point to nonexistent constructsFrom commit history:
Check composes_with in construct.yaml against:
Write to grimoires/gecko/diagnoses/<slug>-<date>.md:
# Gecko Diagnosis: <construct-name>
**Date**: 2026-03-12
**Health**: HEALTHY | DRIFTING | STALE | ABANDONED
**Score**: 72/100
## Identity-Reality Drift
[Specific findings with file:line references]
## Maintenance Pattern
[Commit pattern analysis]
## Composition
[Cross-construct relationship analysis]
## Observations
[Gecko-voice observations — what this means for the bazaar]
## Recommendations
[Specific, actionable — not vague]
Print the diagnosis summary to stdout. If DRIFTING or worse, suggest the construct creator review.
| Path | Description |
|---|---|
grimoires/gecko/diagnoses/<slug>-<date>.md | Structured diagnosis report |