Jason Stedwell
55afdce70c
Skills migration: each of the eight slash commands gains a skills/<name>/SKILL.md twin (same invocation name, byte-identical body). Per-skill allowed-tools pre-authorize the resolved python3/python/py -3 invocations + the CoWork ls fallback probe; disable-model-invocation: true makes /echo-sweep and /echo-triage operator-only. Docs-confirmed: a same-name skill takes precedence over the legacy command, so commands/ coexists until its scheduled 2.0 deletion. The $ECHO path-resolution dedupe is resolved as not-supported (skill dirs are self-contained; no cross-skill snippet sharing). Lint fix: vault_lint.py checks retired patterns BEFORE routes, so a seed README inside a retired tree (archive/...) flags retired-path instead of being absolved by the permissive leaf-readme route. New end-to-end regression test seeds archive/notes/README.md (fails pre-fix, passes now). plugin.json: version 1.6.0, homepage + repository -> git.alwisp.com/jason/echo. All suites green: 25/25 client unit tests (incl. routing-sync guard), feature, reflect, offline-queue, PATCH-semantics. Artifact rebuilt (87 entries, both formats); pointer refreshed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
name, description, allowed-tools, disable-model-invocation
| name | description | allowed-tools | disable-model-invocation |
|---|---|---|---|
| echo-triage | Triage the ECHO inbox — route aging captures to their canonical homes and log the moves | Bash(python3 *echo.py*), Bash(python *echo.py*), Bash(py -3 *echo.py*), Bash(ls /sessions/*) | true |
Use the echo-memory skill to run one-tap Inbox Triage via the triage verb (it reuses the reflect pipeline: classify against the entity index → preview → apply via capture, and writes the audit log for you).
ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py"
[ -f "$ECHO" ] || ECHO=$(ls /sessions/*/mnt/.remote-plugins/*/skills/echo-memory/scripts/echo.py 2>/dev/null | head -1) # CoWork sandbox fallback
python3 "$ECHO" triage --list --json
# Windows: use `python` or `py -3` if `python3` is not on PATH.
- List — the JSON gives each capture as
{line, date, text, age_days}. Surface the aging ones (≥ ~7 days) to the operator and ask which to route. - Propose — for accepted items, write a proposals JSON with the Write tool (reflect schema:
{"title","kind","body",...}plus"line": the original inbox line, echoed into the audit log). Route per the map: preference/pattern →semantic(or a direct PATCH tooperator-preferences.md::Observations); project idea →projectwith--status incubating; durable fact →semantic; person fact →person. - Preview, then apply with the operator's go-ahead:
python3 "$ECHO" triage proposals.json # dry-run: classify + preview, writes nothing
python3 "$ECHO" triage proposals.json --apply # route via capture + log each move
--apply records every move in inbox/processing-log/YYYY-MM-DD.md (- <original> → <destination>) automatically. Do not delete the original captures unless the operator explicitly asks — the processing log is the audit trail. A proposal that stops at the duplicate gate (exit note in the summary) should be re-proposed with the existing entity's title.