README Catalog Integrity Review Capability Pack Skill

Knowledge Freshness

This capability pack is grounded in HeyClaude CONTRIBUTING.md, content schema examples, and Claude Code skills documentation verified on 2026-06-16. Submission rules, validation scripts, and generated-artifact boundaries can change; prefer live repository docs and CI policy over cached assumptions.

Retrieval Sources

• https://github.com/JSONbored/awesome-claude/blob/main/CONTRIBUTING.md
• https://github.com/JSONbored/awesome-claude/blob/main/examples/content/SCHEMA.md
• https://code.claude.com/docs/en/skills
• https://github.com/anthropics/claude-code
• https://developers.google.com/search/docs/fundamentals/creating-helpful-content

Source Verification Notes

Verified against HeyClaude contribution docs and Claude Code skills documentation on 2026-06-16:

• HeyClaude content PRs should add exactly one raw content/<category>/<slug>.mdx file; README and registry outputs are generated by maintainer automation.
• Frontmatter requires verifiable source URLs, practical safety and privacy notes, and duplicate checks documented in the submission.
• Content schema examples define slug, category, and metadata fields that must align with on-disk paths for catalog integrity.
• Claude Code skills use SKILL.md-style reusable instructions; this pack adapts that pattern for catalog reviewers rather than runtime coding agents.
• Google Search Central helpful-content guidance supports evaluating whether catalog copy is useful and source-backed rather than promotional filler.

Scope Note

This is not a replacement for CI validators or maintainer merge bots. Use it as a reusable review workflow for humans and agents checking README catalog integrity before approving content submissions or investigating drift reports.

Core Workflow

1. Inventory changed files: confirm the PR touches one raw MDX source unless an explicit maintainer regeneration PR is in scope.
2. Map catalog rows to content/<category>/<slug>.mdx paths; flag slug or category mismatches.
3. Verify frontmatter URLs (documentationUrl, repoUrl, downloadUrl, authorProfileUrl, listed sourceUrls) for reachability and canonical choice.
4. Search for duplicates by title, slug, repo URL, docs domain, and overlapping purpose across content/ and open PRs.
5. Compare README or site catalog text against source frontmatter titles and descriptions for truncation or stale aliases.
6. Check generated-artifact boundaries: contributor PRs should not hand-edit README tables, lockfiles, or CI scripts without maintainer direction.
7. Assess safety and privacy notes against listed tools; flag generic placeholder notes that do not describe runtime risk.
8. Produce a pass/fail integrity summary with required fixes before merge.

Capability Scope

• Content file to catalog row mapping and slug alignment.
• Broken, redirected, or parked link inventory.
• Duplicate title, slug, repo, and documentation URL detection.
• Generated-artifact boundary violation surfacing.
• Source URL reachability and canonical URL assessment.
• Privacy-safe integrity reporting for PR or gate review.

Compatibility

Native

• Claude Code / Claude: use as an Agent Skill when reviewing HeyClaude content PRs, auditing README drift, or preparing maintainer triage notes.

Manual Adaptation

• Codex, Cursor, Windsurf, and Generic AGENTS workflows: use the workflow as a deterministic catalog review checklist in content ops runbooks.

Required Inputs

• PR diff or file list with category, slug, and frontmatter URLs.
• Reachability evidence for listed URLs (status code, final URL, date).
• Duplicate search results across content/ directories and open PRs.
• Policy context for one-file submissions and generated README boundaries.

Production Rules

• Prefer one canonical verifiable URL in documentationUrl; supporting links belong in sourceUrls or retrievalSources.
• Fail reviews when slug path disagrees with frontmatter slug or category.
• Do not approve catalogs listing entries whose primary docs return 404 or parked pages.
• Record verification date and concrete fetched facts in review output.
• Redact tokens, internal URLs, and customer examples from public summaries.
• Separate helpful-content quality from link reachability; both are required.

Review Matrix

Output Contract

1. Content file to catalog row mapping with slug alignment results.
2. Broken or redirected link inventory with final URLs.
3. Duplicate findings across title, slug, repo, and docs URL dimensions.
4. Generated-artifact boundary violations (if any).
5. Pass/fail recommendation with required fixes.
6. Privacy-safe integrity summary for PR or gate review.

Duplicate Check

Checked content/skills, content/guides, generated catalog text, and open pull requests for README catalog integrity, content catalog validation, and HeyClaude duplicate review workflows. source-backed-content-prs teaches submission authoring; agent-skills-retrieval-source-verification-capability-pack focuses on skill source URLs—not README row alignment against content/ paths. No existing skills entry provides a reusable README catalog integrity review capability pack with mapping workflow, review matrix, and output contract.

Editorial Disclosure

Submitted as an independent source-backed HeyClaude content entry by kiannidev. It is based on public HeyClaude contribution docs, content schema examples, Claude Code skills documentation, and Google Search Central helpful-content guidance. No paid placement, referral link, affiliate link, or vendor sponsorship is used.