readme-generator

Q: How do I install readme-generator?

Run npx skills add https://github.com/wedsamuel1230/embedded-engineering-skills --skill readme-generator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/readme-generator/ (personal) or .claude/skills/readme-generator/ (project).

by wedsamuel1230Docs & Writing

Auto-generates professional README.md files for Arduino/ESP32/RP2040 projects following open-source best practices. Use when user wants to document their project for GitHub, needs help writing a README, or says "make my project shareable". Follows awesome-readme standards with sections for Overview, Hardware, Software, Setup, Usage, Troubleshooting, and Contributing.

Installs: 135
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/wedsamuel1230/embedded-engineering-skills --skill readme-generator

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads readme-generator automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

README Generator

Creates professional, beginner-friendly README files for maker projects.

Resources

This skill includes bundled tools:

scripts/generate_readme.py - Full README generator with wiring diagrams and templates

Quick Start

Interactive mode:

uv run --no-project scripts/generate_readme.py --interactive

Quick generation:

uv run --no-project scripts/generate_readme.py --project "Weather Station" --board "ESP32" --output README.md

Scan existing project:

uv run --no-project scripts/generate_readme.py --scan /path/to/arduino/project --output README.md

When to Use

"Help me document this project"
"I want to share this on GitHub"
"Write a README for my project"
User has working project, needs documentation
Before publishing to GitHub/Instructables

Information Gathering

Ask User For:

1. Project name and one-line description
2. What problem does it solve / why did you build it?
3. Main features (3-5 bullet points)
4. Hardware components used
5. Software libraries required
6. Any photos/videos/GIFs available?
7. License preference (MIT recommended for open source)
8. Target audience (beginners/intermediate/advanced)

Auto-Extract From Code:

Pin assignments from config.h
Library includes
WiFi/Bluetooth features
Sensor types

README Template

Generate using this structure (based on awesome-readme best practices):

# 🎯 [Project Name]

![Project Status](https://img.shields.io/badge/status-active-brightgreen)
![Platform](https://img.shields.io/badge/platform-ESP32-blue)
![License](https://img.shields.io/badge/license-MIT-green)

> One-line description of what this project does and why it's useful.

![Project Photo/GIF](images/project-demo.gif)

## 📋 Table of Contents

- [Overview](#overview)
- [Features](#features)
- [Hardware Components](#hardware-components)
- [Wiring Diagram](#wiring-diagram)
- [Software Dependencies](#software-dependencies)
- [Installation](#installation)
- [Configuration](#configuration)
- [Usage](#usage)
- [Troubleshooting](#troubleshooting)
- [Contributing](#contributing)
- [License](#license)
- [Acknowledgments](#acknowledgments)

## 🔍 Overview

[2-3 paragraphs explaining:]
- What the project does
- Why you built it / what problem it solves
- Who it's for (target audience)

### Demo

[Embed video or GIF showing project in action]

## ✨ Features

- ✅ Feature 1 - brief description
- ✅ Feature 2 - brief description
- ✅ Feature 3 - brief description
- 🚧 Planned: Feature 4 (coming soon)

## 🔧 Hardware Components

| Component | Quantity | Purpose | Notes |
|-----------|----------|---------|-------|
| [MCU Board] | 1 | Main controller | [version/variant] |
| [Sensor 1] | 1 | [function] | [I2C address, etc.] |
| [Display] | 1 | User interface | [resolution] |
| ... | ... | ... | ... |

**Estimated Cost:** $XX-XX

### Where to Buy

- [Component 1](link) - Amazon/AliExpress
- [Component 2](link) - Adafruit/SparkFun

## 📐 Wiring Diagram

![Wiring Diagram](images/wiring-diagram.png)

### Pin Connections

| MCU Pin | Component | Pin | Function |
|---------|-----------|-----|----------|
| GPIO21 | BME280 | SDA | I2C Data |
| GPIO22 | BME280 | SCL | I2C Clock |
| GPIO4 | LED | Anode | Status indicator |
| ... | ... | ... | ... |

## 💻 Software Dependencies

### Required Software

- [Arduino IDE](https://www.arduino.cc/en/software) (v2.0+) or [PlatformIO](https://platformio.org/)
- [Board package] - [installation link]

### Required Libraries

| Library | Version | Purpose | Install via |
|---------|---------|---------|-------------|
| [Library1] | >=1.0.0 | [function] | Library Manager |
| [Library2] | >=2.3.0 | [function] | Library Manager |
| ... | ... | ... | ... |

## 📦 Installation

### Option 1: Arduino IDE

1. **Install Arduino IDE**
   - Download from [arduino.cc](https://www.arduino.cc/en/software)
   
2. **Add Board Support** (if using ESP32/RP2040)

File → Preferences → Additional Board Manager URLs: https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json

Then: Tools → Board → Boards Manager → Search "[board]" → Install

3. **Install Required Libraries**
- Sketch → Include Library → Manage Libraries
- Search and install each library from the table above

4. **Clone or Download This Repository**
```bash
git clone https://github.com/[username]/[repo-name].git

Or download ZIP and extract

Open the Project
- Open [project-name].ino in Arduino IDE

Option 2: PlatformIO (Recommended for Advanced Users)

Install VS Code + PlatformIO extension

Clone and open:

git clone https://github.com/[username]/[repo-name].git
cd [repo-name]
code .

PlatformIO will automatically install dependencies from platformio.ini

⚙️ Configuration

Before uploading, customize config.h:

// === NETWORK SETTINGS ===
#define WIFI_SSID     "your-wifi-name"
#define WIFI_PASSWORD "your-wifi-password"

// === HARDWARE PINS ===
#define LED_PIN       4
#define SENSOR_SDA    21
#define SENSOR_SCL    22

// === FEATURE FLAGS ===
#define ENABLE_OLED   true
#define ENABLE_WIFI   true
#define DEBUG_MODE    true

Environment-Specific Settings

Setting	Development	Production
DEBUG_MODE	true	false
SERIAL_BAUD	115200	9600
SLEEP_INTERVAL	10s	300s

🚀 Usage

Basic Operation

Power On - Connect USB or battery
Wait for Boot - Status LED blinks during initialization
[Normal Operation] - Description of what happens

LED Status Indicators

LED State	Meaning
Solid Green	Normal operation
Blinking Blue	WiFi connecting
Red Flash	Error (check serial)

Serial Monitor

Open Serial Monitor at 115200 baud to see:

[BOOT] Project Name v1.0.0
[INFO] Initializing sensors...
[OK] BME280 found at 0x76
[INFO] Connecting to WiFi...
[OK] Connected: 192.168.1.100
[DATA] Temp: 23.5°C, Humidity: 45%

Web Interface (if applicable)

Navigate to http://[device-ip] to access:

Real-time sensor readings
Configuration panel
Data export

❓ Troubleshooting

Common Issues

<details> <summary>Upload fails: "Failed to connect"</summary>

ESP32: Hold BOOT button while clicking Upload, release when "Connecting..." appears.

Arduino: Check correct COM port selected in Tools → Port.

</details> <details> <summary>Sensor not detected</summary>

Check wiring (SDA/SCL not swapped?)
Run I2C scanner sketch to verify address
Add pull-up resistors (4.7kΩ) if not on module
Check voltage compatibility (3.3V vs 5V)

</details> <details> <summary>WiFi won't connect</summary>

Verify SSID/password in config.h (case-sensitive!)
2.4GHz only (ESP32 doesn't support 5GHz)
Check router isn't blocking new devices
Try moving closer to router

</details> <details> <summary>Random resets</summary>

Power supply too weak - use 500mA+ source
Add 100µF capacitor near MCU
Check for short circuits
Disable brownout detector (ESP32)

</details>

Still Stuck?

Check Issues for similar problems
Open a new issue with:
- Hardware setup (board, sensors)
- Error messages (full serial output)
- Steps to reproduce

🤝 Contributing

Contributions are welcome! Here's how:

Reporting Bugs

Check existing issues first
Use the bug report template
Include serial output and hardware details

Suggesting Features

Open an issue with [Feature Request] prefix
Describe use case and expected behavior

Pull Requests

Fork the repository
Create a feature branch: git checkout -b feature/amazing-feature
Make your changes
Test thoroughly
Commit: git commit -m 'Add amazing feature'
Push: git push origin feature/amazing-feature
Open a Pull Request

Code Style

Use meaningful variable names
Comment complex logic
Follow existing formatting
Test on actual hardware before PR

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

MIT License

Copyright (c) [year] [author]

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

🙏 Acknowledgments

[Library/Project] - for [what it provides]
[Person/Tutorial] - inspiration/guidance
[Community] - testing and feedback

📬 Contact

[Your Name] - @twitter_handle - email@example.com

Project Link: https://github.com/[username]/[repo-name]

⭐ If this project helped you, please give it a star!


---

## Section Guidelines

### Good vs Bad Examples

**Project Description:**

❌ Bad: "An Arduino project with sensors" ✅ Good: "Battery-powered environmental monitor that tracks temperature, humidity, and air quality, sending alerts when thresholds are exceeded"


**Features:**

❌ Bad: "Has WiFi" ✅ Good: "📶 WiFi connectivity with automatic reconnection and OTA updates"


**Installation Steps:**

❌ Bad: "Install the libraries and upload" ✅ Good: Step-by-step with screenshots, version numbers, exact menu paths


### Visual Assets

**Recommended:**
- Project photo (hero image)
- Wiring diagram (Fritzing or hand-drawn)
- Demo GIF (< 5MB, 10-15 seconds)
- Schematic (KiCad export)

**Creating GIFs:**
- Use ScreenToGif (Windows) or Peek (Linux)
- Optimize with ezgif.com
- Keep under 5MB for GitHub

### Badges

```markdown
<!-- Status badges -->
![Build Status](https://img.shields.io/badge/build-passing-brightgreen)
![Version](https://img.shields.io/badge/version-1.0.0-blue)
![License](https://img.shields.io/badge/license-MIT-green)

<!-- Platform badges -->
![Arduino](https://img.shields.io/badge/platform-Arduino-00979D?logo=arduino)
![ESP32](https://img.shields.io/badge/platform-ESP32-blue)
![Raspberry Pi](https://img.shields.io/badge/platform-RPi_Pico-C51A4A)

<!-- Social badges -->
![GitHub stars](https://img.shields.io/github/stars/user/repo)
![GitHub forks](https://img.shields.io/github/forks/user/repo)

File Structure Recommendation

project-name/
├── README.md              # Main documentation
├── LICENSE                # MIT license file
├── .gitignore            # Ignore build files
├── src/
│   ├── main.ino          # Main sketch
│   └── config.h          # User configuration
├── lib/                  # Local libraries (optional)
├── docs/
│   ├── WIRING.md         # Detailed wiring guide
│   ├── API.md            # API documentation (if applicable)
│   └── CHANGELOG.md      # Version history
├── images/
│   ├── project-photo.jpg
│   ├── wiring-diagram.png
│   └── demo.gif
├── hardware/             # PCB/enclosure files (optional)
│   ├── schematic.pdf
│   └── enclosure.stl
└── examples/             # Additional example sketches
    └── basic/

Quick README Checklist

Before publishing, verify:

□ Project name is clear and memorable
□ One-line description explains the "what" and "why"
□ Hero image/GIF shows project in action
□ All hardware components listed with links
□ Wiring diagram included
□ All libraries listed with versions
□ Step-by-step installation instructions
□ Configuration section explains all settings
□ Usage section shows expected output
□ Troubleshooting covers common issues
□ License file present
□ Contact information included
□ No broken links
□ Spelling/grammar checked

Shared Output Contract

Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.

FAQ

What does the readme-generator skill do?

How do I install readme-generator?

Run npx skills add https://github.com/wedsamuel1230/embedded-engineering-skills --skill readme-generator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/readme-generator/ (personal) or .claude/skills/readme-generator/ (project).

Which AI agents can use readme-generator?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is readme-generator safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains readme-generator?

It is published by wedsamuel1230 in wedsamuel1230/embedded-engineering-skills. It has 135 recorded installs.