---
name: Technical Writing
slug: technical-writing
category: Writing
description: Technical Writing guides concise, clear documentation, specs, and markdown files. Use it when creating or editing READMEs, AGENTS.md files, or other codebase docs.
github: "https://github.com/saffron-health/libretto/tree/main/.agents/skills/technical-writing"
language: TypeScript
stars: 877
forks: 67
install: "npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/technical-writing ~/.claude/skills/technical-writing"
installs_to: ~/.claude/skills/technical-writing
source_path: .agents/skills/technical-writing/SKILL.md
collection_size: 23
category_size: 1012
collection_url: "https://dirskills.com/collections/saffron-health/libretto"
added: 2026-08-22T05:21:21.953Z
last_synced: 2026-08-22T05:21:21.953Z
canonical_url: "https://dirskills.com/skills/technical-writing"
---

# Technical Writing

Technical Writing guides concise, clear documentation, specs, and markdown files. Use it when creating or editing READMEs, AGENTS.md files, or other codebase docs.

**Install:**

```bash
npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/technical-writing ~/.claude/skills/technical-writing
```

## README

# Technical Writing

## Audience

Assume readers are at least as smart as you, so do not over-explain. State information once and move on.

## Style

Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.

## Formatting

- Do not use emojis.
- Do not use bold or italics.
- Use headings, lists, and code blocks only when they add clarity.
- Use fenced code blocks with language identifiers.

## Paths

Always use relative file paths: `docs/testing.md`, not `/Users/name/project/docs/testing.md`.

## Do Not Repeat

Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
