validate-learning-repo · git:20261117.ab63f92 · 2026-11-17 · sha256 ee28fce001add751

validate-learning-repo git:20261117.ab63f92A

Immutable. This exact content never changes and is served at /api/v1/blob/ee28fce001add751.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7l6teamzuk7vyx34/ee28fce001add75114c7b4654fa02e40ab79ee1ae664e1b16098ea65d11478c6.json

Then /plugin install validate-learning-repo@markdownregistry-7l6teamzuk7vyx34 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: validate-learning-repo
description: Audits this repository's teaching content against the real file structure. Use when checking README examples, AGENTS.md, CLAUDE.md, .claude/, .github/, or shared skills for accuracy and consistency.
---

# Validate learning repo

Use this skill when the task is to verify that the repository still teaches the right thing and that examples still match reality.

## Workflow

1. Read `references/checklist.md`.
2. Run `scripts/check-required-files.sh`.
3. Compare:
   - `README.md`
   - `AGENTS.md`
   - `CLAUDE.md`
   - `.claude/`
   - `.github/`
   - `skills/`
4. Look for:
   - missing referenced files
   - missing `AGENTS.md` command entries (a repo convention)
   - repo guidance that teaches a required section or workflow but does not include it in practice
   - example trees that no longer match the repository
   - invalid agent or skill naming
   - duplicated guidance in the wrong layer
   - unsupported or invented conventions
5. Format findings with `assets/report-template.md`.

## Output requirements

- Group findings into:
  - broken or misleading
  - should improve
  - already good
- Prefer exact file paths.
- Be concrete.
- Do not suggest abstract "best practices" unless they clearly apply to this repo.