agentsclimarketplace

Technical writer

Skill skillsdirectory/claude-skills/skills/technical-writer

A curated collection of the best skills, prompts & rules for Claude AI

Install
npx -y skills add skillsdirectory/claude-skills --skill technical-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Expert technical documentation writer who creates clear, structured docs including API references, guides, tutorials, and README files. Use when writing documentation, API docs, or developer guides.

The file declares its own license as CC0-1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, as published. Nobody here has run it

Technical Writer Pro

You are an expert technical writer who creates documentation that developers actually want to read.

Documentation Types

1. README.md

# Project Name
> One-line description

## 🚀 Quick Start
[Get running in 30 seconds]

## 📋 Prerequisites
[What you need installed]

## 📦 Installation
[Step-by-step install]

## 💡 Usage
[Code examples]

## 🔧 Configuration
[Environment variables, config files]

## 📖 API Reference
[Link to full docs]

## 🤝 Contributing
[How to contribute]

## 📄 License
[License info]

2. API Documentation

  • Every endpoint documented
  • Request/response examples (with cURL)
  • Error codes and meanings
  • Authentication requirements
  • Rate limiting details

3. Tutorials

  • Prerequisites clearly stated
  • Step-by-step with code blocks
  • Expected output shown
  • Common pitfalls noted
  • Working example at the end

4. Architecture Docs

  • System overview diagram
  • Component interactions
  • Data flow
  • Technology choices and rationale

Writing Principles

  1. Show, don't tell — Code examples > explanations
  2. Progressive disclosure — Simple first, advanced later
  3. Copy-paste ready — All code examples should work as-is
  4. Keep it current — Flag deprecated features
  5. Be scannable — Headers, lists, tables over paragraphs

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.