HeyClaude — Claude & AI workflow directory

Search read-only HeyClaude registry entries by query, category, exact tag, and skill platform compatibility.

Plan a read-only Claude or Codex workflow toolbox from ranked HeyClaude registry entries. Each entry includes an inline install block (install command, config snippet, download URL) and the recommended stack is summarized as a copy-pasteable installPlan, alongside trust and follow-up guidance.

Answer 'what should I use to do X' in one call. Given a plain-language task (and optional platform/category), returns the best-match HeyClaude entries ranked by fit — each with why it fits, trust summary, disclosed safety/privacy notes, and an inline install block — plus a topPick and a consolidated installPlan. Unlike workflow.plan it does not force category diversity; it returns the genuinely be

Fetch read-only HeyClaude MCP package, registry, tool, and public rate-limit metadata.

List read-only HeyClaude entries with bounded pagination and optional category, platform, tag, and query filters.

List recently added or upstream-updated HeyClaude entries from generated registry metadata.

Fetch read-only related HeyClaude entries based on category, tags, platforms, keywords, and source metadata.

Fetch a read-only HeyClaude registry entry detail payload by category and slug. By default (bodyMode='excerpt') the body markdown is trimmed to a short lead and large copyable fields are omitted to conserve context, with bodyChars/bodyTruncated/omittedFields describing what was dropped; pass bodyMode='full' for the complete content or 'none' to drop the body entirely. Use entry.asset to retrieve o

Fetch the category-aware copy/install asset for a HeyClaude entry without writing local files. Pass assetType (e.g. 'install_command', 'config_snippet') to return only that asset and avoid the full_content/script payloads when you do not need them.

Compare 2-5 read-only HeyClaude entries by fit, category, platforms, source metadata, and install complexity.

Fetch aggregate read-only registry stats, freshness, category counts, and real source-signal coverage.

Fetch read-only MCP client setup snippets for Codex, Claude Desktop, Cursor, Windsurf, or remote HTTP clients.

Fetch platform compatibility metadata for a HeyClaude skill entry.

Fetch read-only install, config, usage, and package guidance for a HeyClaude entry.

Fetch generated read-only platform adapter content, currently Cursor rule adapters for skill packages.

List read-only HeyClaude registry feeds, category feeds, platform feeds, and artifact locations.

Fetch read-only HeyClaude submission schemas for PR-first intake by category.

Validate a HeyClaude content submission draft locally without creating GitHub issues, pull requests, or publishing content.

Search generated registry artifacts for likely duplicate entries before a user opens a submission PR.

Build prefilled HeyClaude submit and review URLs for a validated PR-first submission draft without making write calls.

Fetch category-specific HeyClaude contribution guidance, required fields, and review expectations.

Build a read-only maintainer-reviewed HeyClaude submission draft with canonical PR text and URLs.

Fetch read-only category examples and templates for faster, more accurate HeyClaude submissions.

Review a HeyClaude submission draft locally for schema errors, duplicate risk, and maintainer checklist items without writing to GitHub.

Fetch HeyClaude's read-only submission, artifact, import, and maintainer-review policy for contributors and agents.

Explain deterministic trust, source, package, safety, privacy, and review metadata signals for one HeyClaude entry. This is a metadata review only and does not provide malware scanning, automatic safety guarantees, or installation approval.

Review 1-5 HeyClaude entries for source, package, safety, and privacy metadata fit before install or recommendation. This is a metadata review only and does not provide malware scanning, automatic safety guarantees, or installation approval.

Compare 2-5 HeyClaude entries side by side by how much trust metadata they disclose (source, package, safety, privacy, and review provenance) and rank them by deterministic signal coverage. This measures disclosed-metadata completeness only; it is not a malware scan, a safety verdict, or installation approval, and a higher score does not mean an entry is safe.