technical-writer

shubhamsaboo/awesome-llm-apps · updated Apr 12, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill technical-writer
0 commentsdiscussion
summary

Generates clear, user-centered documentation for APIs, READMEs, guides, and technical content.

  • 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
skill.md

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

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]

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

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

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)
how to use technical-writer

How to use technical-writer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add technical-writer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill technical-writer

The skills CLI fetches technical-writer from GitHub repository shubhamsaboo/awesome-llm-apps and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/technical-writer

Reload or restart Cursor to activate technical-writer. Access the skill through slash commands (e.g., /technical-writer) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.642 reviews
  • Advait Yang· Dec 20, 2024

    Registry listing for technical-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Henry Singh· Dec 12, 2024

    Useful defaults in technical-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ganesh Mohane· Dec 8, 2024

    Useful defaults in technical-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Rahul Santra· Nov 27, 2024

    technical-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Omar Ndlovu· Nov 11, 2024

    Keeps context tight: technical-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ava Smith· Nov 3, 2024

    technical-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anika Sharma· Oct 22, 2024

    Solid pick for teams standardizing on skills: technical-writer is focused, and the summary matches what you get after install.

  • Pratham Ware· Oct 18, 2024

    Solid pick for teams standardizing on skills: technical-writer is focused, and the summary matches what you get after install.

  • Naina Chawla· Oct 2, 2024

    technical-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hiroshi Khan· Sep 25, 2024

    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

1 / 5