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

Since October, divisional managers have held full authority for day-to-day operations; policy and planning remain ours. In practice we still spend our time on short-term operational problems, and the arrangements we inherited — our size, our membership, our split of work with the Executive Committee — were built for the Board we used to be. So the question is not what topics deserve discussion. It is what we change so that the Board does the work the reorganization left to it. **We should reb...

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

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

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

Download with Pro
Files
01-big-chief__codex__control.md
# The Board's role after the October reorganization

Since October, divisional managers have held full authority for day-to-day operations; policy and planning remain ours. In practice we still spend our time on short-term operational problems, and the arrangements we inherited — our size, our membership, our split of work with the Executive Committee — were built for the Board we used to be.

So the question is not what topics deserve discussion. It is what we change so that the Board does the work the reorganization left to it.

**We should rebuild the Board around policy and planning: draw a hard line between our work and the Executive Committee's, staff the Board to do that work, and set out how we get there from today's arrangement.**

## 1. Give the operational agenda away and keep policy and planning

- Define what the Board decides and what the Executive Committee decides, so that the same matter does not reach both.
- Refuse the short-term operational items that divisional managers now own outright.
- State the responsibilities of each body and how the two relate day to day.

## 2. Staff the Board for the work that remains

- Set the size that suits a policy and planning body rather than an operating one.
- Fix the composition that goes with it, inside and outside members.
- Adopt principles for selecting directors and for their tenure, so composition holds over time rather than drifting with each appointment.
- Make outside members effective participants — their contribution is what policy work most needs and what an operational agenda most easily wastes.

## 3. Set out the move from the present arrangement to the intended one

- Compare the alternative routes from today's Board and Executive Committee arrangement to the one we choose.
- Say what changes first, so the operational agenda leaves the Board before the membership changes rather than after.

*[data needed: the current split of Board agenda time between operational and policy items, to show the size of the gap we are closing.]*

**What I need from the Board:** agreement that these three are the questions before us, and that we settle 1 before 2.

```mermaid
flowchart TD
    A["Rebuild the Board around policy and planning"] --> B1["1. Give away the operational agenda, keep policy and planning"]
    A --> B2["2. Staff the Board for the work that remains"]
    A --> B3["3. Set out the move from today's arrangement"]
    B1 --> C11["Split Board / Executive Committee decisions"]
    B1 --> C12["Operations sit with divisional managers since October"]
    B2 --> C21["Size and composition for a policy body"]
    B2 --> C22["Selection and tenure principles"]
    B2 --> C23["Outside members made effective participants"]
    B3 --> C31["Compare alternative routes"]
    B3 --> C32["Sequence: remit before membership"]
```

**What changed structurally:** the list of discussion topics became an answer with three same-kind actions under it; composition, selection and tenure merged into one branch because they are one decision about staffing, and the transition — buried as item 5 — became a first-level branch. Order is now sequential-by-dependency: remit determines membership, membership determines the route.

Attribution

welltraumwelltraum
View sourceMore from welltraum →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

1066601 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', ...

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

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