repo-community-files

Solid

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

AI & Automation 5 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 (bu...

Details

Author
bestdeejay-design
Repository
bestdeejay-design/agent-skills
Created
1 weeks ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

oss-community

Create the community and governance files an open source project needs: CONTRIBUTING, CODE_OF_CONDUCT, SECURITY.md, issue forms and pull request templates, CODEOWNERS, FUNDING, and the license file, and set the forge project's description, topics, and homepage. Use when starting a new open source project, opening a private repo to the public, when a repo is missing its community health files, or when its issue templates collect reports that still cannot be triaged. Covers GitHub and GitLab. README structure belongs to oss-readme.

1 Updated today
svyatov
AI & Automation Solid

repo-metadata-health

Audit and update GitHub repository metadata and community health: description (gh repo edit), topics (PUT /repos/topics, max 20), GitHub Pages link + homepage, community-health percentage via the Community Profile API, and a 16-point check checklist. Script: validate_repo.py (gh API + filesystem, auto-detect from git remote). Triggers: 'repo description', 'repo topics', 'github topics', 'github pages', 'community health', 'repo audit', 'repo metadata', 'repo checklist', 'health percentage', 'repo about'.

5 Updated yesterday
bestdeejay-design
Data & Documents Listed

contributor-setup

Analyzes a repo's contributor experience and creates or updates what's missing: GitHub issue-form templates (bug/feature/refactor), an open-source target-group-focused README, CONTRIBUTING.md, and the remaining community-health files (PR template, CODE_OF_CONDUCT, SECURITY, LICENSE, CODEOWNERS). Use when asked to make a repo contributor-friendly, open-source ready, or to set up issue templates / README / CONTRIBUTING.

0 Updated today
emaarco