repo-community-files
Skill6 starsChanged 3 months agoMITView on GitHub
Create and maintain repository community/legal files: LICENSE, CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, SUPPORT.md, issue/PR templates, FUNDING.yml. No scripts — template-driven. Triggers: 'license file', 'code of conduct', 'contributing guide', 'security policy', 'support file', 'issue template', 'pr template', 'funding yml', 'community files', 'repo legal files', 'contributor covenant'.
In this repository59 other files it gives its agents.
- skills/chronos/references/AGENTS.mdAGENTS.md
- api-contract-testingSkill
- api-doc-generatorSkill
- canonSkill
- censorSkill
- changelog-generatorSkill
- chronosSkill
- code-reviewSkill
- commit-lintSkill
- commit-message-writerSkill
- coverage-analyzerSkill
- csv-proSkill
- data-analysisSkill
- deweySkill
- diagram-makerSkill
- doc-compareSkill
- docs-productSkill
- docs-projectSkill
- docs-systemSkill
- dsh-runnerSkill
- frontend-a11ySkill
- frontend-design-tasteSkill
- frontend-perfectionSkill
- frontend-performanceSkill
- frontend-testingSkill
- github-repo-hygieneSkill
- long-running-agent-workflowSkill
- mermaid-to-imageSkill
- mobile-frontendSkill
- pdf-report-builderSkill
- plan-skillSkill
- prd-to-appSkill
- presentation-craftSkill
- presentation-engineeringSkill
- presentation-makerSkill
- raster-to-svgSkill
- reddit-karmaSkill
- repo-metadata-healthSkill
- repo-readme-assetsSkill
- repo-social-previewSkill
- secret-scannerSkill
- security-reviewSkill
- seo-auditSkill
- seo-contentSkill
- seo-crawlSkill
- seo-schemaSkill
- seo-toolkitSkill
- skill-feedbackSkill
- skill-forgeSkill
- skill-suggesterSkill
- sql-helperSkill
- systematic-debuggerSkill
- test-generatorSkill
- test-graphicsSkill
- velesSkill
- version-bumperSkill
- video-script-writerSkill
- web-replicationSkill
- web-scraperSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use this skill to create or update the community/legal files of a repository: LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, …
- Very specific: line 72
Do not use for README assets, metadata, or social previews.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo Community Files — legal & community health files
Use this skill to create or update the community/legal files of a repository: LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, issue/PR templates, FUNDING.
These files drive the GitHub Community Standards checklist (the "Community Health" percentage). Missing files lower the score and block contributions.
When to use
- A new repository needs its legal/community files set up.
- A file is missing or outdated (e.g. SECURITY contact changed, CONTRIBUTING process changed).
- User asks for "license file", "code of conduct", "contributing guide", "security policy", "issue template", "pr template", "funding".
Do NOT use
- For README content/visuals — use
repo-readme-assets. - For description/topics/Pages/community-health audit — use
repo-metadata-health. - For social preview PNG — use
repo-social-preview.
Files
SKILL.md— this file (template-driven; no scripts)
Required / desirable files
| File | Purpose | When to update |
LICENSE | MIT license (owner/year) | on creation, owner change |
CODE_OF_CONDUCT.md | Contributor Covenant 2.1 (full text + contact) | rarely |
CONTRIBUTING.md | Contributor instructions | on process/convention change |
SECURITY.md | Security policy | on contact/policy change |
SUPPORT.md | UPPERCASE filename; "Support" link in issue helper | rarely |
.github/ISSUE_TEMPLATE/*.yml | Issue forms (bug_report, feature_request) — drive the Community Health check | on process change |
.github/pull_request_template.md | PR template (root/docs//.github/, .md/.txt) | on process change |
.github/release.yml | Auto-generated release notes config | on first release |
FUNDING.yml | Optional: "Sponsor" button | rarely |
CHANGELOG.md | Optional: Keep a Changelog format | on each release |
LICENSEmust NOT be moved into.github/— GitHub recognizes it only at the repo root ordocs/(default files in.github/are NOT scanned for license).
Org-level defaults
GitHub supports organization-level community health files via a special .github
repository. Files not found in a repo are inherited from the org .github repo — except
LICENSE (never inherited). Prefer org-level defaults for boilerplate, keep repo-level
copies for repo-specific policies.
Anti-patterns
- Public repo without a LICENSE.
- Accepting contributions without SECURITY.md.
LICENSEplaced under.github/(not detected).- Outdated contacts in SECURITY.md / CODE_OF_CONDUCT.md.
- Issue templates as
.mdinstead of.ymlforms (forms add the Community Health check).
Boundaries
- Do not use for README assets, metadata, or social previews; use the focused
repo-*skills.
Evidence and completion gate
Ground recommendations in the supplied repository or brief. State assumptions, missing inputs, and unresolved risks. Return a concrete artifact or checklist with an owner/action for each open item, then verify that the result answers the requested goal rather than merely repeating the framework.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

