**Markers** ▲ top/answer · ● first-level group · ○ supporting detail · ⚠ violation · ↑ buried conclusion · ⇄ wrong order type here · ⊗ overlap · ⊕ gap · ✂ cut/move to appendix **Annotated opening** ⚠ This memorandum describes how project teams identify and deliver significant profit improvements. [topic label, not answer] ⚠ It is organized in six sections: [table of contents; more than four top-level items; order not explained] ⚠ Background [context label, not a claim] ⚠ Principles of the pro...
Scanned 9/19/2026
Install to Claude Code
npx -y skills add welltraum/minto --skill raw --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Raw?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/welltraum-raw-f9a9a0e6)More formats (shields.io, HTML) on the badges page.
**Markers**
▲ top/answer · ● first-level group · ○ supporting detail · ⚠ violation · ↑ buried conclusion · ⇄ wrong order type here · ⊗ overlap · ⊕ gap · ✂ cut/move to appendix
**Annotated opening**
⚠ This memorandum describes how project teams identify and deliver significant
profit improvements. [topic label, not answer]
⚠ It is organized in six sections: [table of contents; more than four top-level items; order not explained]
⚠ Background [context label, not a claim]
⚠ Principles of the project-team approach [idea label, not a claim]
⚠ Definition of project work [scope label, not a claim]
⚠ Organization of the program [process label, not a claim]
⚠ Distinctive benefits and results [payoff label, not a claim]
⚠ Conditions required for success [requirement label, not a claim]
**Findings**
| Location | Violation | Fix |
|---|---|---|
| First sentence | Statement of purpose / topic label; no answer to the reader’s question | Make the first line a one-sentence answer, not a description of the memo |
| Opening | No SCQ: no accepted Situation, Complication, or literal Question is visible | Add a short Situation → Complication → Question lead that makes the answer necessary |
| “It is organized in six sections” | Table-of-contents display; no key line or controlling idea above the headings | Put the answer/key line before any section list |
| Six headings | Headings are topic labels, not claims that summarize their sections | Retain only headings that can be read as claims supporting the top |
| Six headings | Mixed kinds: background, principles, definition, organization, benefits, conditions | Regroup into one kind matched to the reader’s question |
| Six headings | More than four first-level groups | Reduce to ≤4 top-level groups or demote items under parent claims |
| Heading order/setout | Order is not explicable from the visible opening, and the six-way split does not show a MECE field | Choose an order type and define the field so retained headings are non-overlapping and complete |
**Score**
| Axis | Score |
|---|---:|
| Top | 0 |
| Same-kind groups | 0 |
| Order | 1 |
| MECE | 1 |
| Display | 1 |
Total: 3/10 — not structured yet.
**Three highest-value fixes**
1. Replace the opening topic label with a one-sentence answer to the reader’s question.
2. Cut the six-section list to no more than four same-kind groups under that answer.
3. Add a two-line SCQ lead so the reader sees the complication that makes the answer matter.
Next: I can run write.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!