HeyClaude Content Submission Factory

Knowledge Freshness

This skill is pinned to HeyClaude PR-first submission behavior verified on 2026-06-02.

Retrieval Sources

• https://heyclau.de/submit
• https://heyclau.de/submissions
• https://github.com/JSONbored/awesome-claude/blob/main/AGENTS.md

Core Workflow

1. Identify the best HeyClaude category from the evidence, not from the submitter's guess.
2. Collect a canonical source URL and any official docs, repo, package, or demo URLs.
3. Extract only public, non-secret facts.
4. If the HeyClaude MCP server is available, call get_submission_schema, search_duplicate_entries, validate_submission_draft, and build_submission_urls instead of guessing field shape.
5. Add brand metadata when safe: brandName, brandDomain, and official source links.
6. Write a concise original description and card description.
7. Draft SEO metadata from the resource title, category, tags, and source-backed value.
8. Produce PR-first submission fields and a HeyClaude submit URL for the website-to-PR flow.

Category Scope

• Agents
• MCP servers
• Tools
• Skills
• Rules
• Commands
• Hooks
• Guides
• Collections
• Statuslines

Jobs are intentionally out of scope. Job listings use HeyClaude's jobs lead and review workflow.

MCP-Assisted Path

When an MCP client has the HeyClaude MCP server configured, use it as the source of truth for registry submission structure:

• get_submission_schema for required and optional fields by category.
• search_duplicate_entries before drafting a new listing.
• validate_submission_draft to catch malformed fields before handoff.
• build_submission_urls to generate PR-first review URLs without creating GitHub issues directly.

If the MCP server is unavailable, continue with the PR-first draft packet and explicitly mark validation as manual.

Review Rules

• Do not auto-publish registry content.
• Do not create PRs, create GitHub issues, write files, or mutate local project config.
• Reject or route away paid listings, thin promo, affiliate-style entries, duplicates, and unsupported categories.
• Do not include private repo names, credentials, tokens, internal URLs, or unpublished customer information.
• Do not mirror full third-party pages. Use original summaries and canonical source links.
• Do not claim platform compatibility, validation, package checksums, or first-party status unless source evidence supports it.

Output Shape

Return a compact submission packet:

category: mcp
title: Example MCP Server
slug: example-mcp-server
description: Short source-backed summary.
cardDescription: One-line preview text.
sourceUrl: https://example.com/docs/mcp
documentationUrl: https://example.com/docs
repoUrl: https://github.com/example/example
brandName: Example
brandDomain: example.com
tags:
  - mcp
  - automation
seoTitle: Example MCP Server for Claude
seoDescription: Source-backed description suitable for search previews.
mcpValidation:
  schemaChecked: true
  duplicateSearch: "No likely duplicate found."
  submitUrl: https://heyclau.de/submit?...
  prTargetPath: content/mcp/example-mcp-server.mdx
maintainerNotes: Why this belongs in HeyClaude and what still needs review.

Troubleshooting

Issue: The category is ambiguous
Fix: Prefer the category that matches the install or usage surface. An MCP server is not a skill unless it ships a valid SKILL.md skill package.

Issue: The source page is mostly marketing copy
Fix: Use docs, repo, package, or release pages as supporting sources, and mark unsupported claims as unverified.

Issue: Brand domain is unclear
Fix: Leave brand fields blank rather than guessing from GitHub, docs subdomains, or mirrors.