agent-tooling

Run recursive, machine-first code review, review application, and full-cycle convergence workflows with the `mpcr` CLI. Use when the task involves: (1) Reviewing a diff, pull request, or set of commits, (2) Applying structured review findings back to code, (3) Validating canonical review artifacts or report trees, (4) Driving review→apply→verify convergence loops, or (5) Any task requiring systematic, multi-pass code review with per-agent report trees.

Generate hardened, production-ready Docker architecture including Dockerfiles, Compose stacks, and Swarm deploy configs. Use when the task involves: (1) Writing or improving a Dockerfile or multi-stage build, (2) Containerizing an application (Python, Node.js, Rust, Go, Nginx, or custom stacks), (3) Creating or modifying compose.yaml or Docker Swarm deployments, (4) Hardening container security, healthchecks, secrets management, or resource limits, (5) Setting up CI/CD container scanning or image supply-chain controls (hadolint, trivy, docker scout, SBOM, provenance), or (6) Any task involving Docker, containers, or container orchestration.

Build portable dynamic Espanso forms where a script or binary generates form layouts at runtime. Use when the task involves: (1) Creating or modifying Espanso form triggers or match files, (2) Building dynamic Espanso forms with runtime-generated layouts or choices, (3) Scaffolding a new Espanso form provider pattern, (4) Configuring Espanso YAML for scripted fields or runtime-generated options, (5) Debugging or linting Espanso form configurations, (6) Implementing clipboard or output patterns for Espanso expansions, or (7) Any task involving Espanso text expansion with dynamic or scripted form UIs.

Inspect, create, diff, document, audit, automate, and sync Excel workbook artifacts across package-readable workbooks, safe copies, installed desktop Excel, Microsoft Graph workbook APIs, Office Scripts/Add-in hosts, and Fabric/Power BI semantic models. Use when the task involves: (1) workbook lifecycle or direct commands such as inspect/diagnose/capabilities/create/diff/save-as/ convert/repair/compatibility/document-inspect, sheet/table/range/cell/name edits, links, safe export, formulas, calc, Solver, scenarios, forecasts, data tables, or automation artifacts, (2) package inventory or preservation for charts, pivots, slicers, timelines, Power Query, connections, XML/custom XML, OLE, signatures, encryption, sensitivity, VBA/package metadata, or embedded media, (3) desktop Excel host operations, (4) Graph, Office Scripts, Office.js/Add-in, Fabric, Power BI, DAX, TMDL, PBIP, or semantic-model operations, or (5) manifest/artifact synchronization, audit bundles, parity reports, and portable workbook manifests.

REQUIRED for every task. Log every error, failure, unexpected outcome, or friction encountered — no exceptions. Covers: (1) Any tool, command, script, or build step that fails or produces unexpected results, (2) Any instruction, workflow, or environment that behaves differently than expected, (3) Code bugs, compilation errors, test failures, or runtime exceptions, (4) MCP server, subagent, or integration misbehavior, (5) User-requested friction or diagnostic reporting, (6) Any problem, error, or divergence from expected behavior during task execution. If anything goes wrong, it gets logged here. Do not skip this skill.

End-to-end GitOps workflow governance and automation covering branching, Conventional Commits, PR lifecycle, CI gating, and release management. Use when the task involves: (1) Creating a Git branch from the default branch, (2) Writing or enforcing Conventional Commit messages, (3) Creating, updating, reviewing, or merging pull requests, (4) Generating squash-merge commit messages or release notes, (5) Setting up or enforcing CI gating policies, (6) Automating Git or GitHub CLI (gh) workflows, (7) Enforcing team Git workflow standards or branch naming conventions, or (8) Any task requiring structured Git operations with auditability and governance. Includes helper scripts for git and GitHub CLI.

Design durable, outcome-oriented Playwright and browser e2e tests that prove product behavior instead of recording today's DOM. Use when the task involves: (1) Creating, reviewing, or refactoring Playwright tests, (2) Designing selector strategies, page objects, fixtures, e2e assertions, or trace/artifact capture, (3) Reducing brittle selectors, fixed waits, layout assertions, or flaky authenticated flows, (4) Testing third-party, authenticated, frequently changing, or browser-extension UIs, or (5) Any task involving Playwright e2e test design or brittle-test cleanup.

Detects repo languages, frameworks, task runners, distribution shape, and CI surface, then scaffolds or updates a repo-level harness: justfile, GitHub Actions CI/dist workflows, .gitignore/.gitattributes support files, and local state under .local/harness/. Use when the task involves: (1) Bootstrapping a new or existing repo with a standardized command surface, (2) Creating or updating a justfile with build, test, lint, fmt, ci, dev, or dist recipes, (3) Scaffolding GitHub Actions CI or distribution workflows, (4) Configuring .gitignore, .gitattributes, or Git LFS for a project, (5) Standardizing or updating a project command surface without rewriting build system internals, or (6) Any task requiring repo-level harness scaffolding or project command surface management.

REQUIRED when any part of the task touches Rust code or Rust tooling — do not write, review, debug, or scaffold Rust without this skill active. Covers: (1) Writing new Rust code, features, or bugfixes, (2) Migrating an existing tool or codebase to Rust, (3) Reviewing Rust pull requests or enforcing Rust coding standards, (4) Setting up Rust CI/CD pipelines or GitHub Actions, (5) Creating or modifying Rust workspace layouts (single-crate or monorepo), (6) Scaffolding a new Rust project or crate, (7) Configuring Clippy lints, rustfmt, or Rust toolchain settings, (8) Debugging Rust compilation errors or borrow-checker issues, or (9) Any task where the primary language is Rust (.rs files). If the task involves Rust, use this skill.

Audit a skill's packaging, trigger behavior, task leverage, context design, verification loop, and AGENTS.md adherence, then produce a concise Skill Improvement Brief. Use when the task involves: (1) Auditing or self-auditing a skill for quality or correctness, (2) Health-checking a skill's trigger reliability or context efficiency, (3) Evaluating whether a skill belongs as a skill, AGENTS.md entry, explicit prompt, or tool, (4) Reviewing or revising a skill's packaging, descriptions, or references, or (5) Any task requiring structured skill evaluation with concrete improvement checks.