body-check

Solid

Compose the AIgent's body state by reading existing signals. Lazy compute. Never polled. Reports the five pressures + recommended reflex.

AI & Automation 11 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
89
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /body-check Reports current body state by reading existing signals — does NOT maintain a separate state. Computed on invocation, optionally cached to `memory/BODY_STATE.json` for the session. ## Sources read - `memory/HEAT_INDEX.json` → attention/decay state - `memory/usage_log.md` → token pressure (latest entry vs trailing 5) - `memory/DECISION_LOG.md` + `DECISION_OUTCOMES.md` → decisions due (30/60/90 day intervals) - `memory/ACTIVE_PRIORITIES.md` → tier-1 / mode - `memory/DELEGATION_TRACKER.md` → open delegations - `memory/MEMORY_CANDIDATES.md` → staged backlog count - `memory/HESTIA_SWEEP_LOG.md` → last Hestia sweep date (v0.4.4) - Comms API → unread count (only if invoked with `--full`) ## Output schema Matches `memory/BODY_STATE.json` `_schema` block exactly. See `system/15_somatic_layer.md` for field definitions and pressure thresholds. ## hestia_last_sweep computation (v0.4.4) Read `memory/HESTIA_SWEEP_LOG.md`. Find the most recent `### YYYY-MM-DD` entry (matches `^### (\d{4}-\d{2}-\d{2})` regex). The newest matching date becomes `hestia_last_sweep` as ISO8601 (`<date>T00:00:00Z`). If no matches, `hestia_last_sweep = null`. ## Recommended reflex logic Priority order — first match wins: 1. `context_pressure: critical` → recommend `capsule` 2. `memory_candidate_backlog > 10` → recommend `digest` 3. `hestia_last_sweep` is null OR more than 7 days ago → recommend `sweep` (v0.4.4) 4. `decision_reviews_due > 0` → recommend (no action, surface in /open) 5. All lo...

Details

Author
wrg32786
Repository
wrg32786/aigent-os
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

bs-check

Use before telling a client or stakeholder "this is fixed", before deploying changes to a production site or service, before activating or modifying a live automation/workflow, before claiming an integration works end-to-end, before quoting pricing or API behavior in a comparison, or before running a destructive infrastructure command. Also use when the user says "confidence check", "how confident are you", "validate this", "pressure-test this", "/bs-check", or whenever a confident-sounding claim has not been directly validated by a query, observation, comparison, or quotable source. ALSO covers design-time reasoning audits via subcommands - "bs-check premise" (are we solving the right problem? premise acceptance - Socratic + Steelman), "bs-check approach" (did we commit too fast? - Burden of Proof, Cold Start, Alternatives, Pre-mortem), "bs-check fresh" (all 9 patterns, fresh-context sub-agent). Trigger phrases for those - challenge this, push back, devil's advocate, poke holes, steelman this, are we solving

0 Updated today
GemSpecter
AI & Automation Solid

heartbeat

Run agent heartbeat — periodic checks, memory consolidation, proactive work. Triggers on /agent:heartbeat, "heartbeat", "heartbeat check", "periodic check", "consolidar memoria".

61 Updated today
crisandrews
AI & Automation Solid

memory-hygiene

Detects "stale-but-confident" memory entries — facts that were once verified but have silently drifted. Scans memory/*.md for entries past their staleness threshold and proposes re-verification or archival. Runs automatically as part of harvest-loop Step 0-c and on explicit invocation.

8 Updated today
chrono-meta