user-wraplisted

The return-moment front door — invoke when sitting back down at an open window: 'sitting back down', 'should I keep going or wrap up', 'am I safe to close this window', back-from-lunch or next-morning re-entry. Despite the name, the most common verdict is KEEP GOING — this skill serves the whole return moment, not just closing. Orients from current.md + git (task-handoff --resume's shape), delegates the verdict to /session-wrap --advise (the one triage owner), re-presents its verdict banner + loss report front and center, then acts per verdict. NOT for mid-task transition moments (use bare /session-wrap) or checkpoint-only writes (use /task-handoff --loop).
aberson/skill-mesh · ★ 2 · AI & Automation · score 71

Install: claude install-skill aberson/skill-mesh

# user-wrap A THIN front door for the sit-back-down moment. The operator has been away — lunch, overnight, a context switch — and wants one answer before touching anything: keep going, recycle the window, wrap it, or just close it? This skill composes three existing contracts and owns ZERO triage logic of its own: - **Orientation shape** — `/task-handoff --resume` ([`../task-handoff/SKILL.md`](../task-handoff/SKILL.md) § `--resume` — in-window orient). - **Verdict + loss report** — `/session-wrap --advise` ([`../session-wrap/SKILL.md`](../session-wrap/SKILL.md) § `--advise` — verdict + loss report) is the ONE owner of triage: signal collection, route scoring, the read-only salvage preview, the 4-verdict banner (KEEP GOING / RECYCLE WINDOW / WRAP & CLOSE / SAFE TO CLOSE), and the two-line loss report. - **State fields** — `current.md` format, field semantics, path resolution, and staleness are owned by `.claude/references/task-state-schema.md` (workspace reference, not published in this mirror) (cite it, never restate it). **Defect clause.** Any triage constant appearing in this file or in user-wrap-authored output prose — a token threshold, a context ceiling, a staleness window, a route-scoring rule — is a DEFECT. Those numbers live in session-wrap's threshold table and the task-state schema doc; they reach user-wrap's output only inside the verbatim re-presented `--advise` report, never as this skill's own reasoning. --- ## When to use / when NOT to us