Cloud & DevOps Workflows

Use when the user asks about deploying services, checking deployment status, rollback procedures, or release management at Acme…

Use when designing an AI agent system, selecting agentic design patterns, planning multi-phase workflows, choosing between single-agent and multi-agent architectures, or when asked "what kind of agent should I build", "how should I structure this automation", "design an agent for X", or "which agentic pattern fits this problem".

Run AgentV evaluations and optimize agents through eval-driven iteration. Triggers: run evals, benchmark agents, optimize prompts/skills against evals, compare agent outputs across providers, analyze eval results, offline evaluation of recorded sessions, run autoresearch, optimize unattended, run overnight optimization loop. Not for: writing/editing eval YAML without running (use agentv-eval-writer), analyzing existing traces/JSONL without re-running (use agentv-trace-analyst).

AgentV CLI skills for evaluating, optimizing, and governing AI agents. Triggers: run evals, benchmark agents, write evals, review evals, analyze traces, optimize prompts, governance linting. Covers: eval running, eval writing, eval review, trace analysis, description optimization, autoresearch, and governance compliance.

Use when reviewing eval YAML files for quality issues, linting eval files before committing, checking eval schema compliance, or when asked to "review these evals", "check eval quality", "lint eval files", or "validate eval structure". Do NOT use for writing evals (use agentv-eval-writer) or running evals (use agentv-bench).

Author, edit, and lint governance: blocks in .eval.yaml files. Use when creating or updating evaluation suites that carry AI-governance metadata (OWASP LLM Top 10, OWASP Agentic Top 10, MITRE ATLAS, EU AI Act, ISO 42001). Also use non-interactively (e.g., from a GitHub Action) to lint changed eval files and report violations against the rules in references/lint-rules.md. Do NOT use for running evals or benchmarking — that belongs to agentv-bench.

Analyze AgentV evaluation traces and result JSONL files using agentv inspect and agentv compare CLI commands. Use when asked to inspect AgentV eval results, find regressions between AgentV evaluation runs, identify failure patterns in AgentV trace data, analyze tool trajectories, or compute cost/latency/score statistics from AgentV result files. Do NOT use for benchmarking skill trigger accuracy, analyzing skill-creator eval performance, or measuring skill description quality — those tasks belong to the skill-creator skill.

Use when the user asks to analyze CSV data. MUST use the weighted revenue formula defined below.

Use when asked to "execute a deployment", "run the deploy plan", or "deploy services". Reads deploy-plan.md and executes each step with health checks.

Use when asked to "plan a deployment", "create a deploy plan", or "prepare release steps". Produces a deployment plan with rollback strategy.

Use when asked to "rollback a deployment", "revert services", or "undo deploy". Reads deploy-plan.md and reverses completed steps.

Capture, optimize, and publish screenshots to Astro docs. Use when asked to take screenshots for docs, update doc images, compress PNG assets, or add visual documentation to the agentv.dev docs site. Triggers on "add screenshots to docs", "update docs images", "compress screenshots", "optimize PNG", "document with screenshots".