Enterprise DNAEnterprise DNA

Skills

principle-separate-before-serializing-shared-state

by michael-denyer

Antigravity, Claude Code, Codex, Copilot, Gemini, Muse, OpenCode, Pi, and Prime Agent versions of Poteto's pstack.

Our verdict

Not reviewed yet

We have not reviewed principle-separate-before-serializing-shared-state yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About principle-separate-before-serializing-shared-state

Antigravity, Claude Code, Codex, Copilot, Gemini, Muse, OpenCode, Pi, and Prime Agent versions of Poteto's pstack. Rigorous agent workflows with Cursor primitives translated for other harnesses.

Best for

Developers building multi-agent systems that need reliable state serialization across different coding harnesses.

Use cases

  • Prevent race conditions when multiple agents share state
  • Ensure clean serialization of shared data in agent workflows
  • Port Cursor-based agent workflows to other coding harnesses

Notes

4,171 stars on GitHub. Last updated 2026-11-09. Licensed MIT.

Indexed from github-skill-repos. Verified against the live GitHub repo.

Pros

  • Multi-harness support covers major agent tools
  • Based on proven pstack workflows
  • Open source with high community adoption (3.4k stars)

Cons

  • Requires understanding of the underlying principle to apply correctly
  • May need adaptation for specific project state structures
  • Not a standalone tool; integrates as a skill within a harness

Key facts

What we have checked

Days since the last commit
0
Checked GitHub
GitHub forks
397
Checked GitHub
GitHub stars
4,306
Checked GitHub
Days to a first reply on issues
0.1
Checked GitHub
Open issues
4
Checked GitHub
Releases in the last 90 days
95
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How principle-separate-before-serializing-shared-state is growing

GitHub stars

3,712 to 4,306

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is principle-separate-before-serializing-shared-state looked after, and what do its setup files show

Health score

81 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 0 days ago
Releases15 of 1595 releases in 90 days
Issue replies20 of 20First reply in 0.1 days (median)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 main@356c6e0f978d. What it checks

  • Note No dependency list or install command was found in the skill, so there were no packages to look up on OSV.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.