Use when working in a workspace with an Oathe board (the SessionStart context shows one) — before starting any substantive task, when reporting progress, when picking prior work back up, and when stopping. Claims are speech acts recorded in the cell substrate via the oathe_* MCP tools.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add oathe-ai/oathe --skill oathe-work --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Oathe Work?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oathe-ai-oathe-work)More formats (shields.io, HTML) on the badges page.
---
name: oathe-work
description: Use when working in a workspace with an Oathe board (the SessionStart context shows one) — before starting any substantive task, when reporting progress, when picking prior work back up, and when stopping. Claims are speech acts recorded in the cell substrate via the oathe_* MCP tools.
---
# Working the Oathe board
The board in this session's opening context is the durable record of this folder's work.
The substrate refuses dishonesty by construction — work with it, not around it.
## The loop
1. **Claim before you build.** Substantive work starts with `oathe_claim {task_id, objective}`.
A claim takes responsibility; it never mints the work as done. A task without a real plan
is honestly `plan_status: "unknown"` — never fabricate one. Work you claim while this
session already holds a claim is recorded as spawned under it (the board and the breach
digest show siblings as one row under the parent); pass `parent: null` for standalone
work, or `parent: "<task>"` to name the claim it serves.
2. **Statements as you go.** Record findings and progress with
`oathe_statement {task_id, proposition, evidence_ref}`. A statement is a statement, not
truth — nothing settles by saying it.
3. **Pick up, don't re-derive.** When the user says "continue <task>" (or the board shows a
lease of yours), call `oathe_pickup {task_id}`: the successor sequence returns the compiled
frame for the obligation. The obligation, not the conversation, is what comes back.
4. **Say done when it is done.** Finished work closes with
`oathe_done {task_id, proposition, evidence_ref}` — a completion statement plus the
substrate's own terminal. Completion is ASSERTED, not settled: verification is still owed.
5. **Yield what you cannot finish.** Stopping without finishing means
`oathe_yield {task_id, note}` — the task goes back on the board, unowned, with a declared
cause. Walking away silently leaves a lease to expire, which the board will show.
## Refusals are the product
A second claimant is refused. A statement against no claim is refused. A yield without a
declared cause is refused. When a tool returns a typed error, report it faithfully — do not
retry blindly and do not soften it into success.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!