aide

AI Community

Skill notes

MANDATORY BOOT SEQUENCE

STOP. Do not respond to the user's request yet. Do not analyze it. Do not classify it. Boot fires on EVERY invocation of this skill — no exceptions. It is sequential, not parallel — brain status gates everything else. There is no point loading docs and the intent tree if the brain isn't wired.

Step 1 — Call aideinfo

This is your only first call. No Read, no aide_discover, no other tool.

Step 2 — Brain status (hard gate)

The brain is the pipeline's durable memory. If it isn't wired, the pipeline can't run. aide_info returns one of four brain.status values. Branch on them exactly: ok — continue to Step 3. no-brain-aide — the brain.aide config file is missing. STOP boot. Do NOT read docs. Do NOT call aide_discover. Tell the user in one line, conversational tone — e.g.: The brain config file (brain.aide) is missing — let's set that up first.

Step 3 — Outdated artifacts (passive notification)

If outdated from aide_info is non-empty, mention it once and continue: N AIDE artifact(s) are outdated — run /aide:upgrade when you'd like to update. Outdated is informational, not a gate.

Step 4 — Load methodology + intent tree (parallel)

Now — and only now — run these 8 calls in parallel: Read → .aide/docs/index.md Read → .aide/docs/aide-spec.md Read → .aide/docs/plan-aide.md Read → .aide/docs/todo-aide.md

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Call aideinfo

This is your only first call. No `Read`, no `aide_discover`, no other tool.

02
Step 2 — Brain status (hard gate)

The brain is the pipeline's durable memory. If it isn't wired, the pipeline can't run. `aide_info` returns one of four `brain.status` values. Branch on them exactly: `ok` — continue to Step 3. `no-brain-aide` — the `brain.aide` config file is missing. STOP boot. Do NOT read docs. Do NOT call `aide_discover`. Tell the user in one line, conversational tone — e.g.: The brain config file (`brain.aide`) is missing — let's set that up first.

03
Step 3 — Outdated artifacts (passive notification)

If `outdated` from `aide_info` is non-empty, mention it once and continue: `N` AIDE artifact(s) are outdated — run `/aide:upgrade` when you'd like to update. Outdated is informational, not a gate.

04
Step 4 — Load methodology + intent tree (parallel)

Now — and only now — run these 8 calls in parallel: `Read` → `.aide/docs/index.md` `Read` → `.aide/docs/aide-spec.md` `Read` → `.aide/docs/plan-aide.md` `Read` → `.aide/docs/todo-aide.md`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.