andurilcode
15 verified skills60 total stars
technical-writing
Apply this skill whenever the user needs to write, draft, review, or improve any form of technical document — including RFCs, design docs, ADRs, runbooks, postmortems, one-pagers, internal announcements, Slack threads, PR descriptions, or any prose that communicates technical information to an audience. Triggers on phrases like 'write a design doc', 'draft an RFC', 'help me write this up', 'document this decision', 'write a runbook', 'review my doc', 'make this clearer', 'I need to announce this', 'how should I communicate this?', 'write a postmortem', 'draft a one-pager', or any situation where technical information needs to be transformed into written communication for a specific audience. Also trigger when the user pastes a draft and asks for feedback, when they need to explain a technical decision to non-technical stakeholders, or when they provide their own template and want the agent to follow it. This skill covers the full spectrum from 2-line Slack msages to multi-page design documents.
development4
kaizen
Apply kaizen continuous improvement philosophy to any codebase — identifying waste, unevenness, and overburden at the code level and producing small, actionable improvement opportunities. Triggers on '/kaizen', 'kaizen this codebase', 'continuous improvement audit', 'find waste in this code', 'what small improvements can we make?', 'improve this codebase incrementally', 'code health check', 'codebase hygiene', 'tech debt sweep', or any request to find incremental improvement opportunities in code. Also trigger when the user says 'clean up', 'tidy up', 'make this codebase better', or expresses frustration about code quality without wanting a full rewrite. This is NOT a code review skill for PRs or diffs — kaizen operates on the codebase as a whole or a focus area, looking for systemic improvement opportunities. Use this skill even for small codebases — the philosophy scales down gracefully.
development4
context-engineering-orchestrator
Entry point for context engineering work. Routes to the right skill based on what the user needs — creating instructions, debugging agent failures, building documentation, or measuring outcomes. Use this when the user's goal involves agent context but they haven't named a specific skill.
development4
kaizen
Apply kaizen continuous improvement philosophy to any codebase — identifying waste, unevenness, and overburden at the code level and producing small, actionable improvement opportunities. Triggers on '/kaizen', 'kaizen this codebase', 'continuous improvement audit', 'find waste in this code', 'what small improvements can we make?', 'improve this codebase incrementally', 'code health check', 'codebase hygiene', 'tech debt sweep', or any request to find incremental improvement opportunities in code. Also trigger when the user says 'clean up', 'tidy up', 'make this codebase better', or expresses frustration about code quality without wanting a full rewrite. This is NOT a code review skill for PRs or diffs — kaizen operates on the codebase as a whole or a focus area, looking for systemic improvement opportunities. Use this skill even for small codebases — the philosophy scales down gracefully.
development4
automate
Build automation scripts and pipelines that use coding-agent CLIs (Claude Code, Codex, Gemini CLI, GitHub Copilot CLI) in headless/non-interactive mode as the AI engine, or delegate work to cloud agents (`gh agent-task`) that open pull requests asynchronously. Use this skill whenever the user wants to write a shell script, CI job, cron task, batch processor, webhook handler, or any automation that shells out to `claude`, `codex`, `gemini`, `copilot`, or `gh agent-task` — single-turn prompts, multi-turn agentic loops, parallel fan-out across files/folders, structured JSON outputs consumed by downstream tools, or cloud-delegated tasks that produce PRs. Trigger on phrases like "script that uses Claude", "automate with Claude Code", "headless Claude", "batch process files with an LLM", "pipeline with codex exec", "gemini -p", "copilot --autopilot", "gh agent-task create", "GitHub Action that calls Claude", "cron job to review PRs", "agent loop in bash", "dispatch an agent task to open a PR", "fleet-wide agent-task across repos", or any request to integrate a coding agent CLI into an automated workflow. Also trigger when the user describes the shape of a pipeline (fan-out, map-reduce, review-then-fix, extract-then-summarize, ticket-to-PR, scheduled fleet upgrade) and AI is the engine, even if they don't name the CLI explicitly.
tools4
automate
Build automation scripts and pipelines that use coding-agent CLIs (Claude Code, Codex, Gemini CLI, GitHub Copilot CLI) in headless/non-interactive mode as the AI engine, or delegate work to cloud agents (`gh agent-task`) that open pull requests asynchronously. Use this skill whenever the user wants to write a shell script, CI job, cron task, batch processor, webhook handler, or any automation that shells out to `claude`, `codex`, `gemini`, `copilot`, or `gh agent-task` — single-turn prompts, multi-turn agentic loops, parallel fan-out across files/folders, structured JSON outputs consumed by downstream tools, or cloud-delegated tasks that produce PRs. Trigger on phrases like "script that uses Claude", "automate with Claude Code", "headless Claude", "batch process files with an LLM", "pipeline with codex exec", "gemini -p", "copilot --autopilot", "gh agent-task create", "GitHub Action that calls Claude", "cron job to review PRs", "agent loop in bash", "dispatch an agent task to open a PR", "fleet-wide agent-task across repos", or any request to integrate a coding agent CLI into an automated workflow. Also trigger when the user describes the shape of a pipeline (fan-out, map-reduce, review-then-fix, extract-then-summarize, ticket-to-PR, scheduled fleet upgrade) and AI is the engine, even if they don't name the CLI explicitly.
tools4
kintsugi
Apply kintsugi (金継ぎ) repair visibility philosophy to any codebase — finding invisible repairs and making them legible with 'gold' context. Triggers on '/kintsugi', 'kintsugi this codebase', 'repair visibility audit', 'are our fixes documented?', 'why was this changed?', 'undocumented fixes', 'invisible patches', 'git archaeology', 'missing context on past fixes', 'why does this workaround exist?', or any request to understand or document the history behind code changes. Also trigger when someone asks 'why is this code like this?', 'what incident caused this?', 'who knows why we do it this way?', or when tribal knowledge about past repairs is at risk of being lost. This skill audits the history layer of a codebase — not what the code does today, but whether past breaks and repairs are visible and legible to future developers.
development4
knowledge-architect
Apply this skill whenever knowledge is at risk of being lost, needs to be captured, or a team needs to design how knowledge flows and persists. Triggers on phrases like 'document this decision', 'we should write this down', 'how do we make sure we don't forget this?', 'someone is leaving the team', 'new person is joining', 'why did we do it this way?', 'we keep re-debating this', 'set up our knowledge system', 'our docs are a mess', 'I can never find anything', 'this keeps getting lost', 'onboarding is painful', or any situation where implicit knowledge needs to become explicit and discoverable. Also trigger when the user has just resolved an incident, completed a migration, made a vendor choice, or finished a spike — these are high-value capture moments. This skill covers the full spectrum from capturing a single insight to designing a team's knowledge architecture.
testing4
limit-thinking
Apply limit thinking whenever the user wants to understand what happens when a variable, parameter, or condition is pushed toward its extreme — zero, infinity, 100%, or any boundary. Triggers on phrases like 'what happens if we scale this?', 'what if everyone adopts this?', 'where does this break?', 'what's the ceiling?', 'how does this behave at the extreme?', 'what does this converge to?', 'what if we push this to the max?', 'what's the asymptote?', or any situation where the user is evaluating a system, strategy, rollout, or design by exploring its trajectory rather than its current state. Also trigger when someone is making a decision based on a snapshot ('should we do X?') but hasn't examined the trajectory ('what does X converge to at scale?'). This skill catches the blind spot of static evaluation — most planning failures come from reasoning about where things are, not where things are going. Use this before any scaling decision, rollout plan, or growth strategy.
development4
presentation-craft
Apply this skill whenever the user needs to create, plan, structure, or improve a presentation, talk, pitch, keynote, or slide deck. Triggers on phrases like 'make a presentation about', 'I have a talk on', 'help me structure my deck', 'create slides for', 'pitch deck for', 'I'm presenting at', 'conference talk', 'prepare a keynote', 'workshop slides', or any request that involves communicating ideas to an audience via slides and spoken delivery. Also trigger when the user has existing slides and wants to improve the narrative flow, when they need speaker notes, or when they want to rehearse timing. This skill does NOT produce .pptx files directly (use the pptx skill for file creation). This skill produces the presentation SCRIPT — the narrative blueprint that determines what each slide says, shows, and how long the presenter spends on it.
content-media4
professional-orchestrator
Entry point for professional skills — architecture, communication, process design, ethics, and leadership. Routes to the right skill based on what the user needs. Use this when the user's goal involves a professional discipline but they haven't named a specific skill.
development4
skill-router
Scan ALL available skills before any non-trivial request. Prevents skill blindness, tunnel vision, and wrong-skill selection. Entry point for all skill-assisted work.
data-ai4
summarizer
Apply this skill whenever the user asks to summarize, condense, distill, or compress any content — a document, article, meeting notes, conversation, codebase, book, research paper, video transcript, or any other source material. Triggers on phrases like 'summarize this', 'give me the TL;DR', 'condense this', 'what are the key points?', 'distill this down', 'brief me on this', 'what's the gist?', 'BLUF this', 'executive summary', 'compress this for me', or any request to reduce content while preserving its essential value. Also trigger when the user pastes a long text and implicitly wants it shortened, when they share a link and ask 'what does this say?', or when they ask for meeting notes or action items from a transcript. This skill does NOT apply to 'explain X to me' (use topic-explainer) or 'write a summary section for my doc' (use technical-writing). This skill is for when source material exists and needs to be compressed.
development4
topic-explainer
Apply this skill whenever the user asks to have a topic, concept, technology, or idea explained to them. Triggers on phrases like 'explain X to me', 'what is X?', 'how does X work?', 'teach me about X', 'help me understand X', 'break down X', 'ELI5', 'explain like I'm five', 'give me an overview of X', 'I don't understand X', 'walk me through X', or any situation where the user wants to learn or understand something rather than produce an artifact. Also trigger when someone pastes a concept and asks for clarification, when they ask 'why' something works a certain way, or when they need a refresher on a topic they've encountered before. This skill does NOT apply to 'write documentation about X' (use technical-writing) or 'analyze X' (use reasoning skills). This skill is for when the human is the learner.
documentation4
context-engineering-orchestrator
Entry point for context engineering work. Routes to the right skill based on what the user needs — creating instructions, debugging agent failures, building documentation, or measuring outcomes. Use this when the user's goal involves agent context but they haven't named a specific skill.
development4