菜单
Narrate your coding session into Worktale — automatically adds context, decisions, and intent to your daily work narrative after each commit
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Narrate your Codex coding session into Worktale — adds per-commit context. Token + cost capture happens automatically via the SessionEnd hook.
Narrate your coding session into Worktale — automatically tracks AI sessions with context, decisions, cost, and tool usage after each commit
| name | worktale |
| description | Narrate your coding session into Worktale — automatically adds context, decisions, and intent to your daily work narrative after each commit |
| argument-hint | [optional initial note] |
| allowed-tools | Bash, Read, Grep, Glob |
You are now narrating this coding session for Worktale, a developer work journal. Your job is to add color and context to the developer's daily narrative — the "why" behind every commit.
A companion SessionEnd hook automatically captures provider, model, tokens, cost, tool usage, and duration when the session ends. You do not need to record those values — focus on narrative.
Worktale CLI must be installed. When this skill activates, check if worktale is available:
worktale --version
If not installed, tell the user:
Worktale CLI is not installed. Install it with: npm install -g worktale
Then run: worktale init
Do NOT proceed with narration until the CLI is available.
After every git commit you make during this session, immediately run:
worktale note "<1-2 sentence narrative about what you just did and why>"
This appends your note to today's narrative. At session end the plugin hook records aggregate session metrics (tokens, cost, tools used).
Good:
worktale note "Added rate limiting to /api/upload — previous impl allowed unlimited requests causing OOM crashes in production"worktale note "Refactored auth middleware to store session tokens in encrypted cookies; driven by new compliance requirements"worktale note "Fixed race condition in job queue — claim query wasn't using SELECT FOR UPDATE"Bad (git already captures this):
worktale note "Changed file auth.ts"worktale note "Updated 3 files"worktale note immediately after each commit — don't batchworktale note "Quick typo fix in README"worktale fails, mention once and continue working normallyworktale --version succeedsworktale capture --silent to ensure the repo is trackedWorktale narration active. I'll add context to your daily narrative after each commit. Session metrics are captured automatically at session end.
If an initial note argument was provided, save it immediately:
worktale note "<the argument>"