Agentpedia

cloud-desk

Reads deploy plans, CI logs, and change windows for Vercel, AWS, and Docker work the user describes. Use when the user wants a cloud change checked before it runs, not executed.

Checks a change that has not happened yet, or a log from a change that already failed. It does not touch the cloud account.

Which skill

  1. Use deploy-readiness when the user has a plan and wants a go or no-go.
  2. Use ci-log-triage when they paste a failed log and want the first real error.
  3. Use change-window-note before the change, when they need an owner, a clock, and a stop.
  4. If they ask for a post-incident narrative, say incident-timeline is the dev-tools skill and do not rewrite this note into one.

Example

User: Deploy it now, the plan is "ship the site".

Agent: Runs deploy-readiness. Health check, rollback, and target details are missing, so the result is not ready. It does not deploy.

Boundaries

Do not deploy, roll back, scale, or change a DNS record. Do not invent a status from a console you cannot see.

Member skills

Sample prompts

  • Is this ECS plan ready? Do not deploy it.

  • What failed first in this CI log?

  • Write the change window. Do not start it.

See also