status

memoforge / status skill

Read-only inspection of memoforge task state. Never mutate state.json. Never dispatch worker subagents. Never run python scripts. Only Read and Bash (for ls).

Output format — file references via Cowork artifact cards

This skill is read-only. To give the user clickable access to files, call the Read tool on each file you want to surface — Cowork's UI inserts an artifact card above your next message for any Read tool call, which is the user's clickable affordance. Then print plain-text paths in the report body so the user knows where things live on disk.

Path display in chat text uses state.json.rel_work_dir (canonical CWD-relative path field set by skills/memo/SKILL.md Phase 1 Task setup). If a legacy task is missing this field, compute it on the fly via:

REL_WORK_DIR=$(realpath --relative-to="$(pwd)" "$WORK_DIR" 2>/dev/null \
  || python3 -c "import os.path,sys; print(os.path.relpath(sys.argv[1]))" "$WORK_DIR" 2>/dev/null \
  || python  -c "import os.path,sys; print(os.path.relpath(sys.argv[1]))" "$WORK_DIR" 2>/dev/null \
  || echo "$WORK_DIR")

(This skill is read-only — do NOT write the recomputed value back to state.json; just use it inline for the chat output.)

Do not wrap file paths in markdown link syntax. Cowork does not render relative or absolute paths as clickable file references inside chat text — clickability comes from the Read tool's artifact cards. Print all paths as plain text and rely on the Read calls for click access.

Parse argument

Read $ARGUMENTS.

Empty argument — list all tasks

1. Scan the four canonical output-folder candidates (same resolution order as skills/continue/SKILL.md Task discovery): $CLAUDE_PLUGIN_OPTION_OUTPUT_FOLDER, $MEMOFORGE_OUTPUT_FOLDER, $HOME/Documents/memoforge, outputs/memoforge-work. For each parent that exists, run ls "$parent"/memo-* 2>/dev/null and collect unique task_id directories (a task_id appearing in two parents is deduped, but record the resolved parent path per task).
2. For each found memo-* directory:
   • Read state.json.
   • Extract task_id, current_phase, created_at, user_query (first 100 chars), final_status if set, and rel_work_dir (compute if absent).
3. For each found task, call Read on <resolved_path>/state.json — Cowork will insert an artifact card so the user can click to inspect each one.
4. Then print a plain-text table summarizing what was read:

   | task_id                                          | phase                  | created             | query                                | path                          |
   |--------------------------------------------------|------------------------|---------------------|--------------------------------------|-------------------------------|
   | memo-2026-05-14T10-30-00-gdpr-biometrics-minors  | revision_loop          | 2026-05-14 10:30:00 | Can our product process biometr...   | <rel_work_dir>/                |