AGENT SKILL
back
Resume after away mode.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 4
- Forks
- 1
01 前言 Front Matter
- name
- back
- description
- Resume after away mode.
- allowed-tools
- [ "Bash", "Read", "Grep" ]
- user-invocable
- true
03 SKILL.md 正文
back — end the away grant
The explicit counterpart to away: revoke that
session-scoped grant right now and hand the user a scannable record of what
happened while it was active, instead of leaving them to reconstruct it from
the transcript.
away itself already says the grant is "revocable immediately" on any
"stop"/"ask me from now on" — back is the named form of that
revocation, worth its own trigger so it's easy to invoke without recalling
the exact wording away documents.
When this fires
- "back", "I'm back", "I'm back now"
- "stop away mode", "end away mode", "cancel away", "turn off away"
- "ask me again", "you can ask me questions again"
Procedure
- Check whether
awayis actually active this session. If it was never granted (or was already revoked), say so in one line and stop — nothing to cancel, no decision log to show. - Revoke the grant immediately. From this point on, a judgment call
that
awaywould have resolved unattended goes back to being a normal blocking question (or anAskUserQuestionprompt), exactly as ifawayhad never been invoked. - Surface the decision log
away's procedure asked you to keep — every judgment call resolved on the user's behalf (what the question was, what you decided, why, whether a stronger model was consulted) and every candidate skipped or deferred as too ambiguous to guess at. This is the whole point ofback: hand back a reviewable list, not just a "done, trust me." If the log is empty (no judgment calls actually came up whileawaywas active), say that plainly instead of padding the report. - Point out anything still open. A skipped/deferred item from the log
is now fair game to resolve normally — ask about it, or use
prompt-me/prompt-me-allif there are enough of them that a single inline recap would be unwieldy. - Leave
mwc(or any other separately-granted permission) untouched.backonly cancelsaway's question-suppression grant. If the user also wants to revoke merge authority or another standing permission granted separately this session, that needs its own explicit phrase (mwc's own "stop merging on your own") — don't silently bundle it in.
Relationship to other skills
away— the grant this cancels. Read that skill's Scope and limits and Procedure sections for exactly what was suppressed and what log format to expect;backdoesn't duplicate that content here.prompt-me/prompt-me-all— the right tool oncebackhas surfaced a skipped/deferred list longer than fits in a quick recap;back's own job is producing that list, not re-implementing the sweep-and-restate mechanics those skills already own.mwc— a separate, narrower session-scoped grant (merge authority only) with its own revocation phrase;backdeliberately doesn't touch it, per Procedure step 5.
Anti-patterns
- ❌ Treating
backas a no-op status check — it must actually revoke the grant, not just report on it. - ❌ Reporting "done, all clear" with no decision log when
awaywas active and judgment calls did come up — the log is the deliverable. - ❌ Silently also revoking
mwcor another unrelated grant because it happened to be active alongsideaway. - ❌ Fabricating log entries when nothing was actually decided unattended — an honest "nothing came up" beats padding the report.
04 同仓库更多 Skills
wrap-up
End-of-session verification and UMS.
★ 4
workaround-watcher
Watch upstream issue for fix.
★ 4
wn
→ whats-next.
★ 4
whats-next
Recommend concrete next step or action.
★ 4
wait-for-results
Wait for pipeline/CI results.
★ 4
wai
→ send-notes.
★ 4