Menu
Use when asked to find similar projects, existing tools, prior art, libraries, or whether something already exists before building.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when asked to audit docs, review docs accuracy, or validate documentation claims against actual code, commands, APIs, configs, and diagrams.
Use when asked to grade, evaluate, assess, score, or review an agent skill's quality.
Use when asked to monitor an upstream repository for new commits, releases, merged PRs, or breaking changes affecting a local fork or wrapper.
Use when asked to find security vulnerabilities, run a security scan, review security fixes, or assess a repository for exploitable issues.
Use when asked to update dependencies, upgrade packages, avoid deprecated packages, or fix issues after a dependency update.
| name | prior-art-search |
| description | Use when asked to find similar projects, existing tools, prior art, libraries, or whether something already exists before building. |
| metadata | {"short-description":"Multi-angle search for existing tools before building"} |
One search angle always misses things. Sweep several, then judge.
npm search / PyPI / crates for the domain keywords; registries surface things GitHub search ranks poorly.gh api dependents, awesome-lists in the domain).Per candidate, one row: stars, last commit date, open-issue responsiveness, license, and — most important — the exact overlap and the exact gap vs the idea. Install/run the top 2 candidates on a real example when feasible; READMEs oversell.
Notes: