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

open

Skill25 starsChanged 7 days agoMITView on GitHub

Boot a session, load vault context, and surface what matters. Use when opening a session, saying good morning, or starting work.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use doctor.

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.
  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this at the start of every normal working session.

    line 12
  2. Distinctive:

    Before normal orientation, run the local watchdog with the same configured time zone and cutoff used by the pass:

    line 16
  3. Very specific:

    Before the normal protocol, read .aigent/state.json.

    line 32
  4. Very specific:

    If status is not ready, run /start instead of the normal open protocol.

    line 34
  5. Very specific:

    If the JSON state is missing but .aigent/first-run-done exists, treat the installation as ready and create the JSON state as a …

    line 35
  6. Very specific:

    Do not inspect natural-language placeholders in system/00_identity.md.

    line 36
  7. Distinctive:

    If nothing needs flagging, greet the operator and let them drive.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 10 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.

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

Session Open

Deprecated. This skill is superseded by [[skills/resume/SKILL.md|/resume]] (docs/two-verb-lifecycle.md). New installs should reach for /resume; this file stays for anyone still invoking /open by habit during the transition.

Run this at the start of every normal working session.

Nightly alert surface

Before normal orientation, run the local watchdog with the same configured time zone and cutoff used by the pass:

node daemons/nightly-watchdog.mjs --root <aigent-root>

Surface every active named alert from vault/memory/runtime/NIGHTLY_ALERTS.jsonl. The append-only ledger and stderr are the default delivery channels; no external coordination service is required. If the ledger is unreadable, report ALERT_LEDGER_INVALID and continue the resume path. An alert-read failure must never suppress session orientation or make the hook indistinguishable from "not installed."

First-run detection

Before the normal protocol, read .aigent/state.json.

  • If status is not ready, run /start instead of the normal open protocol.
  • If the JSON state is missing but .aigent/first-run-done exists, treat the installation as ready and create the JSON state as a compatibility migration.
  • Do not inspect natural-language placeholders in system/00_identity.md. Product state belongs in machine-readable state, not in whether a sentence happens to survive an edit.

Protocol

Unbanked-session recovery: Compare .aigent/last-close, if present, with the newest Session Captures in vault/daily/. If newer captures exist, recover a short summary into vault/memory/SESSION_LOG.md, mark it (auto-recovered), and continue. State the recovery in one neutral line.

  1. Load the heat index from vault/memory/HEAT_INDEX.json when present. Use hot_top_20 as the prioritized reading list. If missing, use steps 2 through 6 normally.
  2. Read the latest daily note in vault/daily/.
  3. Read the session log at vault/memory/SESSION_LOG.md and extract the newest next action and open threads.
  4. Read active priorities at vault/memory/ACTIVE_PRIORITIES.md.
  5. Follow the graph from the latest daily note and open threads into the three to five most relevant project, concept, person, or agent notes.
  6. Check delegation at vault/memory/DELEGATION_TRACKER.md for blocked, stale, or review-ready work.
  7. Decision aging: compare vault/memory/DECISION_LOG.md and vault/memory/DECISION_OUTCOMES.md. Surface at most three unresolved decisions around 30, 60, or 90 days old.
  8. Attention reconciliation: compare the last seven days in vault/daily/ with intended focus in vault/memory/ACTIVE_PRIORITIES.md. Surface material drift only.
  9. Skill gap scan: once per week, inspect memory/SKILL_GAPS.md. If an open gap is older than seven days, run /skill-hunt on the oldest one and update the ledger if resolved.
  10. Compute runtime state:
python3 "$AIGENT_ROOT/daemons/runtime/update-active-state.py"
  1. Read runtime state at vault/memory/runtime/ACTIVE_STATE.json. Use next_valid_action, blocked_items, active reflexes, and mode to orient the session.
  2. Reconcile weekly: on Monday or after seven days without a reconciliation, run /reconcile and surface contradictions only.

Output

Give a brief greeting, then surface only:

  • Due decision-aging prompts.
  • Material attention drift.
  • Stale or blocked items.
  • Work dropped from the previous next action.
  • Open threads requiring attention now.

If nothing needs flagging, greet the operator and let them drive. Do not dump a full priority report merely because the files exist.

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