Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Raw

ASecurity

**Audit diagnosis: Period Graph Books memo** --- **Legend** | Marker | Meaning | |---|---| | ▲ | top / answer | | ● | first-level group | | ⚠ | violation (mixed kinds, unexplainable order, false grouping) | | ↑ | conclusion buried lower than it belongs — promote it | | ⊕ | gap (missing category or scope ambiguity) | --- **Annotated text** ▲ Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo de...

2 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgodatabase

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$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 automatically with every re-scan.

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

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
01-big-chief__codex__control.md
**Audit diagnosis: Period Graph Books memo**

---

**Legend**

| Marker | Meaning |
|---|---|
| ▲ | top / answer |
| ● | first-level group |
| ⚠ | violation (mixed kinds, unexplainable order, false grouping) |
| ↑ | conclusion buried lower than it belongs — promote it |
| ⊕ | gap (missing category or scope ambiguity) |

---

**Annotated text**

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

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 [⊕ scope unclear], 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**

| Location | Violation | Fix |
|---|---|---|
| Opening line (▲) | Topic label, not answer; actual answer buried at end and vague | Move the diagnosis ("fragmented process with unclear ownership") to the top in one sentence |
| Production section (●) | Process mechanics (how it works) answering a different question than reader asked (what's wrong); this is observation, not reason | Cut or subordinate to 1–2 sentences as support; reader asked for diagnosis, not procedure |
| Vertical link: Issues → Assessment (↑) | Assessment jumps to conclusion ("no one controls data," "responsibility unclear") with no causal bridge from the specific problems listed above | Insert intermediate conclusion explaining why those symptoms occurred; connect inconsistent data → lack of ownership, not just state both |
| Issues section (⊕) | Scope ambiguous — says "For one book" but unclear whether problems are book-specific or systematic across all four | Clarify: are these symptoms common to all books or unique to this one |
| Same-kind groups (⚠) | Three sections are three different kinds: Production (mechanics) + Issues (symptoms) + Assessment (diagnosis); reader asking "what's wrong?" does not receive grouped reasons | Rebuild around root causes or recommendations, not process steps + problems + conclusion |
| Closing line | Abdicates with a question instead of proposing action | State what you recommend or what decision you need |

---

**Score: 1 / 10** — not structured yet

- Top: 0 (topic label, no answer)
- Same-kind: 0 (three unrelated categories)
- Order: 0 (process–symptoms–diagnosis sequence is unexplainable)
- MECE: 1 (problems listed but scope and causes unclear)
- Display: 1 (headings visible, logic flow is not)

---

**Three fixes that buy the most**

1. **Lead with diagnosis, not process.** Move "fragmented process, no one controls data end-to-end, responsibility unclear" to the opening as a one-sentence answer.
2. **Remove or bury the Production section.** Mechanics answer a different question. Keep 1–2 lines as context if needed; cut the four-step list.
3. **Add intermediate conclusions.** Show why the listed problems happen (e.g., "inconsistent data between periods because multiple re-entries → no single source of truth"). Connect symptoms to root cause before the summary.

Attribution

welltraumwelltraum
View sourceMore from welltraum →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →