Back to skills
SKILL.md
Doc Formatter
ASecurityFormat documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
- 666 stars
- 0 votes
- 0 copies
- 2 views
- Added February 8, 2026
Works with
Security analysis
100/100npx -y skills add majiayu000/claude-skill-registry --skill doc-formatter --agent claude-codeAre you the author of Doc Formatter?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-doc-formatter)---
name: doc-formatter
description: Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
---
# Documentation Formatter
Ensures all documentation has consistent formatting with emojis, status indicators, and version tracking.
## Required Elements
### 1. Emojis for Section Headers
Use these emojis consistently:
| Section | Emoji |
|---------|-------|
| Overview/About | π |
| Features | β¨ |
| Installation | π¦ |
| Quick Start | π |
| Usage | π‘ |
| Configuration | βοΈ |
| API/Reference | π |
| Examples | π |
| Testing | π§ͺ |
| Deployment | π |
| Contributing | π€ |
| Changelog | π |
| License | π |
| Warning/Caution | β οΈ |
| Important | β |
| Tip/Note | π‘ |
| Success | β
|
| Error/Fail | β |
| In Progress | π |
| Deprecated | β |
### 2. Status Bars (Shields.io Badges)
Include at the top of every README:
```markdown



```
#### Status Options
- `Active` (green/success)
- `Maintenance` (yellow/warning)
- `Deprecated` (red/critical)
- `Beta` (blue/informational)
- `Alpha` (purple)
### 3. Versioning Matrix
Include a compatibility/version matrix table:
```markdown
## π Version Matrix
| Version | Status | Release Date | Node | Python | Notes |
|---------|--------|--------------|------|--------|-------|
| 3.0.0 | β
Current | Dec 2025 | 18+ | 3.9+ | Major refactor |
| 2.1.0 | π Maintained | Nov 2025 | 16+ | 3.8+ | Security fixes only |
| 1.x.x | β Deprecated | Oct 2024 | 14+ | 3.7+ | No longer supported |
```
Adapt columns based on project type (languages, frameworks, APIs, etc.)
## Template
```markdown
<div align="center">
# π Project Name
Brief description here.



</div>
---
## β¨ Features
- Feature 1
- Feature 2
## π Quick Start
1. Step one
2. Step two
## π Version Matrix
| Version | Status | Release Date | Notes |
|---------|--------|--------------|-------|
| 1.0.0 | β
Current | Dec 2025 | Initial release |
## βοΈ Configuration
Configuration details...
## π API Reference
API documentation...
## π§ͺ Testing
How to run tests...
## π€ Contributing
Contribution guidelines...
## π Changelog
See [CHANGELOG.md](CHANGELOG.md)
## π License
License information...
---
*Last Updated: December 2025*
```
## Formatting Rules
1. **Every major section** gets an emoji prefix
2. **Status badges** go at the top, centered
3. **Version matrix** required for any project with releases
4. **Tables** should use emoji status indicators (β
β π β)
5. **Code blocks** should specify language for syntax highlighting
6. **Links** should be descriptive, not "click here"
## When to Apply
Apply this formatting when:
- Creating new README.md files
- Updating existing documentation
- Writing spec documents
- Creating CHANGELOG files
- Any markdown file in the project
Attribution
Comments
Loading commentsβ¦
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.