amazon-writing

Use when writing narrative memos, 6-pagers, 1-pagers, press releases, or PRFAQs in Amazon style. Applies Amazon's no-PowerPoint writing standards with data over adjectives, active voice, and the "so what" test.

16 stars

Best use case

amazon-writing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when writing narrative memos, 6-pagers, 1-pagers, press releases, or PRFAQs in Amazon style. Applies Amazon's no-PowerPoint writing standards with data over adjectives, active voice, and the "so what" test.

Teams using amazon-writing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amazon-writing/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/communication/amazon-writing/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amazon-writing/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amazon-writing Compares

Feature / Agentamazon-writingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when writing narrative memos, 6-pagers, 1-pagers, press releases, or PRFAQs in Amazon style. Applies Amazon's no-PowerPoint writing standards with data over adjectives, active voice, and the "so what" test.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Amazon Writing Standards

Amazon has a distinctive "no PowerPoint" culture that emphasizes narrative memos and clear, data-driven communication. This skill provides guidelines for rewriting content following Amazon's internal writing standards.

## Core Writing Rules

Apply these six principles to all Amazon-style documents:

### 1. Narrative Structure

Write in complete narrative form with logical flow from beginning to middle to end. No bullet points or slide-style formatting. The document tells a complete story where all information connects logically. Each paragraph builds on the previous one, leading to a coherent and persuasive argument.

### 2. Conciseness and Clarity

Use simple, straightforward language. Avoid jargon and acronyms unless spelled out on first use. Keep sentences under 30 words when possible. If specialized terms are necessary, provide brief explanations. The reader should understand the topic without needing supporting documents.

### 3. Data Over Adjectives

Replace vague qualifiers with specific, quantifiable data and metrics:

| Avoid | Use Instead |
|-------|-------------|
| "significantly increased" | "increased 47%" |
| "many customers" | "1,247 customers" or "73% of customers" |
| "very fast" | "completes in 2.3 seconds" |
| "substantial savings" | "$2.4M annual savings" |
| "recently" | "on March 15, 2024" |

Every claim requires evidence, not assumptions.

### 4. Active Voice

Write in active voice for clearer, more concise, and more confident text:

| Passive (Avoid) | Active (Use) |
|-----------------|--------------|
| "The feature was developed by the team" | "The team developed the feature" |
| "Customers were surveyed" | "We surveyed customers" |
| "The decision was made" | "Leadership decided" |

### 5. The "So What" Test

Every sentence must add value and have a clear purpose. The reader should immediately understand why each piece of information matters. If a sentence doesn't pass the "so what" test, remove it or rewrite it to show relevance.

### 6. Respect the Reader's Time

Present the most important information clearly and early. Eliminate "clutter" words that don't add meaning. Executives should immediately understand why they should care within the first page.

## Document Types

Amazon uses four primary document formats. Load the appropriate reference file based on document type:

| Document Type | When to Use | Reference File |
|---------------|-------------|----------------|
| Press Release | New product/feature announcements | `references/press-release.md` |
| 6-Pager | Complex strategic topics, detailed analysis | `references/six-pager.md` |
| 1-Pager | Straightforward topics, quick decisions | `references/one-pager.md` |
| PRFAQ | Product innovation, working backwards | `references/prfaq.md` |

## Rewriting Process

When rewriting content to Amazon style:

### Step 1: Analyze Content

Use a scratchpad to analyze before rewriting:

1. Identify the main message or purpose
2. Note vague adjectives/adverbs that need specific data
3. Find passive voice constructions to convert
4. Flag jargon or acronyms needing clarification
5. Determine the logical narrative flow
6. For specific document types: identify required sections present or missing

### Step 2: Load Document Guidelines

Read the appropriate reference file for the target document type to understand required sections and format.

### Step 3: Rewrite

Transform the content following:

- Core writing rules (narrative, data-driven, active voice)
- Document-specific structure and sections
- Length constraints for the document type

### Step 4: Verify

Check the rewritten content against:

- All six core writing rules applied
- Required sections present for document type
- No bullet points (narrative prose only)
- Specific metrics replace vague qualifiers
- Active voice throughout
- Appropriate length for document type

## Quality Standards

A well-written Amazon document demonstrates:

- **Mastery**: Deep understanding of every aspect of the topic
- **Realism**: Optimistic but honest assessment, not rose-colored
- **Data-based**: Firm grasp of metrics and evidence
- **Risk awareness**: Clear understanding of challenges and conditions for success/failure

The great memos are written and re-written, shared with colleagues for improvement, set aside for a couple of days, and then edited again with a fresh mind.

## Reference Files

For detailed document-specific guidelines:

- **`references/press-release.md`** - Press release format and sections
- **`references/six-pager.md`** - 6-pager memo structure
- **`references/one-pager.md`** - 1-pager memo format
- **`references/prfaq.md`** - PRFAQ structure with FAQ guidelines

Related Skills

blog-writing

16
from diegosouzapw/awesome-omni-skill

Write compelling blog posts with proven structure — hook openings, scannable body sections, clear CTAs. Use this skill when drafting blog posts, articles, or content marketing pieces.

writing-skills

16
from diegosouzapw/awesome-omni-skill

Use when creating, updating, or improving agent skills.

writing-project-technical-writing

16
from diegosouzapw/awesome-omni-skill

Writes technical prose (READMEs, ADRs, code comments) in the project's established human voice. Use when creating or editing .md files, writing Swift doc comments, authoring ADRs, or reviewing technical writing for voice consistency.

u09613-writing-and-rhetoric-optimization-for-household-logistics

16
from diegosouzapw/awesome-omni-skill

Operate the "Writing And Rhetoric Optimization for household logistics" capability in production for household logistics workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

postmortem-writing

16
from diegosouzapw/awesome-omni-skill

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...

essay-writing

16
from diegosouzapw/awesome-omni-skill

Writing support (drafting, evaluation and revision) for executives and tech leaders. Support everything from internal culture-building to external technical branding.

copywriting

16
from diegosouzapw/awesome-omni-skill

Write persuasive copy for landing pages, emails, ads, sales pages, and marketing materials. Use when you need to write headlines, CTAs, product descriptions, ad copy, email sequences, or any text meant to drive action. Covers copywriting formulas (AIDA, PAS, FAB), headline writing, emotional triggers, objection handling in copy, and A/B testing. Trigger on "write copy", "copywriting", "landing page copy", "headline", "write a sales page", "ad copy", "email copy", "persuasive writing", "how to write [marketing text]".

Article Writing

16
from diegosouzapw/awesome-omni-skill

Structure and style guidance for law review articles

algebraic-rewriting

16
from diegosouzapw/awesome-omni-skill

Category-theoretic graph rewriting with DPO, SPO, and SqPO pushouts for C-Sets. Declarative transformation of acset data structures.

ai-writing-detection

16
from diegosouzapw/awesome-omni-skill

Comprehensive AI writing detection patterns and methodology. Provides vocabulary lists, structural patterns, model-specific fingerprints, and false positive prevention guidance. Use when analyzing text for AI authorship or understanding detection patterns.

ai-doc-writing

16
from diegosouzapw/awesome-omni-skill

This skill should be used when writing, reviewing, or refactoring documentation that will be consumed as AI context. Optimizes documentation for LLM comprehension using principles of completeness, efficiency, and zero fluff—replacing prose with structured data, enforcing heading hierarchy, detecting meta-commentary, and validating that examples serve a purpose.

adr-writing

16
from diegosouzapw/awesome-omni-skill

Write Architectural Decision Records following MADR template. Applies Definition of Done criteria, marks gaps for later completion. Use when generating ADR documents from extracted decisions.