← ClaudeAtlas

find-or-make-skilllisted

Before Claude attempts any specialized task (game physics, animation library, specific SDK, design system, monetization strategy, etc) — use this skill to find an existing skill…
Nioris/project-forge · ★ 1 · AI & Automation · score 77
Install: claude install-skill Nioris/project-forge
# Find-or-Make Skill ## Purpose Prevent Claude from hallucinating solutions when a proper skill already exists somewhere in the ecosystem. Discovery-first, creation-last. ## Decision chain (execute in order — stop at first hit) ### Step 1: Local project skills (cheapest, most relevant) ``` Glob: .claude/skills/**/SKILL.md ``` Scan descriptions (not just names) for semantic match with the task. Don't just keyword-match — read the `description:` frontmatter field. If a local skill matches → invoke it, STOP. ### Step 2: Local agents (platform builders + general helpers) ``` Glob: .claude/agents/*.md ``` If an agent's frontmatter `description:` matches the task → use it via Task tool, STOP. ### Step 3: Anthropic official skills (verified, high quality) Web search these three sources: 1. `site:code.claude.com skill <topic>` — official docs 2. `github.com/anthropics/skills <topic>` — Anthropic's own skill repo 3. `github.com/anthropics/claude-plugins-official <topic>` — official plugin marketplace If found and clearly matches → tell user the install command (`/plugin install …` or `git clone …` into `.claude/skills/`) and wait for approval. Don't install silently. ### Step 4: Community marketplaces (bigger surface, more variance) Web search: 1. `site:claudepluginhub.com <topic>` 2. `site:buildwithclaude.com <topic>` 3. `github.com vercel-labs/agent-skills <topic>` 4. `github.com anthropics/skills <topic>` (in case Step 3 missed) Report findings to user with links. R