checkup
Skill293 starsChanged 10 days agoMITView on GitHub
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
- Reads credentials
7 other projects use a version of this.
Adopted by
Most recently taken up by
- BermanRoman/promt-seo-geotheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- johnviklund/agent-skillstheir own version, first seen Sep 12, 2026
- rainstorm0907/claude-checkuptheir own version, first seen Aug 12, 2026
- zedarvates/botte-secretetheir own version, first seen Aug 8, 2026
- agentvitals/checkuptheir own version, first seen Jul 28, 2026
Used with
Projects with it also use report.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillreport
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- agentvitals/checkup★ 95same name
- johnviklund/agent-skills★ 2same name
- zedarvates/botte-secrete★ 2same name
- tokyubevoxelverse/checkup★ 1same name
- zedarvates/frugal-skills★ 1same name
- BermanRoman/promt-seo-geo★ 0same name
- rainstorm0907/claude-checkup★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible.
- Very specific: line 25
Use the printed value as {mode}.
- Distinctive: line 28
Run three sequential batches.
- Distinctive: line 34
Never run Connected network probes beside local checks.
- Distinctive: line 39
Read the one typed Runtime health surface as JSON:
- Very specific: line 46
Do not invoke qmd, inspect QMD process tables, guess ports, or read another instance's runtime directory.
- Distinctive: line 69
If the Runtime worker or indexes are unavailable while canonical memory is ready, run the safe Runtime lifecycle adapter once:
- Distinctive: line 97
Do not auto-replace API keys, repair graph state, publish, or send a notification.
- Very specific: line 112
Never mutate Git, canonical memory, or framework files during diagnosis.
- Very specific: line 146
Use ✓, ⚠, and ✗ for pass, degraded, and unavailable.
- Distinctive: line 152
Never expose raw JSON, tokens, environment values, or unformatted probes.
- Distinctive: line 153
Never use Graph or a control-plane response as canonical health authority.
- Very specific: line 154
Never call QMD directly; instance ownership belongs to Egregore Runtime.
- Distinctive: line 155
Never send, publish, commit, pull, or push as part of checkup.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Egregore checkup
Diagnose the Egregore Runtime first. Treat canonical Markdown and its instance-owned Local Retriever as the product baseline. Graph, control-plane, and notification probes are explicit Connected integrations; their failure must never make canonical Local Runtime state look unavailable.
When to invoke
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
Procedure
Detect mode without attempting a network call:
bash bin/config-get.sh modeUse the printed value as {mode}; quote it in single quotes when you use it in a command, and write any single quote inside the value as '\''. If it prints local, skip Connected
integrations; if it prints connected, include them after the local checks.
Run three sequential batches. Parallelize only within a batch.
- Runtime and local configuration.
- Connected integrations, only when
{mode}isconnected. - Workspace and Git checks.
Never run Connected network probes beside local checks; a timeout must not cancel or obscure the Runtime result.
Batch 1: canonical Runtime
Read the one typed Runtime health surface as JSON:
EGREGORE_ROOT="$PWD" PYTHONSAFEPATH=1 PYTHONPATH="$PWD${PYTHONPATH:+:$PYTHONPATH}" \
python3 -m egregore_runtime.harness_cli status --jsonDo not invoke qmd, inspect QMD process tables, guess ports, or read another
instance's runtime directory. The adapter owns those mechanics. Interpret the
returned fields as follows:
canonical_state_ready— foundational. Fail only when canonical memory is unavailable.adapter=qmd-local,collection, andindex_path— the resolved instance-owned Local Retriever. Display these without exposing another instance or deriving ownership yourself.runtime_state,runtime_pid, andruntime_endpoint— owned worker readiness.semantic_readyis healthy;semantic_index_buildingis a warning with lexical fallback;runtime_unavailableis repairable.bm25_ready— local keyword readiness. Warn when false.semantic_readyandembedding_state— semantic readiness. A warming or missing model is degraded, not canonical data loss.index_spec_version,index_revision, andsource_revision— freshness. Report drift; never repair it by editing index files.warnings— show concise, redacted messages.
Also validate egregore.json, the canonical memory link/repository, and the
mode-appropriate key names in .env. Never print secret values. Local mode
requires no control-plane key.
If the Runtime worker or indexes are unavailable while canonical memory is ready, run the safe Runtime lifecycle adapter once:
bash bin/search.sh startThen re-read Runtime health once. This starts or reuses only the worker owned by this Egregore instance and schedules semantic warming behind the adapter.
Batch 2: Connected integrations
Skip this batch completely in local mode. In connected mode, label every row as an integration, keep it outside the foundational Runtime verdict, and run:
timeout 10 bash bin/graph-projection.sh verify --enable 2>&1; echo "EXIT:$?"
timeout 10 bash bin/notification.sh status 2>&1; echo "EXIT:$?"- Hosted relationship index — pass when the gateway accepts the configured credentials and the projection is reachable. Offline, auth, or stale projection results are Connected warnings; canonical Markdown remains authoritative.
- Notification adapter — read the sanitized Runtime
statusfield. Treatok(connected) orconfigured(local) as healthy. Telegram is optional and never part of Runtime readiness.
Do not auto-replace API keys, repair graph state, publish, or send a notification. Report the exact integration boundary that failed.
Batch 3: workspace
Check locally:
- the configured base branch exists and compare it with
origin/<base>only when an origin is already configured; - the current worktree and memory repository are clean or clearly report their dirty-file counts;
- the framework version is readable locally. Do not fetch merely to render a health report;
- the shell launcher points at this instance when a launcher is configured.
Never mutate Git, canonical memory, or framework files during diagnosis.
Offer $pull, $update, or $setup as the next Egregore action when relevant;
do not tell the user to construct repair commands manually.
Rendering
Render one compact diagnostic box. In connected mode add a separate
CONNECTED INTEGRATIONS section after RUNTIME; in local mode omit it.
┌──────────────────────────────────────────────────────────────────────┐
│ ⊕ CHECKUP {date} │
├──────────────────────────────────────────────────────────────────────┤
│ CONFIG │
│ ✓ Instance — {org} ({mode}) │
│ │
│ RUNTIME │
│ ✓ Canonical memory — ready · source {source_revision} │
│ ✓ Local Retriever — qmd-local {adapter_version} · owned │
│ ⚠ Semantic index — warming · lexical fallback ready │
│ ✓ Worker — pid {pid} · {endpoint} │
│ │
│ CONNECTED INTEGRATIONS │
│ ⚠ Hosted relationship index — offline · local memory ready │
│ ✓ Telegram — connected │
│ │
│ WORKSPACE │
│ ✓ Memory repository — clean │
│ ✓ Git — {base} synced │
├──────────────────────────────────────────────────────────────────────┤
│ Runtime ready · {warnings} warnings · integrations {state} │
└──────────────────────────────────────────────────────────────────────┘Use ✓, ⚠, and ✗ for pass, degraded, and unavailable. State the Runtime
verdict independently from Connected integration health. After a safe Runtime
repair, append only the rechecked result.
Rules
- Never expose raw JSON, tokens, environment values, or unformatted probes.
- Never use Graph or a control-plane response as canonical health authority.
- Never call QMD directly; instance ownership belongs to Egregore Runtime.
- Never send, publish, commit, pull, or push as part of checkup.
- Emit telemetry only through the normal command wrapper, best-effort.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

