GhostlyGawd
- 27 skills
- 0 followers
- 7 hours ago last updated
- ▌ Lab · ghostlygawd bundleEXPERIMENTAL. Preview 2–4 alternatives or a measurable roadmap without changing the project. Use for low-cost incubation, preview-only brainstorming, or roadmap drafting with exact-target approval before any later action. Do not use when the user explicitly invokes the standalone brainstorm skill or requests independent parallel candidates; do not use as build or mutation authority.
- ▌ Guard · ghostlygawd bundleConfigure or explain Recursive Guard, a separately trusted Codex plugin that is inert unless a repository explicitly adds a reviewed .recursive-guard.json policy. Use when a user wants opt-in protection for instruction, provider, hook, or other sensitive repository paths without replacing existing agent configuration.
- ▌ Learn · ghostlygawd bundleCapture corrections and follow-ups in private local state, select a compact retrospective, inspect promotion candidates, or emit a review-only learning diff. Use when a user corrects an agent, asks to remember a workflow lesson, requests a retrospective, or wants to improve reusable instructions without silently changing the current repository.
- ▌ Verify · ghostlygawd bundleProduce a deterministic structural scorecard, run a fixed Atlas-style query, inspect an eval corpus without executing repository code, or emit a review-only proposal diff. Use when a user asks for portable evidence about a repository, its tests or instructions, eval-corpus health, or a proposed verification change without modifying the project.
- ▌ Observe · ghostlygawd bundleRecord falsifiable predictions, score outcomes, inspect calibration and a compact scorecard, or audit/delete Recursive Observe's private local evidence. Use when a user asks to track whether an agent task succeeds, measure confidence, review prediction accuracy, or manage Observe data without changing the current repository.
- ▌
- ▌
- ▌
- ▌ Coordinate · ghostlygawd bundleCoordinate concurrent agents through collision-safe local claims, bounded leases, idempotent handoffs, and a read-only Mission projection without changing the project or contacting an external service. Use when multiple sessions or worktrees need explicit ownership and handoff evidence.
- ▌ Auto Healer · ghostlygawd bundleUse the moment you fix a bug, see a failure recur, or are about to re-fix code you've touched before. `heal.py fix` logs the bug + scored attempt in ONE call (the low-friction primary path); `heal.py match` recalls prior FALSIFIED hypotheses for a file/error before you re-fix, so you don't re-derive dead ends. A per-repo bug+attempt ledger keyed by cwd makes a root defect resurfacing 'in a different shape' visible across sessions. Pull the web via /heal — never pushed. Pairs with stuck-detection (the in-session ladder); this is the cross-session memory.
- ▌ Calibration · ghostlygawdPredict-then-score protocol. Use at the START of any non-trivial task (multi-file change, debugging session, design decision, anything you could be wrong about) to log a falsifiable prediction, and at the END to score it. Also use when the user asks "how confident are you", when choosing between approaches, or when /calibrate reports overconfidence in a category. This protocol IS the harness's verified self-awareness; skipping it makes your judgement unmeasurable.
- ▌ Eval Capture · ghostlygawdSnapshot a just-completed task into the regression corpus (evals/corpus/). Use after any task where the user accepted the result AND future harness changes could plausibly regress it — recurring task shapes, tasks that needed corrections before acceptance, anything involving taste the user articulated. Also use when /meta-retro reports a category with misses but no eval coverage. Without corpus growth, "harness improvement" is unmeasurable drift.
- ▌
- ▌ Retrospection · ghostlygawdThe learning-extraction procedure behind /retro and /meta-retro. Use when a significant task completes, when the Stop gate or 3-corrections nudge fires, when the user expresses frustration or strong approval, or when you finish anything you'd handle differently next time. Converts session experience into reviewed harness diffs — this is the ONLY mechanism by which the system improves, so under-triggering it means not learning.
- ▌ Structural QA · ghostlygawdUse to answer a question about how THIS harness is wired — "what enforces / guards X", "how does Y work", "what depends on Z / what breaks if I change it", "is there a path from A to B", "what's orphaned or load-bearing", "which spec governs FILE". Answer by traversing the cartograph graph (cartograph/extract.py --query / --context), citing the file each result names (Read it to pin the line), NOT by grepping. The harness is wired by lifecycle triggers + settings.json + /cmd pointers, which an import-grep misses but the graph models. Read-only.
- ▌
- ▌
- ▌ Specialization · ghostlygawd bundleUse immediately when no installed skill covers a reusable domain, or when feedback, a mistake, or a better process reveals that an existing skill is incomplete or wrong. Record the first observation, create or amend a private candidate, and dogfood it on the triggering case now. Follow provenance to improve the canonical skill instead of forking it. Recurrence strengthens evidence but never delays a proven correction.
- ▌ Stuck Detection · ghostlygawdUse the moment the same error, test failure, or rejection happens TWICE in a row, when you notice retry-with-minor-variation behavior, when elapsed effort is 2x your prediction, or when you're about to try the same approach "one more time but harder". Encodes the stop/strategy-switch/escalate ladder. Trigger proactively — by the third identical failure you are burning context and user trust.
- ▌
- ▌ Harness Authoring · ghostlygawdStandards for writing or modifying the harness's own artifacts — skills, commands, agents, hooks, user-model entries. Use whenever /retro routes a learning into a new or edited artifact, when promoting a project-level learning upstream, or when refactoring existing skills. Encodes budgets, provenance, falsifiability, and the duplication check. Writing an artifact without this skill produces lint failures and junk-drawer drift.
- ▌ Routing Learnings · ghostlygawdThe anti-auto-memory router. Use this EVERY time you notice something worth remembering — a repeated mistake, a user correction, a procedure that worked, a preference, a project quirk — and especially whenever you feel the urge to "just note this down" in CLAUDE.md or memory. Also use during /retro to classify each mined learning. Routing prose into the wrong artifact is the primary failure mode of this harness; when in doubt, trigger this skill.
- ▌ Follow Up Handling · ghostlygawdUse at the END of any task that generated deferred work — the "next steps", "you could also", "want me to…", unfixed-nit, or parked-for-later items. Instead of reciting them at the user (which overloads them — their stated correction), capture each via `harness followup add` and end with a single count line. Also use when the user says follow-ups overwhelm them, or asks to defer/park something. Surfacing the list is always a PULL (/followups), never a push.
- ▌
- ▌ Windows Host Paths · ghostlygawdWindows host paths — the space in `D:\GitHub Projects\…` defeats naive parsers
- ▌ Host Assumption Bleed · ghostlygawdUse when designing or building a NEW project/system FOR the user — especially anything described as autonomous, self-governing, agentic, or self-improving. THIS harness's governance invariants (human-in-the-loop approval, a write-locked enforcement layer only a human PR may change, human-seeded work) are facts of the recursive-harness repo, NOT universal best practice. Importing them by reflex can negate a sub-project whose premise is autonomy. Before designing a sub-project's governance/safety, confirm whether a human gate is a real requirement or a cage you're copying.
- ▌