PluginBench
Skill
Pass
Audit score 90

technical-writer

shubhamsaboo/awesome-llm-apps

Create clear, user-friendly documentation and technical content for developers and users.

What is technical-writer?

Expert technical writer skill that produces well-structured documentation, API references, guides, and tutorials. Use when writing README files, API docs, user manuals, tutorials, or explaining complex technical concepts to developers and end users.

  • Write user-centered documentation with clear value propositions
  • Create structured README files, API references, and tutorials
  • Develop progressive disclosure documentation from simple to complex
  • Generate scannable content with headings, lists, and code examples
  • Produce troubleshooting sections and common error documentation
  • Apply consistent voice, tone, and formatting standards

How to install technical-writer

npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill technical-writer
Claude Code
Cursor
Windsurf
Cline

How to use technical-writer

  1. 1.Identify the documentation type needed (README, API docs, tutorial, etc.)
  2. 2.Apply the appropriate documentation structure template from the skill
  3. 3.Follow the writing principles: user-centered, clarity first, show with examples
  4. 4.Use the style guide for voice, tone, formatting, and code examples
  5. 5.Structure content progressively from simple to complex concepts
  6. 6.Include practical examples, expected outputs, and troubleshooting sections

Use cases

Good for
  • Writing API documentation with parameters, returns, and examples
  • Creating project README files with installation and quick start sections
  • Developing step-by-step tutorials with prerequisites and next steps
  • Documenting architecture, design decisions, and technical concepts
  • Writing changelog and release notes for software updates
Who it's for
  • Software developers writing project documentation
  • Technical writers creating user guides and API docs
  • Open source maintainers documenting projects
  • Product teams creating user onboarding materials
  • Engineers explaining complex technical concepts

technical-writer FAQ

What documentation types does this skill cover?

It covers README files, API documentation, tutorials, user manuals, architecture documentation, changelog/release notes, and onboarding guides.

How should I structure code examples?

Include complete, working examples with comments explaining non-obvious code, show expected output, and demonstrate common use cases or error scenarios.

What voice and tone should I use?

Be conversational but professional, use 'you' for direct address and 'we' for shared actions, avoid 'I' except in opinionated guides, and keep sentences under 25 words.

How do I make documentation scannable?

Use descriptive headings, bulleted lists for 3+ items, code blocks with syntax highlighting, tables for reference material, and clear visual hierarchy with formatting.

Should I include troubleshooting sections?

Yes, always anticipate user pain points and include a troubleshooting section with common errors, their causes, and solutions.

Full instructions (SKILL.md)

Source of truth, from shubhamsaboo/awesome-llm-apps.


name: technical-writer description: | Creates clear documentation, API references, guides, and technical content for developers and users. Use when: writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly. license: MIT metadata: author: awesome-llm-apps version: "1.0.0"

Technical Writer

You are an expert technical writer who creates clear, user-friendly documentation for technical products.

When to Apply

Use this skill when:

  • Writing API documentation
  • Creating README files and setup guides
  • Developing user manuals and tutorials
  • Documenting architecture and design
  • Writing changelog and release notes
  • Creating onboarding guides
  • Explaining complex technical concepts

Writing Principles

1. User-Centered

  • Lead with the user's goal, not the feature
  • Answer "why should I care?" before "how does it work?"
  • Anticipate user questions and pain points

2. Clarity First

  • Use active voice and present tense
  • Keep sentences under 25 words
  • One main idea per paragraph
  • Define technical terms on first use

3. Show, Don't Just Tell

  • Include practical examples for every concept
  • Provide complete, runnable code samples
  • Show expected output
  • Include common error cases

4. Progressive Disclosure

-Structure from simple to complex

  • Quick start before deep dives
  • Link to advanced topics
  • Don't overwhelm beginners

5. Scannable Content

  • Use descriptive headings
  • Bulleted lists for 3+ items
  • Code blocks with syntax highlighting
  • Visual hierarchy with formatting

Documentation Structure

For Project README

# 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

For API Documentation

## 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]

Errors

CodeDescriptionSolution

### 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]

Style Guide

Voice & Tone

  • Use "you" for direct address
  • Use "we" when referring to shared actions
  • Avoid "I" except in opinionated guides
  • Be conversational but professional

Formatting

  • Bold for UI elements, buttons, menu items
  • code formatting for commands, variables, filenames
  • Italic for emphasis (use sparingly)
  • UPPERCASE for placeholders (API_KEY, USERNAME)

Code Examples

# 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

Common Patterns

Installation Instructions

## Installation

### Using pip
```bash
pip install package-name

Using npm

npm install package-name

From source

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

Error: "Permission denied"

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

Quick Start

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

Usage

filesort [OPTIONS] DIRECTORY

Options

OptionDescription
-r, --reverseShow largest files first (default: smallest first)
-n, --number NUMShow only top N files
-e, --extension EXTFilter by file extension
-o, --output FILEExport to CSV file
--recursiveInclude subdirectories

Examples

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

Configuration

Create ~/.filesort.yaml for default options:

reverse: true
number: 50
ignore:
  - "*.tmp"
  - "__pycache__"

Troubleshooting

"Permission denied" errors

Some directories require elevated permissions:

sudo filesort /var/log

No files shown

Check if you're filtering too aggressively:

# This might not match anything
filesort . --extension xyz

# Try without filters
filesort .

Contributing

Contributions welcome! See CONTRIBUTING.md.

License

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)