Tlaplus Split Action
Split a TLA+ action into two sequential actions by introducing a new program counter (pc) state. Handles pc variable updates, UNCHANGED statements, TypeOk predicates, and follows naming conventions with renumbering. Use when the user asks to split, divide, or break an action into two parts, or wants to add an intermediate step to an action sequence.
Install
npx skills add tlaplus/AgentSkills --skill tlaplus-split-actiongit clone --depth 1 https://github.com/tlaplus/AgentSkills.git /tmp/AgentSkills
mkdir -p ~/.claude/skills
cp -r /tmp/AgentSkills/skills/tlaplus-split-action ~/.claude/skills/tlaplus-split-actionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Split TLA+ Action into Two Actions
Split an existing TLA+ action into two sequential actions by introducing a new intermediate `pc` state. This is useful for modeling finer-grained atomicity or adding intermediate steps to an action sequence.
## Prerequisites
- The specification must have a `pc` variable (or equivalent like `state`, `phase`) that tracks action sequencing. If not, create one.
- The action to split must update `pc` to transition between states
## Overview
Given an action like:
```tla
ActionX_1(thread) ==
/\ pc[thread] = PC_ActionX_1
/\ pc' = [pc EXCEPT ![thread] = PC_Start]
/\ y' = y + 2
/\ UNCHANGED <<x, z>>
```
Splitting it creates:
```tla
ActionX_1(thread) ==
/\ pc[thread] = PC_ActionX_1
/\ pc' = [pc EXCEPT ![thread] = PC_ActionX_2] \* Leads to new intermediate state
/\ y' = y + 2 \* Original logic (or subset per user)
/\ UNCHANGED <<x, z>>
ActionX_2(thread) == \* New action
/\ pc[thread] = PC_ActionX_2
/\ pc' = [pc EXCEPT ![thread] = PC_Start] \* Original destination
/\ UNCHANGED <<x, y, z>> \* All vars unchanged (or subset per user)
```
## Workflow
### Step 0: Add `pc` variable if not presentDetails
- Skill name
tlaplus-split-action- Repository
- tlaplus/AgentSkills
- Path
skills/tlaplus-split-action/SKILL.md- License
- MIT
- Repo updated
- 4 February 2026
FAQ
What does the Tlaplus Split Action skill do?
Split a TLA+ action into two sequential actions by introducing a new program counter (pc) state. Handles pc variable updates, UNCHANGED statements, TypeOk predicates, and follows naming conventions with renumbering. Use when the user asks to split, divide, or break an action into two parts, or wants to add an intermediate step to an action sequence.
How do I install the Tlaplus Split Action skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add tlaplus/AgentSkills --skill tlaplus-split-action. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tlaplus Split Action popular?
It lives in tlaplus/AgentSkills, which has 49 GitHub stars and 1 forks.
Related skills
Tlaplus Add Variable
49tlaplus/AgentSkills
Add a new variable to an existing TLA+ specification without changing its semantics. Ensures the variable is declared, initialized, and added to all UNCHANGED statements. Use when the user asks to add, introduce, or declare a new variable in a TLA+ spec, or mentions UNCHANGED statements.
Tlaplus From Source
49tlaplus/AgentSkills
Generate a high-level TLA+ model from source code (C, C++, Rust, etc.). Analyzes code to understand its purpose, creates abstractions, writes TLA+ specification, and proposes invariants and properties. Use when the user wants to model source code in TLA+, create a formal specification from implementation, or verify concurrent/distributed algorithms.
Game Code Review
57AlterLab-IEU/AlterLab_GameForge
Reviews game code and AI-agent changes as a forked reviewer and writes a severity-ranked report: frame-rate independence, hot-path allocations, state and resource lifecycle, hallucinated engine APIs and leaked secrets, for Godot, Unity, Unreal and web. Use for "review my code", "review this PR", "check what the agent wrote". Not for design documents (use game-design-review).
Game Godot Specialist
57AlterLab-IEU/AlterLab_GameForge
Writes and reviews Godot 4 code (4.7 stable, 4.8 beta) in GDScript and C#: scenes and nodes, signals, Resources, autoloads, Jolt physics, shaders, profiling, export, GUT/gdUnit4 tests and headless CLI checks. Use when the project has project.godot, .gd or .tscn files, or the user mentions Godot or GDScript. Not for engine-agnostic architecture (use game-technical-director).
Programmed Illusion
113Hmbown/Wizards-of-the-Ghosts
In D&D, Programmed Illusion creates an illusion that lies dormant until a specific trigger condition is met, then plays out its scene automatically. The real-world version is the conditional demo, automated preview, or triggered walkthrough: onboarding flows that appear when a user first visits, contextual tooltips that activate on hover, preview environments that spin up on pull request, automated scenario presentations that play when specific data conditions are detected. Programmed Illusion is the illusion that does not need a wizard present to cast it.
Game Vibe Code
57AlterLab-IEU/AlterLab_GameForge
Runs an AI-agent build loop from idea to a playable, verified, shippable game: one-page spec, playable in the first hour, one feature per iteration with a pass/fail check, Playwright screenshots, commits and a progress.md handoff. Use for "vibe code a game", "build a game with Claude", "make a browser game fast". Not for throwaway mechanic tests (use game-prototype).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.