Agent skill · Documentation

memo-stress-tester

Use when evaluating business documents for structural integrity and persuasive logic.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill memo-stress-tester --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Requires: Claude Code and compatible agent products
Path: skills/analysis/memo-stress-tester/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Overview Memo stress-testing is the rigorous evaluation of a business document's "readiness" for executive decision-making. It identifies logical gaps, unproven assertions, and "half-baked" ideas. By applying the Amazon narrative standard, Minto's pyramid logic, and the doctrine of Completed Staff Work, it ensures that a document is a self-contained tool for strategic action rather than a draft for the boss to finish. ## Guiding Principles ### Principle 1: Completed Staff Work (Source: Web, Completed Staff Work Doctrine) Study, write, restudy, and rewrite until you have evolved a single proposed action. The "Chief" should only need to approve or disapprove. If the superior has to do more research or thinking, the staff work is incomplete. ### Principle 2: The Self-Contained Narrative (Source: Bryar, Working Backwards) A memo must stand on its own without a supporting presentation. It should be a narrative that forces better thinking and allows for deep, silent reading. If the document relies on "hallway context" or a presenter's explanation, it fails the stress test. ### Principle 3: MECE Validation (Source: Minto, The Pyramid Principle) Every group of supporting points must be

What's inside
Steps it walks through
  1. Overview
  2. Guiding Principles
  3. Principle 1: Completed Staff Work (Source: Web, Completed Staff Work Doctrine)
  4. Principle 2: The Self-Contained Narrative (Source: Bryar, Working Backwards)
  5. Principle 3: MECE Validation (Source: Minto, The Pyramid Principle)
  6. Principle 4: Contribution over Effort (Source: Drucker, The Effective Executive)
  7. Principle 5: The "Answer First" Order (Source: Minto, The Pyramid Principle)
  8. When to Use This Skill
  9. When NOT to Use This Skill
  10. Core Process
  11. Step 1: The "Completed Staff Work" Audit (Source: Web)
  12. Step 2: The SCQ Logic Check (Source: Minto, The Pyramid Principle)
  13. Step 3: The MECE Stress Test (Source: Minto, The Pyramid Principle)
  14. Step 4: The Amazon "Narrative" Pass (Source: Bryar, Working Backwards)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the memo-stress-tester skill do?

Use when evaluating business documents for structural integrity and persuasive logic.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill memo-stress-tester --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going