| Marker | Meaning | |---|---| | `▲` | top / answer | | `●` | first-level group | | `○` | supporting detail | | `⚠` | violation (mixed kinds, unexplainable order, false grouping) | | `↑` | conclusion buried lower than it belongs — promote it | | `⇄` | wrong order type here | | `⊗` | overlap (ME broken) | | `⊕` | gap (CE broken) | | `✂` | cut, or move to an appendix | ▲ ✂ This memorandum describes how project teams identify and deliver significant profit improvements. ✂ It is organized in six ...
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-a9d793fd)More formats (shields.io, HTML) on the badges page.
| Marker | Meaning |
|---|---|
| `▲` | top / answer |
| `●` | first-level group |
| `○` | supporting detail |
| `⚠` | violation (mixed kinds, unexplainable order, false grouping) |
| `↑` | conclusion buried lower than it belongs — promote it |
| `⇄` | wrong order type here |
| `⊗` | overlap (ME broken) |
| `⊕` | gap (CE broken) |
| `✂` | cut, or move to an appendix |
▲ ✂ This memorandum describes how project teams identify and deliver significant profit improvements. ✂ It is organized in six sections:
⚠ ⇄ Background
⚠ ⇄ Principles of the project-team approach
⚠ ⇄ Definition of project work
⚠ ⇄ Organization of the program
⚠ ⇄ Distinctive benefits and results
⚠ ⇄ Conditions required for success
### Findings
| Location | Violation | Fix |
|---|---|---|
| First sentence | Top is a topic label ("describes how"), not an answer to the reader's question. | Replace with one-sentence answer addressing the reader's decision or action need. |
| Heading list | Six groups exceed the 3–4 limit; elements are mixed kinds (context, principles, definition, org, benefits, conditions). | Reduce to 3–4 groups; derive the common kind from the reader's question and regroup. |
| Heading list | Order is unexplainable; reflects report convention rather than time, structure, ranking, deduction, or induction. | Assign a single ordering principle to the groups. |
| Meta-text | "This memorandum describes..." and "It is organized in..." hide the structure and waste attention. | Cut all meta-text; let the hierarchy speak through headings and key lines. |
| Heading list | High risk of non-MECE split due to breadth and lack of clear decomposition field. | Verify boundaries between groups; merge overlaps; ensure the field is fully covered. |
### Score
| Axis | Score |
|---|---|
| Top | 0 |
| Same-kind groups | 0 |
| Order | 0 |
| MECE | 0 |
| Display | 0 |
| **Total** | **0 / 10** |
Band: `0–3` not structured yet
### Three fixes that buy the most
1. Replace the opening sentence with a precise, one-sentence answer to the reader's question.
2. Collapse the six headings into 3–4 first-level groups of the same kind, ordered by a justified principle.
3. Delete all meta-descriptions of the document structure; present the argument directly.
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!