agentleFS
Sign inStart free
wrg32786wrg32786/aigent-os/skills/system-check/SKILL.md

system-check

Skill25 starsChanged 8 days agoMITView on GitHub

Run read-only installation smoke tests for skills, daemons, memory, runtime, freshness, and routes. Use when verifying an install or checking aigent-OS health.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run from the aigent-OS root:

    line 20
  2. Very specific:

    Every nightly daemon exists and passes node --check.

    line 49
  3. Distinctive:

    All date-sensitive checks use one timezone and one cutoff:

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/system-check

Run from the aigent-OS root:

bash daemons/system-check.sh

The script is read-only. It prints one line per check, a final SUMMARY: N PASS / N FAIL / N INFO, and exits 1 when any check fails.

Path resolution

Framework code resolves from AIGENT_ROOT, defaulting to the parent directory of daemons/system-check.sh.

Operational memory resolves in this order:

  1. AIGENT_STATE_HOME_DIR/vault/memory when the state-home diversion is set.
  2. AIGENT_STATE_HOME_DIR/memory as a compatibility fallback.
  3. AIGENT_ROOT/vault/memory for a normal installation.
  4. AIGENT_ROOT/memory only when the canonical vault path does not exist.

This is the same shape used by the nightly controller. Tests should set AIGENT_ROOT, AIGENT_STATE_HOME_DIR, and date-sensitive environment values explicitly so ambient state cannot change the result.

Checks

  • Required top-level skills exist, including the nightly close-parity skills.
  • Shell and Python daemons parse.
  • Every nightly daemon exists and passes node --check.
  • The memory-heat daemon parses.
  • Operational state files have their required schemas, including the generic sweep log and dispatch-fitness table.
  • Capsules have valid frontmatter, identity, and status.
  • Canonical cognitive JSON and JSONL inputs exist and parse. Missing canonical input is a failure, not an empty-success case.
  • DREAM_LOG.md freshness comes from its newest valid dated header, never its file modification time.
  • The newest NIGHTLY_LOG.md pass is current and has complete terminal evidence. A terminal status: FAIL remains red even when every checkpoint row is present.
  • /nightly resolves through the unique /nightly-close-parity route.
  • The eval directory contains at least one supported file.
  • The local daemon error log is surfaced as INFO when it contains entries.

Date configuration

All date-sensitive checks use one timezone and one cutoff:

export AIGENT_NIGHTLY_TIME_ZONE="America/Los_Angeles"
export AIGENT_NIGHTLY_CUTOFF_HOUR="4"
bash daemons/system-check.sh

America/Los_Angeles and hour 4 are the defaults. Tests may pin the current instant with AIGENT_SYSTEM_CHECK_NOW.

What it does not do

  • It does not repair files or resolve alerts.
  • It invokes the route checker with alerts disabled.
  • It invokes the watchdog in check-only mode, so /system-check never appends to the nightly alert ledger.
  • It does not inspect a message bus, task board, browser profile, or private machine configuration.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free