About zero-day
A deprecated skill notice for users explicitly invoking `zero-day` or asking about its migration. It points to `vulnerability-research` and provides replacement and removal guidance, not the former workflow.
Key features
- 01Migration guidance to `vulnerability-research`
- 02Checks whether the replacement is installed
- 03Advises backing up customizations before removal
Use cases
- 01Handling an explicit `zero-day` invocation
- 02Finding the replacement for a former workflow
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/zero-dayin Claude Code to confirm it loaded.
Details
From the project READMEDeprecated: zero-day
This old skill name is retained temporarily to explain the catalog migration. It provides migration guidance only and does not contain the former task workflow.
When to use
Only when the user explicitly invokes the old zero-day name or asks how to migrate it.
When NOT to use
Do not select this notice for ordinary domain tasks or treat it as an active skill.
Workflow
- Explain that this skill was renamed or merged into vulnerability-research.
- If vulnerability-research is installed, offer it by name and use its own instructions when the request authorizes that work.
- If it is missing, explain how to install the replacement and remove this old entry after backing up customizations. Do not read a sibling path or install anything silently.
See MIGRATION.md in the collection repository
for installer-specific steps and the complete mapping.
Rules
- Keep this notice for one transition release and at least seven days after publication.
- Never claim an installed copy will update or disappear automatically.
- Preserve local edits and private overlays before removing an installed entry.
Comments
Markdown supported