This skill is deprecated. It was split into four focused skills. Do not run workflows from this file — load the matching sub-skill directly.
| Need | Load this skill instead |
|---|---|
| README (EN + localized mirror) + animated SVG header/footer | repo-readme-assets |
| LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, issue/PR templates, FUNDING | repo-community-files |
| description, topics, GitHub Pages link, community-health audit, 16-point checklist | repo-metadata-health |
| social preview (og:image) PNG 1280×640 | repo-social-preview |
The old scripts/references were moved into the four new skills:
generate_assets.py, validate_svg.py, extract_context.py + svg references → repo-readme-assetsvalidate_repo.py + community-checklist.md + repo-hygiene.yml example → repo-metadata-healthgenerate_social_preview.py + social-preview.md → repo-social-previewKeep this router for one release cycle for backward compatibility (global AGENTS.md
rules may still reference github-repo-hygiene), then delete the folder.
repo-* skill is applicable.This skill performs no repository edits. First identify whether the request concerns README assets, community/legal files, GitHub metadata, or the social preview. Load exactly the focused skill from the routing table and carry its verification gate into the final report.
The router’s output must name the selected sub-skill and explain why the other three were not selected. If the request spans areas, compose the focused skills explicitly instead of reviving the deprecated monolithic workflow.