igniteui/ai-repo-structure · Archived

validate-learning-repo

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.

First seen Jul 19, 2026

Installation

$ npx skills add igniteui/ai-repo-structure --skill validate-learning-repo

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from igniteui/ai-repo-structure.

npx skills add igniteui/ai-repo-structure

Browse all from igniteui/ai-repo-structure

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,262 B
  • docs SUMMARY.md 228 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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/

  1. Look for:

- missing referenced files - missing required AGENTS.md command entries - 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

  1. 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.