Creates comprehensive README files with templates for different project types. Use when creating README, project documentation, or getting started guides.
Pro scans all 3 files and shows the line behind each finding
Scanned 2/12/2026
npx -y skills add armanzeroeight/fastagent-plugins --skill readme-generator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Readme Generator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/armanzeroeight-readme-generator)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: readme-generator
description: Creates comprehensive README files with templates for different project types. Use when creating README, project documentation, or getting started guides.
---
# README Generator
## Quick Start
Generate a README based on project type:
```bash
# Detect project type
ls package.json && echo "Node.js project" || \
ls setup.py pyproject.toml && echo "Python project" || \
ls go.mod && echo "Go project"
```
## Instructions
### Step 1: Analyze Project
Gather project information:
- Project name (from package.json, pyproject.toml, etc.)
- Description (from manifest or git)
- Main language and framework
- Key features (scan source files)
- Dependencies (from manifest files)
### Step 2: Select Template
Choose template based on project type:
| Type | Template | Key Sections |
|------|----------|--------------|
| Library | library | Installation, API, Examples |
| CLI Tool | cli | Installation, Commands, Options |
| Web App | webapp | Features, Setup, Deployment |
| API | api | Endpoints, Authentication, Examples |
### Step 3: Generate Core Sections
**Title and Description:**
```markdown
# Project Name
Brief one-line description of what the project does.
[](LICENSE)
[](package.json)
```
**Installation:**
```markdown
## Installation
\`\`\`bash
npm install project-name
# or
pip install project-name
\`\`\`
```
**Usage:**
```markdown
## Usage
\`\`\`javascript
const project = require('project-name');
// Basic example
project.doSomething();
\`\`\`
```
### Step 4: Add Project-Specific Content
Include relevant sections:
- **Features**: Bullet list of key capabilities
- **API Reference**: For libraries
- **Configuration**: For configurable tools
- **Examples**: Real-world use cases
- **Contributing**: How to contribute
- **License**: License information
### Step 5: Add Badges and Links
Common badges:
```markdown



```
## README Structure
### Essential Sections (all projects)
1. **Title and Description**
2. **Installation**
3. **Quick Start / Usage**
4. **License**
### Recommended Sections
5. **Features** - What makes it useful
6. **Documentation** - Link to full docs
7. **Examples** - Common use cases
8. **Contributing** - How to help
9. **Support** - Where to get help
### Optional Sections
10. **Requirements** - System dependencies
11. **Configuration** - Setup options
12. **Troubleshooting** - Common issues
13. **Changelog** - Recent changes
14. **Acknowledgments** - Credits
## Advanced
For detailed information, see:
- [Templates](reference/templates.md) - README templates by project type
- [Best Practices](reference/best-practices.md) - Documentation standards and style guide
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!