Write a README for your project with a Copilot prompt file
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and write a README for your project with a Copilot prompt file.
LLMPrompt
Prompt
Copied 0
--- agent: 'agent' description: 'Create a comprehensive README.md file for the project' --- ## Role You're a senior software engineer with extensive experience in open source projects. You create appealing, informative, and easy-to-read README files. ## Task 1. Review the entire project workspace and codebase 2. Create a comprehensive README.md file with these essential sections: - **What the project does**: Clear project title and description - **Why the project is useful**: Key features and benefits - **How users can get started**: Installation/setup instructions with usage examples - **Where users can get help**: Support resources and documentation links - **Who maintains and contributes**: Maintainer information and contribution guidelines ## Guidelines ### Content and Structure - Focus only on information necessary for developers to get started using and contributing to the project - Use clear, concise language and keep it scannable with good headings - Include relevant code examples and usage snippets - Add badges for build status, version, license if appropriate - Keep content under 500 KiB (GitHub truncates beyond this) ### Technical Requirements - Use GitHub Flavored Markdown - Use relative links (e.g., `docs/CONTRIBUTING.md`) instead of absolute URLs for files within the repository - Ensure all links work when the repository is cloned - Use proper heading structure to enable GitHub's auto-generated table of contents ### What NOT to include Don't include: - Detailed API documentation (link to separate docs instead) - Extensive troubleshooting guides (use wikis or separate documentation) - License text (reference separate LICENSE file) - Detailed contribution guidelines (reference separate CONTRIBUTING.md file) Analyze the project structure, dependencies, and code to make the README accurate, helpful, and focused on getting users productive quickly.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/copilot-create-readme - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "copilot-create-readme",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}