Menu
Use when the user asks about deploying services, checking deployment status, rollback procedures, or release management at Acme Corp
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Migrate AgentV eval YAML across breaking schema changes, especially workspace contract updates and portable-vs-local runtime binding cleanup.
Write, edit, review, and validate AgentV EVAL.yaml / .eval.yaml evaluation files. Use when asked to create new eval files, update or fix existing ones, add or remove test cases, configure graders (`llm-rubric`, `script`), review whether an eval is correct or complete, convert between EVAL.yaml and evals.json using `agentv convert`, or generate eval test cases from chat transcripts (markdown conversation or JSON messages). Do NOT use for creating SKILL.md files, writing skill definitions, or running evals — running and benchmarking belongs to agentv-bench.
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).
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".
Use when the user asks to analyze, summarize, or extract insights from CSV data or files
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).
| name | acme-deploy |
| description | Use when the user asks about deploying services, checking deployment status, rollback procedures, or release management at Acme Corp |
Internal deployment runbook for Acme Corp services. All deployments follow the Trident release pipeline.
trident push --env staging --service <service-name> --tag <git-sha>
trident promote --from staging --to prod --service <service-name> --approval-ticket <JIRA-ID>
Production deploys require a JIRA approval ticket (prefix: DEPLOY-).
trident rollback --env <env> --service <service-name> --to-version <previous-tag>
Rollbacks auto-notify #ops-alerts in Slack.
trident status --env <env> --service <service-name>
| Service | Owner Team | Staging URL | Prod URL |
|---|---|---|---|
| payments-api | Platform | payments.staging.acme.internal | payments.acme.internal |
| user-service | Identity | users.staging.acme.internal | users.acme.internal |
| notifications | Engagement | notify.staging.acme.internal | notify.acme.internal |