Skip to content
Back to skills

Raw

ASecurity

**Legend** | 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 | *** Subject: Period Graph Books ⚠ [Topic label; no answer to reader's question about corrective proposals] Since Per...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 19, 2026
businessgodatabase

Security analysis

A100/100

Pro scans all 21 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add welltraum/minto --skill raw --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Raw?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Raw
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/welltraum-raw-ff0d38da/badge)](https://www.skillsdirectory.com/skills/welltraum-raw-ff0d38da)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
**Legend**

| 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 |

***

Subject: Period Graph Books

⚠ [Topic label; no answer to reader's question about corrective proposals] Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer.

Production

● [Process steps; descriptive, not analytical] 1. Gather data from divisional forms, internal documents, and telephone calls.
2. Calculate graph points manually or on the corporate computer, including rolling values for revenue, cost, and percentages.
3. Transcribe the points to input sheets. Analysts update the current period, then Color Graphics re-enters the points into its own database and generates the graphs.
4. Check the data and calculations.

Issues

⚠ [Mixed kinds: systemic observation, specific example, list of errors] The transfer inserted another person into an already fragmented process. Divisional staff and three corporate departments participate, and the same information may be entered into computer systems three times.

⊕ [Gap: Systemic cause "no one controls data" introduced later without support here] For one book, divisional data are loaded into a dedicated corporate program, calculated, transferred to Color Graphics input sheets, entered again, and returned for updates. Problems include inconsistent data between periods and regions, incorrect variable-cost calculations, unexplained changes to points that were previously correct, and prior-period data that must be re-entered.

Overall assessment

↑ [Recommendation buried below description] Most problems arise from a cumbersome fragmented process. No one controls the data from beginning to end, responsibility is unclear, and errors can fall between stages. The production process badly needs streamlining, both for each book and for common calculations. The current team cannot manage the required changes as well as ongoing production.

Could we discuss how best to proceed?

***

### Findings

| Location | Violation | Fix |
|---|---|---|
| Opening paragraph | Top is a topic label; does not answer the reader's question for corrective proposals. | Replace with a one-sentence recommendation answering the question. |
| Body structure | Groups are mixed kinds (steps, problems, assessment); order is descriptive recall. | Restructure into 3–4 same-kind groups (reasons or actions) ordered by ranking or deduction. |
| Last paragraph | Recommendation buried; ask is vague ("discuss"). | Promote recommendation to top; close with a specific decision or sign-off request. |
| Issues / Assessment link | Gap: "Responsibility is unclear" stated in assessment but not evidenced in Issues. | Add evidence linking errors to lack of ownership/control. |
| Intro | Missing SCQ story; jumps straight to description. | Draft Situation → Complication → Question → Answer intro dosed to management. |

### Score

| Axis | Score |
|---|---|
| Top | 0 |
| Same-kind groups | 0 |
| Order | 0 |
| MECE | 1 |
| Display | 1 |
| **Total** | **2** |

**Band:** `0–3` not structured yet

### Three fixes that buy the most

1. Rewrite the opening to state the recommendation immediately (e.g., "We recommend streamlining the graph book process to eliminate errors and clarify ownership.").
2. Reorganize content into three groups of reasons or actions supporting the recommendation, moving the descriptive "Production" steps to an appendix.
3. Close with a clear decision request rather than a vague invitation to discuss.

Files in this skill

  • 01-big-chief__codex__control.md1 KB
  • 01-big-chief__codex__skill.md1.1 KB
  • 01-big-chief__gpt-oss-120b__control.md1.7 KB
  • 01-big-chief__gpt-oss-120b__skill.md1.8 KB
  • 01-big-chief__haiku45__control.md1.2 KB
  • 01-big-chief__haiku45__skill.md1 KB
  • 01-big-chief__kimi__control.md1.3 KB
  • 01-big-chief__kimi__skill.md1.8 KB
  • 01-big-chief__opus5__control.md1.2 KB
  • 01-big-chief__opus5__skill.md2.9 KB
  • 01-big-chief__qwen3.6-35b-a3b__control.md1.3 KB
  • 01-big-chief__qwen3.6-35b-a3b__skill.md1.2 KB
  • 01-big-chief__sonnet5__control.md1.2 KB
  • 01-big-chief__sonnet5__skill.md1.3 KB
  • 02-ttv__codex__control.md1.2 KB
  • 02-ttv__codex__skill.md2.2 KB
  • 02-ttv__gpt-oss-120b__control.md4.1 KB
  • 02-ttv__gpt-oss-120b__skill.md2.8 KB
  • 02-ttv__haiku45__control.md1.5 KB
  • 02-ttv__haiku45__skill.md1.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…