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.
What this skill does
# 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 in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.