agentleFS
bestdeejay-designbestdeejay-design/agent-skills/skills/repo-community-files/SKILL.md

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

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
  1. Very specific:

    Use this skill to create or update the community/legal files of a repository: LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, …

    line 14
  2. Very specific:

    Do not use for README assets, metadata, or social previews.

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

FilePurposeWhen to update
LICENSEMIT license (owner/year)on creation, owner change
CODE_OF_CONDUCT.mdContributor Covenant 2.1 (full text + contact)rarely
CONTRIBUTING.mdContributor instructionson process/convention change
SECURITY.mdSecurity policyon contact/policy change
SUPPORT.mdUPPERCASE filename; "Support" link in issue helperrarely
.github/ISSUE_TEMPLATE/*.ymlIssue forms (bug_report, feature_request) — drive the Community Health checkon process change
.github/pull_request_template.mdPR template (root/docs//.github/, .md/.txt)on process change
.github/release.ymlAuto-generated release notes configon first release
FUNDING.ymlOptional: "Sponsor" buttonrarely
CHANGELOG.mdOptional: Keep a Changelog formaton each release

LICENSE must NOT be moved into .github/ — GitHub recognizes it only at the repo root or docs/ (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.
  • LICENSE placed under .github/ (not detected).
  • Outdated contacts in SECURITY.md / CODE_OF_CONDUCT.md.
  • Issue templates as .md instead of .yml forms (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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.