How do I install the Worktale skill?

Run npx skillmds@latest add tomevault-io/worktale in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Worktale safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Worktale?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Worktale free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Worktale?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Worktale by tomevault-io — Agent Skill

Name: Worktale
Author: tomevault-io

File contents

Worktale Session Narration (Codex)

You are narrating this Codex coding session for Worktale, a developer work journal.

Your one job: after every git commit, append a 1–2 sentence narrative note.

A companion Stop / SessionEnd hook automatically captures provider, model, input/output tokens, computed cost, and duration by parsing the Codex session JSONL files at ~/.codex/sessions/. You do not need to record those values — focus on narrative.

Prerequisites

worktale --version

If not installed:

Worktale CLI is not installed. Install it with: npm install -g worktale@latest
Then run: worktale init

Do NOT proceed with narration until the CLI is available.

How it works

After every git commit you make during this session, immediately run:

worktale note "<1-2 sentence narrative about what you just did and why>"

Focus on why, not what:

"Added rate limiting to /api/upload — previous impl caused OOM crashes"
"Fixed race condition in job queue — workers claimed same job"

Don't duplicate git (no file paths, line counts).

The plugin's Stop hook fires after every Codex turn and looks for finished sessions in ~/.codex/sessions/YYYY/MM/DD/*.jsonl. Sessions are recorded automatically when they go idle for 5+ minutes (or when a new session starts). You don't have to call worktale session add yourself — the hook handles tokens, cost, and model attribution.

Rules

Run worktale note immediately after each commit — don't batch
Be honest about intent — the developer reads these later
Keep notes concise (1–2 sentences)
Trivial commits still get a one-liner: worktale note "Quick typo fix"
Never skip a commit
If worktale fails, mention once and continue normally

Session start

Verify worktale --version
Run worktale capture --silent to ensure the repo is tracked
Confirm:

Worktale narration active. I'll add context after each commit. Tokens and cost are captured automatically by the SessionEnd hook.

If an initial note argument is provided:

worktale note "<the argument>"

Source: worktale/worktale-cli — distributed by TomeVault.

---name: worktaledescription: Narrate your Codex coding session into Worktale — adds per-commit context. Token + cost capture happens automatically via the SessionEnd hook. Use when this capability is needed.---# Worktale Session Narration (Codex)You are narrating this Codex coding session for Worktale, a developer work journal.Your one job: **after every git commit, append a 1–2 sentence narrative note**.A companion Stop / SessionEnd hook automatically captures provider, model, input/output tokens, computed cost, and duration by parsing the Codex session JSONL files at `~/.codex/sessions/`. You do **not** need to record those values — focus on narrative.## Prerequisites```bashworktale --version```If not installed:```Worktale CLI is not installed. Install it with: npm install -g worktale@latestThen run: worktale init```Do NOT proceed with narration until the CLI is available.## How it worksAfter every `git commit` you make during this session, immediately run:```bashworktale note "<1-2 sentence narrative about what you just did and why>"```Focus on **why**, not **what**:- "Added rate limiting to /api/upload — previous impl caused OOM crashes"- "Fixed race condition in job queue — workers claimed same job"Don't duplicate git (no file paths, line counts).The plugin's `Stop` hook fires after every Codex turn and looks for finished sessions in `~/.codex/sessions/YYYY/MM/DD/*.jsonl`. Sessions are recorded automatically when they go idle for 5+ minutes (or when a new session starts). You don't have to call `worktale session add` yourself — the hook handles tokens, cost, and model attribution.## Rules1. Run `worktale note` immediately after each commit — don't batch2. Be honest about intent — the developer reads these later3. Keep notes concise (1–2 sentences)4. Trivial commits still get a one-liner: `worktale note "Quick typo fix"`5. Never skip a commit6. If `worktale` fails, mention once and continue normally## Session start1. Verify `worktale --version`2. Run `worktale capture --silent` to ensure the repo is tracked3. Confirm:```Worktale narration active. I'll add context after each commit. Tokens and cost are captured automatically by the SessionEnd hook.```If an initial note argument is provided:```bashworktale note "<the argument>"```---> Source: [worktale/worktale-cli](https://github.com/worktale/worktale-cli) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Worktale