菜单
Read and update Sessio thread/stage work state from an agent session. Use this when working inside a Sessio thread or stage, reporting progress, marking work blocked/completed, or managing structured stage issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create Sessio teamwork, workflow/process, brainstorm, or debate threads from a natural-language description. Use this skill whenever the user asks to set up, design, create, scaffold, or coordinate a Sessio thread/workflow. The skill must use the Sessio CLI for thread creation, assistant creation, and process-stage creation, while respecting each thread kind's structure: process uses stages, teamwork uses thread-level assistants without stages, and brainstorm/debate use participant-style lanes without stages.
macOS desktop automation — click, right-click, type, key combos, scroll, drag, and screenshot other apps (Notes, Music, Notion, Slack, 网易云音乐…). Works on apps with rich AX trees AND apps that expose no AX (Qt, custom-drawn, AX-disabled) by falling back to pixel-coordinate CGEvent dispatch. Use when the user asks Sessio to interact with a native Mac app. Not for web pages (use the `browser` skill for those).
Read and update Sessio thread/stage work state from an agent session. Use this when working inside a Sessio thread or stage, reporting progress, marking work blocked/completed, or managing structured stage issues.
Search and resolve project-level Sessio session memory. Use this whenever the user asks about prior project discussions, previous agent sessions, historical decisions, implementation context, qmd memory, or "what did we decide before" in a Sessio-enabled workspace.
| name | sessio-work-state |
| description | Read and update Sessio thread/stage work state from an agent session. Use this when working inside a Sessio thread or stage, reporting progress, marking work blocked/completed, or managing structured stage issues. |
Use the Sessio CLI as the source of truth for thread/stage progress. Agents should update work state with non-destructive commands instead of only describing progress in chat text.
The app exposes the CLI at:
~/.sessio/bin/sessio
If sessio is already on PATH, either form is acceptable. Prefer --json for commands you need to parse.
When a thread/stage chat injects a threadStageId, use that id for progress writes:
sessio stage set-status --id "<threadStageId>" --status in_progress --json
sessio stage update --id "<threadStageId>" --summary "what has been done" --json
sessio stage set-status --id "<threadStageId>" --status completed --outcome "final result" --json
Valid stage statuses:
not_started
in_progress
blocked
needs_review
completed
skipped
Use blocked when progress cannot continue without a decision, missing input, failing dependency, or external state change:
sessio stage set-status --id "<threadStageId>" --status blocked --summary "what is blocking" --json
Issues are structured stage records. Add one when a blocker or risk should be tracked separately from summary/outcome:
sessio stage issue add --stage-id "<threadStageId>" --title "short issue title" --severity high --description "what is blocked and why" --json
List and update issues:
sessio stage issue list --stage-id "<threadStageId>" --json
sessio stage issue set --id "<issueId>" --status resolved --json
sessio stage issue set --id "<issueId>" --status dismissed --json
Valid issue statuses are open, resolved, and dismissed.
Valid severities are low, medium, high, and critical.
Read thread/stage state before making a judgement:
sessio thread show --id "<threadId>" --json
sessio stage list --thread-id "<threadId>" --json
sessio stage show --id "<threadStageId>" --json
delete; use stage issue set --status dismissed instead.~/.sessio/bin/sessio.