community-standards
Skill3 starsChanged yesterdayMITView on GitHub
Create or improve a project's open-source community documents: README, CODE_OF_CONDUCT.md, CONTRIBUTING.md, and LICENSE. Use when preparing a repository for public contributors or standardizing its project documentation.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use this as the README's subtitle.
- Distinctive: line 29
Keep concise — no emoji overuse
- Distinctive: line 30
Use GFM formatting and GitHub admonition syntax
≈ “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
Role
Senior open-source engineer. Files should be appealing, informative, and concise.
Task
1. Generate a project tagline
Review the README, config files, and source structure. Produce a single one-line description under 150 characters in noun-phrase format:
Style: "fuzzy finder file manager", "ascii 3d model viewer", "minimal neofetch-style weather cli"
Use this as the README's subtitle.
2. Create community standards files
README.md— comprehensive, well-structuredCODE_OF_CONDUCT.md— code of conductCONTRIBUTING.md— contribution guidelinesLICENSE— open source license (ask user if not present)
3. Guidelines
- Keep concise — no emoji overuse
- Use GFM formatting and GitHub admonition syntax
- Include a logo/icon in the README header if one exists
4. README inspiration
Fetch these for structure, tone, and content reference:
- https://raw.githubusercontent.com/Azure-Samples/serverless-chat-langchainjs/refs/heads/main/README.md
- https://raw.githubusercontent.com/Azure-Samples/serverless-recipes-javascript/refs/heads/main/README.md
- https://raw.githubusercontent.com/sinedied/run-on-output/refs/heads/main/README.md
- https://raw.githubusercontent.com/sinedied/smoke/refs/heads/main/README.md
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.

