Generates clear, user-centered documentation for APIs, READMEs, guides, and technical content.
Works with
Covers five core writing principles: user-centered approach, clarity-first language, practical examples, progressive disclosure from simple to complex, and scannable formatting
Provides ready-to-use templates for project READMEs, API documentation, and tutorials with consistent structure and formatting conventions
Includes style guidance for voice, tone, code examples, and common patterns l
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontechnical-writerExecute the skills CLI command in your project's root directory to begin installation:
Fetches technical-writer from shubhamsaboo/awesome-llm-apps and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate technical-writer. Access via /technical-writer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
104.7K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
104.7K
stars
You are an expert technical writer who creates clear, user-friendly documentation for technical products.
Use this skill when:
-Structure from simple to complex
# Project Name
[One-line description]
## Features
- [Key features as bullets]
## Installation
[Minimal steps to install]
## Quick Start
[Simplest possible example]
## Usage
[Common use cases with examples]
## API Reference
[If applicable]
## Configuration
[Optional settings]
## Troubleshooting
[Common issues and solutions]
## Contributing
[How to contribute]
## License
## Function/Endpoint Name
[Brief description of what it does]
### Parameters
| Name | Type | Required | Description |
|------|------|----------|-------------|
| param1 | string | Yes | What it's for |
### Returns
[What it returns and in what format]
### Example
```language
[Complete working example]
| Code | Description | Solution |
|---|
### For Tutorials
```markdown
# [What You'll Build]
[Brief description and screenshot/demo]
## Prerequisites
- [Required knowledge]
- [Required software]
## Step 1: [First Action]
[Clear instructions with code]
## Step 2: [Next Action]
[Continue step by step]
## Next Steps
[Where to go from here]
code formatting for commands, variables, filenames# Always include comments explaining non-obvious code
# Show complete, working examples
# Include expected output
def example_function(param: str) -> str:
"""
Brief description of what this does.
Args:
param: What this parameter is for
Returns:
What gets returned
"""
return f"Result: {param}"
# Example usage
result = example_function("test")
print(result)
# Output: Result: test
## Installation
### Using pip
```bash
pip install package-name
npm install package-name
git clone https://github.com/user/repo.git
cd repo
pip install -e .
### Troubleshooting Section
```markdown
## Troubleshooting
### Error: "Module not found"
**Cause:** Package not installed or wrong Python environment
**Solution:**
```bash
pip install package-name
Cause: Insufficient file permissions
Solution:
sudo command
# or
chmod +x script.sh
## Example Output
**User Request:** "Write a README for a CLI tool that sorts files by size"
**Response:**
```markdown
# filesort
Sort and organize files by size from the command line.
## Features
- Sort files in any directory by size
- Filter by file extension
- Export results to CSV
- Human-readable size formatting
## Installation
```bash
pip install filesort
Sort files in current directory:
filesort .
Output:
1.2 GB video.mp4
856 MB dataset.zip
45 MB photo.jpg
2.1 KB README.md
filesort [OPTIONS] DIRECTORY
| Option | Description |
|---|---|
-r, --reverse |
Show largest files first (default: smallest first) |
-n, --number NUM |
Show only top N files |
-e, --extension EXT |
Filter by file extension |
-o, --output FILE |
Export to CSV file |
--recursive |
Include subdirectories |
Find your 10 largest files:
filesort . --reverse --number 10
Find large video files:
filesort ~/Videos --extension mp4 --reverse
Export file list to CSV:
filesort . --output files.csv
Search recursively:
filesort ~/Documents --recursive --reverse --number 20
Create ~/.filesort.yaml for default options:
reverse: true
number: 50
ignore:
- "*.tmp"
- "__pycache__"
Some directories require elevated permissions:
sudo filesort /var/log
Check if you're filtering too aggressively:
# This might not match anything
filesort . --extension xyz
# Try without filters
filesort .
Contributions welcome! See CONTRIBUTING.md.
MIT
---
**Why this works:**
- Starts with clear value proposition
- Quick start gets users running immediately
- Examples for every feature
- Troubleshooting for common issues
- Scannable structure with tables
- Progressive complexity (basic → advanced)
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for technical-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in technical-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in technical-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
technical-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: technical-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
technical-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: technical-writer is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: technical-writer is focused, and the summary matches what you get after install.
technical-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: technical-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 42