openstory-skills

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>".

Coach yourself — honest feedback on how you work with coding agents: prompt quality, recurring failure patterns, and what your work has been pointing at. From your own OpenStory store. Use when the user asks "how am I doing", "feedback on my prompting", "where do I get stuck", "what am I focused on lately", or "coach me".

Report what your AI coding sessions have cost — total spend, cache savings, and a tokens-per-day timeline — from your own OpenStory store. Use when the user asks "what did this cost", "my agent spend", "how much have I spent", "tokens per day", or anything about token usage or cost of coding sessions.

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.

Scan your session history for anything sensitive before you share it — secrets, API keys, credentials, private details — and report a redacted summary. From your own OpenStory store. Use when the user asks "is there anything sensitive in my history", "scan before I share", "any secrets in my sessions", or "check my data before I export it".

Turn today's coding sessions into a standup update — what you did, what's blocked, what's next — from your own OpenStory store. Use when the user asks "write my standup", "what did I do today", "standup", or "summarize today's work".

Find the last time you did or solved something across all your coding sessions, and show how — the exact commands, the session, the date. Use when the user asks "how did I fix X", "did I ever set up Y", "where did I do Z", "find the session where…", or "have we hit this before". Searches the user's own OpenStory store.