deprecation-and-migration
Skill4 starsChanged 4 months agoLicence not identifiedView on GitHub
Manages deprecation and migration. Use when removing old systems, APIs, IPC methods, or features. Use when migrating consumers from one implementation to another, evolving the wire protocol or DB schema, or deciding whether to maintain or sunset existing code.
We split this skill into the rules it gives an agent
11 rules. 11 are common, 0 are distinctive, and 0 are very specific to this project.
11
Common
Most of the 54 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions60 projects use a version of this.
Word for word · 0
None found.
Edited · 48
- addyosmani/agent-skills★ 112k51% same
- rizqinrr/viserys-agent★ 56052% same
- shashankswe2020-ux/whoop-mcp★ 17475% same
- vinvcn/addyosmani-agent-skills-zh★ 4620% same
- sampleXbro/agentsmesh★ 2475% same
- jaskirat1616/grok-skills★ 2253% same
- HK-hub/AgentSkills★ 653% same
- lza6/claw-code-tingfeng★ 575% same
- ddddjaak/ae-skills★ 475% same
- Marvellbrazil/my-agentic-skills★ 452% same
38 more not listed
Wrote their own version · 12
- drvoss/everything-copilot-cli★ 49same name
- jmxt3/gitscape.ai★ 33same name
- bnalwalid/walidforge-skills★ 2same name
- codexskills/agent-forge★ 2same name
- GuillemRoca/agent-skills-android★ 2same name
- NashEQify/forge★ 2same name
- Aleksandr-Litvinenko/agent-skills-ru★ 1same name
- celestialdust/achilles-skills★ 1same name
- Hello-Lain/skills★ 1same name
- juandelossantos/another-agent-skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use constraint-driven-development, playwright-cli and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 15 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 4 projects that use this
OpenAISkillverification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Also in 3 projects that use this
MicrosoftSkillcaveman
Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-and-interface-designSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
- zynk-pre-release-auditSkill
- debugging-difficult-bugsSkill
- pr-explainerSkill
- pr-splitterSkill
- smoke-testSkill
- zynk-docsSkill
- zynkSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

