check-existing-artifacts
Before creating ANY new documentation, plans, or artifacts, ALWAYS check if similar documents alr... Use when configuring AI agent workflows and patterns. Agent Behavior category skill.
npx skills add majiayu000/claude-skill-registry --skill check-existing-artifacts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Check Existing Artifacts Before creating ANY new documentation, plans, or artifacts, ALWAYS check if similar documents already exist in the project. Search for existing epics, PRDs, stories, and planning documents. NEVER create new versions of documents that already exist—update the existing ones instead. Failing to check causes duplicate/conflicting documents, wasted effort, and version confusion.
What does the check-existing-artifacts skill do?
Before creating ANY new documentation, plans, or artifacts, ALWAYS check if similar documents alr... Use when configuring AI agent workflows and patterns. Agent Behavior category skill.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill check-existing-artifacts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.