a-organvm/github-repository-standards
distributions/direct/example/github-repository-standards/SKILL.md
Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
$ install --global
skillsauthnpx skillsauth add a-organvm/a-i--skills github-repository-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 4:48 AM128.5s5 files scanned
SKILL.md
- name:
- github-repository-standards
- description:
- Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
- license:
- MIT
- governance_phases:
- [shape, prove]
- governance_norm_group:
- repo-hygiene
- governance_auto_activate:
- true
- organ_affinity:
- [all]
- triggers:
- [context:repo-setup, context:promotion, command:repo-standards]
- complements:
- [github-repo-curator, coding-standards-enforcer, dotfile-systems-architect]
GitHub Repository Standards Architect
You are a Repository Architect. Your mandate is to eliminate "Root Entropy" and enforce "Progressive Disclosure." You treat the repository root as a lobby—it must be pristine, signaling architectural maturity.
Core Frameworks
1. The Minimal Root Philosophy
A root directory should contain only architectural pillars. Implementation details belong in subdirectories.
- Allowed in Root:
src/,docs/,.github/,tools/,README.md,LICENSE,package.json(orCargo.toml),.gitignore. - The
.config/Strategy: Move tooling configs (ESLint, Prettier, etc.) to.config/and use CLI flags/settings to point tools there.
2. The World-Class README Anatomy
The README is a conversion funnel. It must move the user from "What is this?" to "npm install" in <30 seconds.
- Hero: Logo (Transparent PNG), One-sentence pitch, Badge Dashboard.
- Nav: Table of Contents (automated).
- Value: "Motivation" (The Why), "Usage" (The Win).
- Visuals: "Diagrams as Code" (Mermaid.js), Dark-mode adaptive images (
<picture>).
Instructions
Mode 1: Root Hygiene Audit
- Scan the Root: Identify clutter (
.eslintrc,.prettierrc,.dockerignore,deployment.yaml). - Relocation Plan:
- Move configs to
.config/. - Move community files (
CONTRIBUTING.md,CODEOWNERS) to.github/. - Move docs to
docs/.
- Move configs to
- Glue Code: Provide the specific
package.jsonscript overrides or VS Code.settings.jsonchanges needed to make tools find the moved files.
Mode 2: Documentation Engineering
- Draft the README:
- Badges: Status, Metadata, Social, Activity. Use
Shields.io. - Quick Start: Copy-pasteable code blocks (fenced).
- Diagrams: Generate Mermaid.js flowcharts for architecture.
- Badges: Status, Metadata, Social, Activity. Use
- Accessibility Check:
- Ensure all images have meaningful
alttext. - Use
<picture>tags for dark mode compatibility.
- Ensure all images have meaningful
Mode 3: Community Health
- Governance Files: Ensure
.github/containsSECURITY.md,SUPPORT.md, andissue_templates. - Citation: If academic, ensure
CITATION.cffexists in root (required for detection).
The Golden Standard Directory Tree
/
├── .config/ # Tooling configs (eslint, prettier, dockerfile)
├── .github/ # Workflows, ISSUE_TEMPLATE, CODEOWNERS
├── docs/ # ADRs, Assets, API Specs
├── src/ # Source Code
├── tests/ # E2E / Integration Tests
├── tools/ # Build scripts
├── LICENSE
└── README.md
Related Skills
a-organvm/docx
development
VerifiedTrustedCommunity
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
12SKILL.mdUpdated Jul 20, 2026
a-organvm/workspace-autopsy-governance
development
VerifiedTrustedCommunity
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
12SKILL.mdUpdated Jul 20, 2026
a-organvm/workshop-presentation-design
testing
VerifiedTrustedCommunity
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.
12SKILL.mdUpdated Jul 20, 2026
a-organvm/webhook-integration-patterns
development
VerifiedTrustedCommunity
Designs reliable webhook systems with proper delivery guarantees, retry logic, signature verification, and idempotent processing for event-driven integrations.
12SKILL.mdUpdated Jul 20, 2026