Skills: utilities (2/2)
Agent Skills in the utilities category, with argument hints and descriptions from the release.
20 skills in this category.
| Skill | Details |
|---|---|
av:loop | Autonomous iterative optimization loop — run N iterations against a mechanical metric, learn from git history, auto-keep/discard changes. Use for improving measurable metrics (coverage, performance, bundle size, etc.) through repeated experimentation. — Arguments: [Goal/Metric description] or inline config block |
av:markdown-novel-viewer | View markdown files in a calm, book-like reader served via HTTP. Use for long-form content review — RFCs, runbooks, design docs, reports, specs, novels — anywhere you want a distraction-free reading mode in the browser. — Arguments: [file-or-directory] |
av:mermaidjs-v11 | Create diagrams with Mermaid.js v11 syntax. Use for flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, state diagrams, architecture diagrams, timelines, user journeys. — Arguments: [diagram-type or description] |
av:plan | Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation, editorial self-contained HTML plan artifacts with --html, and AgentWiki publishing with --wiki. — Arguments: [task] [--fast|--hard|--deep|--parallel|--two] [--tdd|--no-tasks] [--html] [--github] [--wiki] [--advice] [--yagni] [--skip-journal] OR [archive|red-team|validate] |
av:plan-i18n | Add a bilingual Vietnamese/English language-switch to a plan.html artifact. Use after /av:plan --html when the user wants bilingual or dual-language plan output. — Arguments: [plan-dir] |
av:predict | 5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes. — Arguments: <feature description or change proposal> [--files <glob>] [--chain reason|probe] |
av:preview | View files or generate visual explanations, slides, and diagrams. Use for code walkthroughs, architecture visualization, HTML/Markdown presentations. — Arguments: [path] OR [--html] --explain|--slides|--diagram|--ascii [topic] OR --html --diff|--plan-review|--recap |
av:problem-solving | Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty. — Arguments: [problem description] |
av:project-management | Track progress, update plan statuses, coordinate runtime work, generate reports, and preserve cross-session continuity. — Arguments: [task: status, hydrate, sync, report] |
av:project-organization | Organize files, directories, and content structure in any project. Use when creating files, determining output paths, organizing existing assets, or standardizing project layout. — Arguments: [directories or files to organize] |
av:research | Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis. — Arguments: [topic] [--yagni] |
av:research-prompt | Draft a self-contained research brief for a human or AI researcher. Use when users ask for a research prompt, research brief, or a deep-research task to hand off. — Arguments: <research topic | decision> |
av:retro | Generate data-driven sprint retrospectives from any git history. Use for sprint reviews, commit analysis, code-health indicators, team-velocity reporting, and quarterly engineering reviews. Works on solo or team repos. — Arguments: [timeframe] [--compare] [--team] [--format html|md] |
av:review-pr | Review a GitHub pull request thoroughly — analyze diff for correctness, security, breaking changes, code quality, and AI-slop patterns. Supports --fix to auto-remediate findings, --reply to post the review back to GitHub via the gh CLI as a formal review, and --merge to merge a ready PR and watch post-merge CI to green. — Arguments: <PR number or URL> [--fix] [--reply] [--merge] [--advice] |
av:scenario | Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use for pre-implementation risk discovery, QA planning, regression design, and iterative saturation when coverage must be exhaustive. — Arguments: <file path or feature description> [--iterations N] [--saturation] |
av:security | STRIDE + OWASP-based security audit with optional red-team persona discovery loop and auto-fix. Scans code for vulnerabilities from multiple attacker perspectives (auth attacker, supply chain, insider, infrastructure), categorizes by severity, and can iteratively fix findings using av:autoresearch pattern. — Arguments: <scope glob or 'full'> [--fix] [--red-team] [--iterations N] |
av:security-scan | Scan codebase for security vulnerabilities, hardcoded secrets, dependency issues, and OWASP patterns. Use when asked to 'security scan', 'check for secrets', 'audit security', or before major releases. — Arguments: [scope] [--secrets-only] [--deps-only] [--full] |
av:sequential-thinking | Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction. — Arguments: [problem to analyze step-by-step] |
av:test | Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports. — Arguments: [context] OR ui [url] |
av:watzup | Generate short handoff reports from Git branches, remote refs, worktrees, unfinished plans, and roadmap docs. Surfaces priority-ranked next steps with checkbox progress and rationale. Use when the user asks what's in flight, wants progress/next steps, is in a fresh worktree or detached checkout, or needs end-of-session status. |