Curation Policy

claudecode.directory is a curated directory, not a dumping ground. This page explains exactly what gets listed, what gets removed, and how rankings are computed — so you can trust what you find here.

What gets listed

Every listing is reviewed by a maintainer before publication. To be accepted, a resource must be:

  • Directly useful for working with Claude or Claude Code (MCP servers, tools, CLAUDE.md templates, hooks, prompts, docs).
  • Documented well enough that a developer can evaluate it without installing it.
  • Actively maintained, or explicitly labeled when it is archived or historical.
  • Working as advertised — we spot-check installs and links during review.
  • Free to try. Paid products are fine if there is a usable free tier or trial.

What gets removed or flagged

We prune rather than accumulate. A listing is flagged for review — and removed or labeled if the issue is confirmed — when:

  • Its URL is dead (404s or redirects to unrelated content).
  • Its repository is archived, or has had no commits for 12+ months (archived listings stay visible with a clear archived warning when they remain historically useful).
  • A security concern is reported and confirmed.
  • It turns out to be spam, malware, or a misrepresentation of what it does.

How ranking works

Rankings blend objective and community signals. We never sell placement, and no listing can pay to rank higher:

  • Objective GitHub health: stars, forks, open issues, last-commit recency, license — fetched from the GitHub API on a regular cadence and shown on every enriched listing.
  • Community engagement: votes and copy counts collected on this site.
  • Recency: newly added and recently updated resources get temporary visibility boosts on trending views.
  • Editorial picks ("Featured") are chosen by maintainers and always labeled as such.

Freshness

GitHub data is refreshed by an automated enrichment job, and every enriched listing shows a "last verified" date. Right now 20 of 46 listings carry live GitHub health data; the rest are inline content (templates, prompts, hooks) maintained directly in this directory.

  • Enrichment cadence: weekly (automated).
  • Dead-link and staleness detection: automated scans surface candidates; a maintainer makes the final call. Nothing is auto-deleted.

Reporting a problem

Anyone can report an issue with a listing — stale link, unmaintained project, security concern — using the "Report an issue" link on every resource page. Reports go straight into the review queue.