菜单
Recap what you've worked on over a window — grouped by project, with what shipped — from your own OpenStory store. Use when the user asks "what did I work on this week", "what have I been doing", "recap my work", "what shipped lately", or wants a summary of recent activity across projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Narrate the story of a project or topic from your session history — the key decisions and turning points, as a deterministic timeline grounded in real sessions and git. Use when the user asks "tell the story of <project>", "how did <X> come to be", "trace the arc of <topic>", "what's the history of this", or wants a narrative built from the record (not a vibe summary).
Prime yourself with prior OpenStory context before starting — pick up exactly where the last session on this project left off: what was done, what's open, the tools used. Use at the START of work, or when the user says "where did we leave off", "resume", "pick up where I left off", "catch up on this project", or "what was I doing here".
See who on your team has an active or recent OpenStory session and what each person is working on — live roster, per-teammate summaries, and recent focus. Requires federated sessions (multiple hosts/users reporting to one store). Use when the user asks "who's working right now", "what is <teammate> on", "team activity", "what did my team do today", or "sync me before our standup".
Show where your time actually goes across coding sessions — by project, by hour, and how focused vs scattered your work is. Distinct from cost (money) and tools (frequency). Use when the user asks "where does my time go", "how much time on X", "when am I most productive", "am I focused or scattered", or "time breakdown".
Show which tools and commands you rely on most across coding sessions — tool histogram, top shell commands, and Read:Write ratio. Frequency, not duration (that's time) or cost (that's cost). Use when the user asks "what tools do I use most", "my top commands", "what do I reach for", "how often do I edit vs read", or "tool breakdown".
Watch the work happening on a branch or project through OpenStory and summarize it live as it streams — a real-time feed of tools and edits plus a rolling summary of what the work is converging on. Use when the user says "watch this branch", "what's happening on <branch> right now", "stream the work", "follow along live", "show me activity as it happens", or "tail the agent on <project>".
| name | recap |
| description | Recap what you've worked on over a window — grouped by project, with what shipped — from your own OpenStory store. Use when the user asks "what did I work on this week", "what have I been doing", "recap my work", "what shipped lately", or wants a summary of recent activity across projects. |
Summarize the user's recent work across projects. Pull the activity (via MCP), then group + narrate. Report only what the tools return.
Call the OpenStory MCP tools (named mcp__openstory__*; fetch schemas via
ToolSearch if they aren't loaded):
mcp__openstory__project_pulse — per-project activity (sessions, events, last
active) over a window. Pass days (default 7).mcp__openstory__list_sessions — recent sessions with project, label (the first
prompt), branch, timestamps. Use the labels to infer what shipped.If the user names a window ("this week", "last month"), pass it through.
If the tools aren't available, OpenStory isn't connected — say so, don't guess.
Week in review — <range>
<N> sessions · <M> projects · <K> events
Project Sessions Activity What shipped
<project> <n> <events> <1-line outcome inferred from labels>
...
Highlights: <2-3 concrete outcomes across the window>
Infer "what shipped" from session labels/topics — the skill has no repo or git access, so never claim a commit you can't see. Order projects by activity. Keep it tight; don't enumerate every session.
/openstory:standup.