Skip to content

ahundt/autorun-skills

v1.0.0rc5Apache-2.0

General-purpose agent skills: writing, planning reports, skill authoring, diagrams, demos, tmux testing

ai-skill-builder

Guides creation, audit, and improvement of portable Agent Skills using the shared SKILL.md format and Anthropic's established methodology, without confusing the portable specification with runtime-specific extensions. Use when the user wants to "create a skill", "create an agent skill", "build a skill", "make a new skill", "write a new skill", "improve an existing skill", "audit my skill", "audit a SKILL.md", "refine my skill", "test a skill", "test skill discovery", "install skills across harnesses", "package a skill for distribution", or needs guidance on skill structure, semantic XML regions, progressive disclosure, description quality, frontmatter, scripts, arguments, security, testing, cross-harness compatibility, or distribution.

cli-demo-recorder

Create demo videos for CLI and TUI tools. Use when user asks to "record a demo", "make a demo GIF", "create a demo video", "record my CLI tool", "asciinema demo", "demo recording script". Covers asciinema+agg+ffmpeg pipeline, tmux recording, multi-shell, and dual-purpose demo+test harnesses in Python, Rust, TypeScript, and Bash.

function-signature-and-parameter-guidance

Design and review caller-facing names and contracts: functions, tools, commands, CLI flags, parameters, config keys, env vars, profiles, event types, and node/edge identifiers. Check names, descriptions, help, docstrings, schemas, defaults, bounds, units, errors, outputs, mutation, and whether values reach behavior. Use when asked to "name a parameter", "parameter naming", "name this tool or command", "choose a flag, option, or config key", "design an options object", "one tool or two", "bool or enum here", "name a profile, field, event, node, or edge", "make names clear and unambiguous", "check ISO, platform, or language naming", "audit CLI/MCP/JSON-Schema help", "define accepted values or defaults", "what should this return on failure", "rename this without breaking callers", "improve an error message", "why did the caller pass the wrong argument", "why did this parameter do nothing", or "red-team these descriptions". Not for local variables, general prose, README copy, release notes, or commits.

mermaid-diagrams

Render Mermaid diagrams to SVG using beautiful-mermaid and bun. Use when the user asks to "render mermaid", "generate diagram", "create flowchart", "update diagrams", "render SVG from mermaid", "beautiful-mermaid", "regenerate diagrams", or needs to convert Mermaid diagram syntax into styled SVG files. Supports all Mermaid diagram types with 15 themes including tokyo-night.

streamline-text

Edit prose for brevity and scanability without losing facts. Use for requests to "revise", "rewrite", "edit", "polish", "clean up", "clarify", "simplify", "condense", "tighten", "shorten", "streamline", "de-fluff", remove bloat/repetition or unnecessary newlines, fix spelling/typos without changing meaning, make text concise/compact/skimmable, or finalize drafts, messages, notes, docs, reports, issues, or reviews. Activate for "too verbose", "very verbose", or "remove unnecessary newlines", and proactively when text is verbose, wordy, meandering, dense, hard to scan, or has duplicates, vague claims, undefined terms, or cold-reader problems. Preserve evidence, qualifiers, requirements, commands, numbers, and scope with a fact index and restore/cold-reader audit. For public Reddit, Hacker News, social posts, or release notes use public-facing-writing; for PRs use write-maintainer-ready-prs; pair with avoid-ai-isms when text sounds generated.

synthesize-project-requirements

Create one evidence-backed project requirements and gotchas note from cumulative notes, current repository state, git history, and human-authored messages found with AI Session Search. Use when asked to "go through all the notes", "recover project requirements", "mine prior sessions", "collect requirements and gotchas", "make a project memory note", "prepare a project handoff", or preserve decisions and corrections for a handoff. Do not use for a one-off log summary or direct factual answer unless durable project memory or a handoff is requested. Default to the project's notes directory; publish to its documentation only when requested and add a guidance-file pointer only with permission.

task-lifecycle-workflow

Run a full evidence-to-completion lifecycle for long, correction-heavy, multi-artifact, or release-bound work. Use when asked to "coordinate dependent work", "preserve cumulative requirements", "recover off-rails work", "cold-read the result", or "continue until fully ready". Do not use for planning alone, factual answers, typos, or reversible one-owner work with one check; use Autorun's focused plan skills for those.

test-fixes-in-parallel

Test 8 to 10 fundamentally different fixes for one stubborn bug side by side, with parallel subagents, instead of one at a time. Use when the root cause is ambiguous and asked to "fix this stubborn bug", "we've tried everything", "run approaches in parallel", "use parallel subagents", or "find which config actually works". Builds a minimal test harness, runs every approach, names the fixes that work, and explains why they work.

tmux-automation

Run, watch and type into terminal programs in tmux or byobu panes without disturbing the user's other sessions. Use when asked to "test this CLI in tmux", "run it in a tmux session", "send keystrokes to a pane", "capture a pane's output", "restart the agent in that window", "resume Claude Code, Codex or Pi in its pane", or to test a terminal app on a private tmux server. Covers read-only discovery, checking the target, sending text and Enter in two calls, verifying by capture, and the resume command of each AI coding harness.

write-decision-ready-technical-reports

Turn technical investigations, plans, audits, and status updates into clear decision-ready reports without losing evidence. Use when asked to "make this plan decision-ready", "write a technical status report", "show the before and after", or clarify what is true now, what changed, what decision is needed, what each option costs, or what work remains.

write-durable-goal-prompts

Write or repair a durable goal prompt for Autorun, /goal, or another long-running agent. Use when asked for a "goal prompt", "goal paragraph", "durable goal", or when an autonomous goal became stale because it embedded a commit, count, phase, or temporary decision.