principle-separate-before-serializing-shared-state
An agent skill by cursor, from cursor/plugins. Tags: architecture, concurrency, development, troubleshooting, validation.
What it does
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add cursor/plugins --skill principle-separate-before-serializing-shared-state
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/cursor/plugins
cp -r plugins/pstack/skills/principle-separate-before-serializing-shared-state ~/.claude/skills/principle-separate-before-serializing-shared-state
Safety box score
Grade A, minimal risk: 0 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is a short markdown guide about how to design around shared mutable state; it does not ship code, scripts, or networked tooling. The practical risk is essentially nil beyond the general risk of misleading advice in any documentation-only skill.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | No scripts, shell commands, or code evaluation are present; the only file is `SKILL.md`. |
| Network access | 0 (none) | There is no download, upload, API call, or remote host interaction in the skill files. |
| Filesystem reach | 0 (none) | The skill only describes a design pattern and does not read, write, or delete files. |
| Secrets & credentials | 0 (none) | It does not ask for credentials, tokens, `.env` files, or other secrets. |
| Privilege & persistence | 0 (none) | No sudo, global install, service registration, or OS/shell settings changes are included. |
| Instruction hijack surface | 0 (none) | `SKILL.md` contains ordinary guidance text and no prompt-injection patterns, hidden instructions, or remote-follow instructions. |
| Irreversible actions | 0 (none) | It does not perform or instruct any external action such as posting, deploying, deleting, or paying. |
| Transparency | 0 (none) | The skill is fully readable markdown; there are no binaries, encoded blobs, or unreviewable installers. |
Before installing
- Read `SKILL.md` to confirm it is documentation-only and contains no accompanying scripts.
- If you later add automation to this skill, review those new files separately before enabling them.
- No special safety checks are needed for the current version beyond standard repository review.
Rated 2026-10-16 by an automated review of 1 file from the skill's repository.
Source
- Repository
- cursor/plugins (all skills from this repository)
- Path
- pstack/skills/principle-separate-before-serializing-shared-state/SKILL.md
- Branch
- main
- Collection
- cursor
- Updated
- 2026-09-23
Related skills
- principle-type-system-discipline — Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.
- seo-programmatic — Programmatic SEO planning and analysis for pages generated at scale from data sources.
- architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
- debug-voice — Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture what happened in a Grok realtime voice session.
- fix-ci — Find failing PR checks, inspect logs or external check links, and apply focused fixes
- how — Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live".