scaryrawr/scarydex

codex-plugin-docs

Write or update ScaryDex Codex plugin documentation, install guidance, port-boundary notes, attribution, and source references without claiming unsupported client capabilities.

codex-plugin-maintenance

Port or maintain ScaryDex plugins for Codex, review pinned upstream changes, record dispositions, and validate manifests, hooks, bundles, and the portable capability boundary.

audio

Generate local OMLX speech or transcribe an audio file into a saved transcript. Not for realtime microphone streaming or long-form video-to-document workflows.

blogify

Use this skill to turn a video or audio recording (a talk, meeting, or demo) into written content: documentation, a blog post, tutorial, changelog, or notes. Handles transcription, takeaway synthesis, screenshot/frame selection, and grounded drafting from…

screen-record

Record agent-driven screen demos and edit video or audio with local FFmpeg. Use for screen recording or desktop capture while computer-use tools drive a workflow; trimming setup or dead time; putting videos side by side; adding captions or subtitles;…

arena

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

interrogate

Use for interrogate, adversarial review, multi-model review, challenge this, or stress test this code. Adversaries try to break a change or design, and only findings proven by a run survive.

ketchup-video

Catch the user up like ketchup, with a short subtitled video of slides about the work and every waiting decision listed below it. Use for /ketchup-video.

poteto-help

Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

poteto-mode

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

principle-explain-the-number

Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

setup-pstack

Configure pstack’s optional per-role Codex model preferences and offer project verification skills. Use for pstack setup or role choices, not to alter Codex’s global model settings.

statechart

Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, "show the PM the bug", or to turn an agreed chart into a…

create-formal-verification-skill

Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, model-check this race, prove this…

reflect

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

swarm

Fan out independent Codex workers for coverage, competing candidates, or exploration and consolidate their evidence. Use for swarm requests or explicit parallel review and verification.

anti-slop

Use when writing, reviewing, refactoring, or repairing TypeScript or JavaScript, and when asked to anti-slop, unslop, remove AI-generated slop, fix Anti-Slop findings, improve type precision, replace unsafe assertions, parse unknown data, or avoid lint-shaped…

better-init

Create or refresh concise Codex repository guidance in AGENTS.md and task-specific project skills. Use for repository initialization, bootstrap, stale instructions, or reorganizing guidance; not for merely explaining existing instructions.

principle-prove-it-works

Use when implementing a feature, fixing a bug, changing behavior, or refactoring code, including ordinary implement/fix/change requests that do not ask for proof. Check the actual acceptance condition and return proportionate evidence by default, or name the…

pstack-schema-validate

Validate pstack snapshots, verification receipts, durable handoffs, or Markdown plans against the plugin's versioned contracts. Use for "validate this pstack artifact", checking pstack JSON, or verifying a pstack plan profile. Not for general JSON schema…

show-me-your-work

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or…

correct

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each…

ketchup

Catch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /ketchup.

maintain-formal-verification-skill

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in…

principle-test-behavior-not-implementation

Apply when writing, changing, reviewing, or keeping tests. Call the code as its users do and assert an independently specified result or effect. Rewrite tests that would pass when the behavior they claim to prove is broken.

sharpen

Make a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.

highlight-reel

Mine a long talking-head or livestream recording into a verified highlights reel: timestamped highlight clips cut with ffmpeg, key-frame candidates from scene-diff, and takeaways with verbatim-verified quotes. Routes media understanding across local OMLX…

image-gen

Create or generatively edit images into saved PNG files with local OMLX models. Not for image analysis, screenshot explanations, or ordinary resizing and conversion.

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

automate-me

Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode Agent Skill, optionally pulling evidence from recent…

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

create-verification-skill

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove…

figure-it-out

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for…

how

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding…

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

principle-never-block-on-the-human

Apply when tempted to ask 'should I do X?' on reversible work.

recall

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working…

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

unslop

Cut AI tells from any writing. Must always apply.

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat,…