create-readme — GitHub Copilot skill: what it does, install
This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code.
npx skills add github/awesome-copilot --skill create-readmeWhat create-readme does
create-readme reviews the full project and workspace, then creates a README.md. It organizes the document with GitHub Flavored Markdown and uses GitHub admonition syntax where it fits. When the project contains a logo or icon, the skill can place it in the README header.
The generated file leaves out LICENSE, CONTRIBUTING, and CHANGELOG sections because those have dedicated files. The instructions also keep emoji use limited and the README concise. Install it when documentation should reflect the repository itself; it is a poor fit when you need a tightly controlled manual template.
What it helps with
- create a README.md from the project contents
- document a repository with GFM formatting
- add a discovered project logo or icon to the README header
- leave LICENSE and CHANGELOG sections out of the README
Example prompts for the agent
- Review the whole workspace and create a README.md for this project.
- Update README.md from the current codebase, using GFM and GitHub admonitions where appropriate.
- Create a concise README.md without LICENSE, CONTRIBUTING, or CHANGELOG sections.
How to install create-readme
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill create-readme2GitHub CLI
gh skill install github/awesome-copilot create-readme3Manually: put the files in place
.github/skills/create-readme/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill create-readme -a claude-code2Manually: put the files in place
~/.claude/skills/create-readme/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-readme/
Manually: put the files in place
.agents/skills/create-readme/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/create-readme/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/create-readmeManually: put the files in place
.devin/skills/create-readme/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about create-readme
How do I install create-readme in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill create-readme, then use .github/skills/create-readme/SKILL.md.
What does create-readme do?
It reviews the project and workspace, then creates a structured README.md in GitHub Flavored Markdown. It can also use a project logo or icon in the README header.
Which sections does create-readme leave out?
It leaves out LICENSE, CONTRIBUTING, and CHANGELOG sections. These are expected to live in dedicated files.
Source text
SKILL.md · MIT
--- name: create-readme description: 'Create a README.md file for the project' --- ## Role You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read. ## Task 1. Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project. 2. Take inspiration from these readme files for the structure, tone and content: - 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 3. Do not overuse emojis, and keep the readme concise and to the point. 4. Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections. 5. Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate. 6. If you find a logo or icon for the project, use it in the readme's header.
© github · MIT · github/awesome-copilot