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, missing answer, etc.) | | `↑` | conclusion buried lower than it belongs | | `⇄` | wrong order type here | | `⊗` | overlap (ME broken) | | `⊕` | gap (CE broken) | | `✂` | cut, or move to an appendix | --- ``` ⚠▲ Subject: Period Graph Books ⚠● Production ○ 1. Gather data from divisional forms, internal docum...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 19, 2026
ai-agentsgodatabase

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-3463bcf4/badge)](https://www.skillsdirectory.com/skills/welltraum-raw-3463bcf4)

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, missing answer, etc.) |
| `↑` | conclusion buried lower than it belongs |
| `⇄` | wrong order type here |
| `⊗` | overlap (ME broken) |
| `⊕` | gap (CE broken) |
| `✂` | cut, or move to an appendix |

---

### Annotated memo

```
⚠▲ Subject: Period Graph Books

⚠● Production
○ 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
○ 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.
○ 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
○ 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 table  

| Location | Violation | Suggested fix |
|---|---|---|
| `Subject: Period Graph Books` | **Top missing answer** – topic label, not a controlling idea that answers a reader question. | Replace with a one‑sentence answer to the reader’s question (e.g., “We recommend consolidating the graph‑book production process to eliminate duplication and errors.”). |
| Entire memo (first paragraph) | **SCQ intro absent / question placed at end** – no explicit Situation → Complication → Question early on. | Insert a concise SCQ intro that states the shared Situation, the Complication (process fragmentation), the Question (what should we do?), and the Answer. |
| `Issues` paragraph | **Mixed‑kind list & MECE breach** – combines data‑duplication, calculation errors, and process fragmentation without clear same‑kind grouping; overlaps between points. | Split into separate same‑kind groups (e.g., “Data duplication”, “Calculation inaccuracies”, “Process fragmentation”) and ensure each group is mutually exclusive and collectively exhaustive. |
| `Overall assessment` | **Buried recommendation** – recommendation implied but not explicit; conclusion hidden below. | Add a clear, stand‑alone recommendation before the closing question. |
| `Issues` paragraph | **No explicit ordering** – items listed arbitrarily, no rationale for order. | Order the issue groups by impact or frequency and state the ordering principle. |
| Headings (`Production`, `Issues`, `Overall assessment`) | **Structure not visible** – lack of hierarchical numbering or visual cues. | Use numbered headings (e.g., 1. Production, 2. Issues, 3. Assessment) or indentation to make the hierarchy obvious at a glance. |
| `Could we discuss how best to proceed?` | **Answer missing** – question asks for next steps but no answer is provided. | Provide the answer (e.g., “We should form a cross‑functional task force to redesign the workflow within two weeks.”). |

*(Only the most critical seven findings are shown; 2 additional minor overlaps were omitted.)*

---

### Score (0 – 2 per axis)

| Axis | Score | Comment |
|---|---|---|
| Top | **0** | No controlling answer present. |
| Same‑kind groups | **1** | Some groups mix different kinds; partial compliance. |
| Order | **1** | Order is present but not justified. |
| MECE | **1** | Overlaps and gaps exist in the issue list. |
| Display | **1** | Basic headings exist but hierarchy is not clearly visible. |

**Total: 4 / 10** – baseline workable level.

---

### Three highest‑impact fixes  

1. **Insert a one‑sentence answer at the top** that directly answers the reader’s question.  
2. **Add a full SCQ intro** (Situation → Complication → Question → Answer) early in the memo.  
3. **Re‑organize the “Issues” section into distinct, same‑kind, MECE groups** and state an explicit ordering principle.

Files in this skill

  • 01-big-chief__codex__control.md1.1 KB
  • 01-big-chief__codex__skill.md1.7 KB
  • 01-big-chief__gpt-oss-120b__control.md1.5 KB
  • 01-big-chief__gpt-oss-120b__skill.md1.9 KB
  • 01-big-chief__haiku45__control.md1 KB
  • 01-big-chief__haiku45__skill.md1.3 KB
  • 01-big-chief__opus5__control.md1.2 KB
  • 01-big-chief__opus5__skill.md2.6 KB
  • 01-big-chief__qwen3.6-35b-a3b__control.md1.1 KB
  • 01-big-chief__qwen3.6-35b-a3b__skill.md1.4 KB
  • 01-big-chief__qwen3.6-fp8__control.md1.2 KB
  • 01-big-chief__qwen3.6-fp8__skill.md2.2 KB
  • 01-big-chief__qwen3.8-27b__control.md1.2 KB
  • 01-big-chief__qwen3.8-27b__skill.md1.4 KB
  • 01-big-chief__sonnet5__control.md1.2 KB
  • 01-big-chief__sonnet5__skill.md1.2 KB
  • 02-ttv__codex__control.md1.5 KB
  • 02-ttv__codex__skill.md2.3 KB
  • 02-ttv__gpt-oss-120b__control.md2.9 KB
  • 02-ttv__gpt-oss-120b__skill.md2.7 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…