Statechart
Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives a shortest path for each rule that breaks. Use for /statechart, or when a task needs a TLA+ model checked or a model's bug shown as a path through states.
Install
npx skills add bolasblack/claude-skills --skill statechartgit clone --depth 1 https://github.com/bolasblack/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/statechart ~/.claude/skills/statechartPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Statechart The chart shows how a system moves between states, in the words of the person who reads it. That person, the reader, decides whether the behavior is right. ## Run Work in a scratch folder outside the repo. Write a TLA+ spec and its config there, or copy in the `.tla` and `.cfg` files of an existing model after you review them, because other files beside a spec can run as code. Then run: ```sh <skill dir>/scripts/statechart SPEC.tla [--config FILE] [--view FILE] [--out DIR] ``` `<skill dir>` is the directory that holds this `SKILL.md`. If the launcher is not executable, run it with `sh`. `scripts/statechart.ts` is TypeScript, so run it with a runtime that can execute TypeScript. The first run installs TLC and Java with mise and needs the network, so tell the user before it starts. If mise or a supported runtime is missing, report that and let the user decide how to provide it. ## Write the spec - Write each rule that the reader agrees to as an INVARIANT. A rule can be about a screen, a result, a stored value, or a message. If the model has no variable for a rule, add the variable. Never weaken a rule to make it hold. - Write `Next` as a disjunction of the actions, such as `YouPressPlay \/ YouPressStop`. If you do not, TLC names every step `Next`.
Details
- Skill name
statechart- Repository
- bolasblack/claude-skills
- Path
skills/statechart/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Statechart skill do?
Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives a shortest path for each rule that breaks. Use for /statechart, or when a task needs a TLA+ model checked or a model's bug shown as a path through states.
How do I install the Statechart skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add bolasblack/claude-skills --skill statechart. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Statechart popular?
It lives in bolasblack/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Caveman
5bolasblack/claude-skills
Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".
Agent Centric
5bolasblack/claude-skills
Track decisions (AGD) with validation and indexing. Use when making design decisions, recording important choices, discussing trade-offs, or when user mentions AGD or decision record.
Codex
5bolasblack/claude-skills
OpenAI Codex second opinion via the codex CLI — three modes. Review: independent diff review with a pass/fail gate. Challenge: adversarial pass that tries to break the code. Consult: ask Codex anything, with session continuity for follow-ups. Use when the user says "codex review", "codex challenge", "ask codex", or wants a second opinion from Codex.
Subagent Driven Development
8Freddy-CHEN-ux/00_claude_skills
Use when decomposing complex work. Dispatch fresh subagent per task, review between tasks. Flow: Load plan → Dispatch task → Review output → Apply feedback → Mark complete → Next task. No skipping reviews, no parallel dispatch.
Skilzy Creator
8Freddy-CHEN-ux/00_claude_skills
Comprehensive toolset for creating, converting, validating, and packaging Skilzy-compliant AI agent skills. This skill should be used when users want to initialize a new skill, convert a Claude skill archive to the Skilzy format, validate an existing skill's structure and compliance, or package a skill for distribution to the Skilzy registry.
Subagent Workflow
8Freddy-CHEN-ux/00_claude_skills
Use when orchestrating subagents for implementation. Covers when to dispatch vs recall, how to scope tasks, session management, and handoff patterns. Load this before working with any subagent.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.