entityprocess/acme-deploy
examples/features/agent-skills-evals/workspace/.codex/skills/acme-deploy/SKILL.md
Use when the user asks about deploying services, checking deployment status, rollback procedures, or release management at Acme Corp
$ install --global
skillsauthnpx skillsauth add entityprocess/agentv acme-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 12:24 PM13.6s1 file scanned
SKILL.md
- name:
- acme-deploy
- description:
- Use when the user asks about deploying services, checking deployment status, rollback procedures, or release management at Acme Corp
Acme Corp Deployment Procedures
Overview
Internal deployment runbook for Acme Corp services. All deployments follow the Trident release pipeline.
Deployment Commands
Deploy to staging
trident push --env staging --service <service-name> --tag <git-sha>
Promote to production
trident promote --from staging --to prod --service <service-name> --approval-ticket <JIRA-ID>
Production deploys require a JIRA approval ticket (prefix: DEPLOY-).
Rollback
trident rollback --env <env> --service <service-name> --to-version <previous-tag>
Rollbacks auto-notify #ops-alerts in Slack.
Check deployment status
trident status --env <env> --service <service-name>
Service Registry
| 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 |
Rules
- All prod deploys require a DEPLOY- JIRA ticket
- Staging deploys are auto-approved during business hours (9am-5pm PT)
- Rollbacks bypass approval but require post-mortem within 48h
- Deploy freezes are announced in #engineering-announcements
Related Skills
entityprocess/agentv-trace-analyst
tools
VerifiedTrustedCommunity
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.
12SKILL.mdUpdated May 25, 2026
entityprocess/agentv-governance
development
VerifiedTrustedCommunity
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.
12SKILL.mdUpdated May 25, 2026
entityprocess/agentv-eval-writer
development
VerifiedTrustedCommunity
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-grader`, `code-grader`, `rubrics`), 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.
12SKILL.mdUpdated May 25, 2026
entityprocess/agentv-eval-review
development
VerifiedTrustedCommunity
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).
12SKILL.mdUpdated May 25, 2026