eol-check
Skill1.6k starsChanged 3 days agoMITView on GitHub
Compare the versions of the platform dependencies this repo runs on (Node, React, React Native, Expo, Next.js, Docusaurus, TypeScript, Firebase Functions runtime) against endoflife.date and npm, and say what to upgrade. Use for an EOL / maintenance / "are we up to date" check, or from the factory's weekly run.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Vulnetix/pix-ai-coding-assistanttheir own version, first seen Nov 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Vulnetix/pix-ai-coding-assistant★ 9same name
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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- gdpr-auditSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- security-findingsSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Read the resolved version from yarn.lock when a range is given.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
EOL check
Goal: upgrade to a new stable release as soon as it's proven (out for at least 14 days), and never run on something past its end of life.
1. Collect what this repo uses
Find the version actually in use, and every place that pins it:
| Product | Where to look |
| Node.js | .nvmrc, engines, CI node-version, netlify.toml NODE_VERSION, Dockerfile FROM, server/firebase.json runtime, pkg targets |
| React / React DOM | package.json of each workspace |
| React Native / Expo | package.json of examples and test apps, peer ranges of published packages |
| Next.js | frontend/package.json |
| Docusaurus | website/package.json |
| TypeScript | root package.json |
Read the resolved version from yarn.lock when a range is given.
2. Compare with upstream
- Lifecycle:
curl -s https://endoflife.date/api/<product>.json(nodejs,react,react-native,expo,nextjs,docusaurus,typescript). Each cycle hascycle,releaseDate,eol,support,latest,latestReleaseDate. - Latest stable:
npm view <package> time --jsonfor release dates when endoflife.date lacks the product.
3. Decide
For each product:
- EOL — our cycle's
eoldate is past → severity high. - EOL soon —
eolwithin 90 days → medium. - Upgrade available — a newer stable cycle or patch whose release is ≥ 14 days old → low (patch/minor) or medium (major).
- Ignore releases younger than 14 days, pre-releases and release candidates.
- Note known blockers (e.g. a major that a dependency doesn't support yet — check the ADRs and open issues before proposing it).
4. Output
A table: product · in use · latest stable (date) · our cycle EOL · status · action, then for each action one line saying patch/minor (safe to upgrade automatically, ends in a draft PR) or major (needs a human go: describe blockers and the files to change). Don't upgrade anything in the same run unless asked.
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.

