Menú
Request a new skill from the CEO - describe what it should do, and the request is emailed to the admin. EXPLICIT INVOCATION ONLY - sends external email.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Backup the entire workspace to GitHub. EXPLICIT INVOCATION ONLY - never auto-trigger from natural language.
CEO-only: Push all workspace updates to all executives. Single command that commits, classifies, publishes to corporate repo, bumps BUILD.json, pushes CRM, aggregates CRM, syncs exec workspaces, and reports. EXPLICIT INVOCATION ONLY - never auto-trigger.
Manually trigger workspace sync - git pull of the code/data clones, then a push-all backup. EXPLICIT INVOCATION ONLY - never auto-trigger.
Pre-implementation gate: recommended structured checkpoint between plan approval and /implement. Use before any non-trivial implementation: combines success-criteria definition, an inline contrarian stress-test (the /devil discipline), an optional /council architecture review with Kimi as devil's advocate, harness gap audit, and test-contract writing. Produces a GO/NO-GO artifact with a ready-to-paste /implement prompt. Skip for trivial one-liner fixes, typo corrections, and config-only changes.
Ultrathink principal-engineer review gate. Runs a Validate-Identify-Improve-Adjust (VIIA) pass over a target - a plan awaiting approval, just-executed work, a specific file or directory, or the entire workspace - then runs an adversarial refutation layer (Phase 2.5) with cross-family judge rotation (Claude and Kimi k3) and optional two-agent debate on BLOCKER + HIGH findings before presenting findings with concrete proposed fixes for batched approval. Blocks forward progress until approved. Triggers on "scrutinize", "stress-test this", "principal review", "validate and improve", "review the plan before I approve", "audit what you just did", "ultrathink review". Do NOT trigger for artifact grading alone (use /evaluate), fact-checking drafts (use /validate), or strategic reasoning (use /deep-think). Usage: /scrutinize [plan | execution | file:<path> | dir:<path> | workspace | trajectory:<run_id>] [--relentless] [--no-refute] [--include-low-confidence] [--include-ambiguous]
Second-opinion advisor. Default roster is Kimi k3 alongside Claude's own view; Gemini and Grok are opt-in via --gemini / --grok / --all. Two modes: independent (the models see the problem only, reason fresh) and critique (they stress-test a draft). Distinct from /deep-think (Claude reasoning structured, alone) and /odin (Claude + the curated knowledge brain). Trigger when the user says: "council", "/council", "second opinion on", "consult the council", "what would Gemini/Grok/Kimi say about", "stress-test this with Gemini/Grok/Kimi", "council vote".
Basado en la clasificación ocupacional SOC
| name | request-skill |
| x-heading-requires | ["email"] |
| disable-model-invocation | true |
| description | Request a new skill from the CEO - describe what it should do, and the request is emailed to the admin. EXPLICIT INVOCATION ONLY - sends external email. |
| metadata | {"author":"Misha Hanin","email":"misha.hanin@odinix.com","version":"1.1"} |
| argument-hint | [description of the skill you need] |
| allowed-tools | Read, Bash(python3:*) |
| model | haiku |
| x-heading-orchestration | {"parallel_safe":false,"shared_state":[],"triggers":["request skill","I need a new skill"]} |
| x-heading-capability | {"what":"Lets an executive request a new skill from the CEO - captures what it should do, a use case, and expected output, then emails the request to the admin.\n","how":"Explicit invocation only - run /request-skill <description>. Sends external email via scripts/send-email.py to ceo@31c.io. If an existing skill already covers it, points you there instead of sending.\n","when":"Use when you need a capability the workspace does not have yet. Building or editing skills directly is the CEO-only /skill-creator.\n"} |
| x-heading-routing | {"category":"Operations","triggers":["NEVER auto-trigger. Explicit `/request-skill` only."],"exclusions":["Create directly -> /skill-creator (CEO only)"],"compound":"No","router":"manual"} |
Submit a request for a new skill to be created by the CEO/admin. The request is sent via email to the admin with your description, use case, and workspace context.
$ARGUMENTS -- Description of the skill neededIf $ARGUMENTS is empty or too vague, ask:
Read .workspace-identity.json to get the requester's name and role.
Read personal/context/personal-info.md to get the requester's title and email.
Compose the request email:
Subject: HEADING OS Skill Request from {exec_name} ({exec_title})
Body (HTML):
<h2>New Skill Request</h2>
<p><strong>From:</strong> {exec_name} ({exec_title})</p>
<p><strong>Date:</strong> {today}</p>
<p><strong>Workspace:</strong> {exec_slug}</p>
<h3>Skill Description</h3>
<p>{description from $ARGUMENTS}</p>
<h3>Use Case</h3>
<p>{example scenario}</p>
<h3>Expected Output</h3>
<p>{expected output/action}</p>
<h3>Priority</h3>
<p>{requester's assessment: nice-to-have / would-help-daily / urgent-need}</p>
Show the drafted request to the user and confirm before sending. Then send via: python3 scripts/send-email.py --to "ceo@31c.io" --subject "HEADING OS Skill Request from {name}" --body "{html_body}" (recipient is hardcoded to the CEO; content is the user's own request).
Confirm to the user: "Your skill request has been sent to the CEO. You'll hear back when it's ready -- new skills are published via corporate sync."