Content Schema Reference

June 2, 2026 ยท View on GitHub

Canonical validator logic lives in packages/registry.

Global required fields

Every entry should include:

  • title
  • slug
  • description
  • cardDescription
  • agents: usageSnippet, copySnippet
  • collections: items
  • commands: commandSyntax, usageSnippet, copySnippet
  • guides: usageSnippet
  • hooks: trigger, usageSnippet, copySnippet, configSnippet, scriptBody
  • mcp: installCommand, usageSnippet, copySnippet, configSnippet
  • rules: copySnippet
  • skills: installCommand, usageSnippet, copySnippet, downloadUrl, skillType, skillLevel, verificationStatus, verifiedAt, retrievalSources, testedPlatforms
  • statuslines: scriptLanguage, usageSnippet, copySnippet, configSnippet, scriptBody
  • tools: pricingModel, websiteUrl, disclosure

Forbidden fields

Do not include these in content files:

  • viewCount
  • copyCount
  • popularityScore

Upvotes are now owned by D1 (votes_entries) and not contributor metadata.

Downloadable package policy

  • Local package URLs (/downloads/...) must include packageVerified: true.
  • Community submissions should provide source/docs/release URLs, install commands, retrieval sources, or full copyable content.
  • Community ZIP/MCPB artifacts are not published as HeyClaude-hosted downloads.
  • Skills local packages must be .zip under /downloads/skills/....
  • MCP local packages must be .mcpb under /downloads/mcp/....

Skills capability metadata

Skills support two operating modes:

  • skillType: general
  • skillType: capability-pack

Capability packs are deep, version-aware skills and must include:

  • skillLevel: expert
  • verificationStatus (validated or production)
  • verifiedAt (ISO date YYYY-MM-DD)
  • retrievalSources (array of official docs/reference URLs)
  • testedPlatforms (array, e.g. Claude, Codex, OpenClaw, Cursor, Windsurf, Gemini)
  • Required sections in markdown body:
    • ## Knowledge Freshness
    • ## Retrieval Sources
    • ## Core Workflow
    • ## Capability Scope
    • ## Production Rules

Validation workflow

Run before merging content changes:

pnpm validate:content
pnpm validate:clean
pnpm audit:content
pnpm build

Submission workflow

  • Use /submit first for free Claude resources. The public preflight checks:
    • Category fields
    • Required copyable assets
    • Slug shape
    • Local package requests
    • Affiliate/referral URLs
  • Use direct pull requests when you are comfortable adding MDX directly and running the full gate.
  • Fully valid, source-backed, non-artifact PRs may trigger the gate to open a maintainer-owned import PR after passing checks. Maintainers still review before merge.
  • Tool/app/service promotions, listing claims, and jobs use the D1-backed website lead forms, not free content submissions.

For vote-state sync checks:

node scripts/sync-votes-to-d1.mjs --mode=both
node scripts/verify-d1-votes.mjs --mode=both