scan-community-repos

Scanning community repositories for SKILL.md files involves processing GitHub URLs and local paths to verify accessibility, extract skill metadata, and generate a JSON catalog summarizing readiness and incompatibility.

Cataloging skill compatibility across multiple GitHub repositories is done by automating discovery and assessment, producing a markdown report and a machine-readable JSON catalog that labels each skill as ready, normalizable, or incompatible for batch import.

Yes, you can use local paths alongside GitHub URLs to check skill compatibility. The scanner accepts a mixed list of both sources, handling accessibility checks and extracting skill metadata from each valid path.

Classifying SKILL.md files as ready, normalizable, or incompatible is achieved by parsing frontmatter and body structure against required metadata, producing a clear view of which skills are ready for batch import.

Scanning repositories for skill metadata generates two output formats: a human-readable markdown report summarizing results and a machine-readable JSON catalog designed for downstream batch normalization.

A SKILL.md file shows up as incompatible during a repository scan when it fails required metadata checks after frontmatter and body structure parsing, indicating it cannot be normalized for batch import.