Skills

principle-migrate-callers-then-delete-legacy-apis

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-migrate-callers-then-delete-legacy-apis 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-migrate-callers-then-delete-legacy-apis

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 using multiple AI coding agents who need a disciplined approach to API deprecation.

Use cases

Plan and execute a safe API migration by updating all callers first
Coordinate multi-agent workflows across different coding harnesses
Remove legacy APIs only after verifying all dependent code is updated

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

Supports a wide range of popular coding agents
Emphasizes a safe, systematic migration order
Based on proven Cursor primitives adapted for other tools

Cons

Requires familiarity with multiple agent-specific configurations
May need manual setup for each harness
Focused on a specific migration pattern, not general-purpose

Key facts

What we have checked

Days since the last commit: 0; Checked 7 Nov 2026GitHub
GitHub forks: 372; Checked 7 Nov 2026GitHub
GitHub stars: 4,117; Checked 7 Nov 2026GitHub
Days to a first reply on issues: 0.1; Checked 7 Nov 2026GitHub
Open issues: 4; Checked 7 Nov 2026GitHub
Releases in the last 90 days: 89; Checked 7 Nov 2026GitHub

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-migrate-callers-then-delete-legacy-apis is growing

GitHub stars

3,712 to 4,117

stars. 1 Nov 2026 to 7 Nov 2026, 2 readings.

Source: GitHub. Checked 7 Nov 2026.

Health and security

Is principle-migrate-callers-then-delete-legacy-apis 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 7 Nov 2026. How it is worked out

Part	Points	What we saw
Recent activity	30 of 30	Last push 0 days ago
Releases	15 of 15	89 releases in 90 days
Issue replies	20 of 20	First reply in 0.1 days (median)
Maintainer	0 of 15	Owned by a single user
Official source	Not counted	MCP 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 24 Oct 2026 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 7 Nov 2026 · 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