Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Manage long Claude Code work with statem state-machine runbooks.
Install Use Statem
$ npx skills add henryqin1997/statem --skill use-statem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install henryqin1997/statem use-statem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .claude/skills/use-statem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .claude/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add henryqin1997/statem --skill use-statem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install henryqin1997/statem use-statem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .agents/skills/use-statem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .agents/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add henryqin1997/statem --skill use-statem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install henryqin1997/statem use-statem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .cursor/skills/use-statem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .cursor/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/henryqin1997/statem.git --path integrations/claude/statem/skills/use-statem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add henryqin1997/statem --skill use-statem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install henryqin1997/statem use-statem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .gemini/skills/use-statem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .gemini/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install henryqin1997/statem use-statemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add henryqin1997/statem --skill use-statem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .github/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .github/skills/use-statem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .github/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add henryqin1997/statem --skill use-statem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install henryqin1997/statem use-statem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/henryqin1997/statem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/integrations/claude/statem/skills/use-statem .opencode/skills/use-statem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "use-statem" agent skill from https://github.com/henryqin1997/statem/tree/main/integrations/claude/statem/skills/use-statem into .opencode/skills/use-statem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-statem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
use-statem- GitHub stars
- 1.3k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 591 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Manage long Claude Code work with statem state-machine runbooks.
- Works in 7 steps: Inspect or create a spec such as… → Run statem validate statem.yaml --json. → Start or resume with statem start… → …
- Tasks need durable state
- SKILL.md covers Operating Loop, Context Clear, Loop Compaction and Auto Loop Hook, plus 1 more section
- Calls python3
What it does
Use Statem is an agent skill from henryqin1997/statem. Manage long Claude Code work with statem state-machine runbooks. Use when tasks need durable state, explicit transitions, redo loops, save/resume behavior, or cross-agent review.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: CLI runbook for agent long run. The licence is Apache-2.0.
When your agent uses it
- Tasks need durable state
- Explicit transitions
- Save/resume behavior
- Cross-agent review
Example prompts
- “/use-statem”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Bash(statem *), Bash(python3 -m statem *)
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Inspect or create a spec such as statem.yaml.
- Run statem validate statem.yaml --json.
- Start or resume with statem start statem.yaml --run-id --json.
- Before work, run statem cur --run-id --json.
- When a state is complete, run statem goto --run-id --json.
- Before pausing, run statem save --run-id --json.
- For handoff context, read recent history: statem history --run-id --tail 10 --json.
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3309a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(statem *)Bash(python3 -m statem *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Use Statem loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 591 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from henryqin1997/statem at commit 8c3309a, republished under its Apache-2.0 licence (© henryqin1997). 591 words, ~1,071 tokens.
Download SKILL.mdSave it as
.claude/skills/use-statem/SKILL.md (or your agent's skills folder).- name
- use-statem
- description
- Manage long Claude Code work with statem state-machine runbooks. Use when tasks need durable state, explicit transitions, redo loops, save/resume behavior, or cross-agent review.
- allowed-tools
- Bash(statem *), Bash(python3 -m statem *)
- argument-hint
- task-or-spec
Use Statem
Use statem as a state-aware runbook for long agent runs. It should guide the work and preserve progress without turning the session into a rigid workflow harness.
Operating Loop
- Inspect or create a spec such as
statem.yaml. - Run
statem validate statem.yaml --json. - Start or resume with
statem start statem.yaml --run-id <id> --json. - Before work, run
statem cur --run-id <id> --json. - When a state is complete, run
statem goto <next> --run-id <id> --json. - Before pausing, run
statem save --run-id <id> --json. - For handoff context, read recent history:
statem history --run-id <id> --tail 10 --json.
If statem is not on PATH, use python3 -m statem from the repository that contains the Python package.
For dynamic servers, company machines, or disposable git checkouts, prefer a
machine-local state directory. Set STATEM_STATE_DIR once, for example
$HOME/.local/state/statem/<project>, so runtime state survives checkout
replacement. After moving to a new checkout, run statem start <spec> --run-id <id> once to rebind the run to the current spec path.
Commit YAML runbooks with the repo. Do not commit runtime state; treat .statem/
or STATEM_STATE_DIR as local, copy-on-use execution data.
Context Clear
Avoid /clear in normal loops. It flushes the conversation, including any
instructions that were supposed to run after it, and can lose useful intent that
was not written to durable files. Prefer explicit transitions plus safe
compaction. Before a hard clear, run
statem prompt --run-id <id> and paste the generated prompt immediately after
/clear. After a hard clear, recover from .statem with start, cur, and
history instead of relying on previous chat context.
Loop Compaction
For cyclic runbooks, prefer an explicit session hygiene node after a full loop.
When another cycle will continue and the context is noisy, run
statem compact-prompt --run-id <id>, use the generated /compact
instruction, then recover with statem cur and statem history --tail 10.
Agents may inspect the full graph with statem state; cur, next, and
goto are for disciplined execution and attention anchoring, not for hiding the
runbook.
Show full SKILL.md (258 more words)Show less
Auto Loop Hook
When the host supports a Stop hook, users may opt into auto-loop behavior with
integrations/hooks/statem_stop_hook.py. The hook runs when the agent is about
to hand control back to the user. If a statem run is active, the current node is
not a terminal/handoff node, and there are outgoing transitions, it returns a
continuation prompt that tells the agent to inspect statem cur and keep
working from the current node.
Registration examples live in:
examples/hooks/README.mdexamples/hooks/codex-stop-autoloop.hooks.jsonexamples/hooks/claude-stop-autoloop.settings.json
Merge the matching snippet into the host hook configuration and use an absolute script path if the hook is registered outside the statem repository.
Treat this as host-level glue. It must not advance state, run /clear, or hide
the graph. The agent should still transition only with statem goto.
Spec Guidance
- Put runtime data under
.statem/; do not mix it into the spec. - Use
in_hookfor setup after entering a node. - Use
before_transferfor checks/redos while still in the current node. It is a spec field, not a CLI command;statem gotoruns it automatically. - Use
out_hookto persist current-node progress before leaving. - Use edge
hookas prepare-transfer work afterout_hookand before entering the target. If a blocking edge hook fails, the pointer stays at the source so the agent can retry. - Use
type: commandfor deterministic shell checks and hooks. - Use
type: predicatefor file checks instead of shell when possible. - Use
type: llm_reviewto call Codex, Claude, or another reviewer command. - Treat blocked transitions as useful feedback: stay in the node, fix the issue, then retry.
© henryqin1997, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in integrations/claude/statem/skills/use-statem of henryqin1997/statem.
Open the folder on GitHubat commit 8c3309a
Compare with similar skills
Use Statem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Use Statem this skillhenryqin1997/statem | 1.3k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 497 | — | ~2k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 6.2k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Make Trace
AIScientists-Dev/Flowtrace
Turn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace.
More from henryqin1997/statem
Statem
henryqin1997/statem
A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…
Related
Categories
Questions about Use Statem
What does Use Statem do?
Manage long Claude Code work with statem state-machine runbooks. Use Statem is an agent skill from henryqin1997/statem. Manage long Claude Code work with statem state-machine runbooks.
When should I use Use Statem?
Use Statem fits situations like: tasks need durable state; explicit transitions; save/resume behavior; cross-agent review.
How do I install Use Statem in Claude Code?
Run `npx skills add henryqin1997/statem --skill use-statem -a claude-code`. Or copy the skill folder (integrations/claude/statem/skills/use-statem in henryqin1997/statem) into .claude/skills/use-statem in your project. Claude Code loads it when a task matches its description.
How do I install Use Statem in Codex?
Run `npx skills add henryqin1997/statem --skill use-statem -a codex`. Or copy the skill folder (integrations/claude/statem/skills/use-statem in henryqin1997/statem) into .agents/skills/use-statem in your project. Codex loads it when a task matches its description.
Can I use Use Statem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add henryqin1997/statem --skill use-statem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-statem, .gemini/skills/use-statem, .github/skills/use-statem and .opencode/skills/use-statem in your project.
What does Use Statem need to run?
Going by SKILL.md and its folder, Use Statem needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash(statem *), Bash(python3 -m statem *).
Does Use Statem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Use Statem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Use Statem use?
Use Statem is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Use Statem use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Use Statem?
Skills that share tags, products or a category with Use Statem: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 497 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Use Statem?
henryqin1997 (a GitHub user) maintains it in henryqin1997/statem, which has 1,335 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 2, 2026.
Source: henryqin1997/statem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.