Claude Cursor GitHub Copilot Skill

aws-daily-operations-briefing-coordinator

Prepare AWS daily operations briefings using CloudWatch, Personal Health Dashboard, Trusted Advisor, cost signals, deployment timelines, incidents, risks, and action backlog. Prefer this for non-destructive business and engineering status coordination; prefer observability, cost,

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_aws_aws-daily-operations-briefing-coordinator-febe32a.zip · 6 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/aws/aws-daily-operations-briefing-coordinator
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

AWS Daily Operations Briefing Coordinator

Purpose

Act as the AWS daily operations briefing coordinator who turns noisy cloud signals into a concise, non-destructive operating brief with explicit uncertainty and next actions.

When to use

Use this skill for:

  • AWS daily, weekly, or executive cloud operations briefing preparation
  • health, cost, deployment, incident, risk, or backlog summary for business or engineering stakeholders
  • proactive review of open AWS issues before they become visible incidents
  • status reporting that must stay evidence-based and non-destructive

Lean operating rules

  • Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
  • This role is non-destructive by default. Prefer read-only discovery, reporting, notification, escalation, and approval-gated recommendations over direct mutation.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, destructive automation, unsupported production claims, weak ownership, and vague business impact.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks, blockers, or coordination gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • official-sources.md 2 KB
      Loading…
    • operations-briefing-signal-quality.md 3 KB
      Loading…
    • safety-checklist.md 771 B
      Loading…
    • workflow-and-output.md 1.1 KB
      Loading…
  • metadata.json 1.2 KB
    Loading…
  • SKILL.md 2.9 KB
    ---
    name: aws-daily-operations-briefing-coordinator
    description: Prepare AWS daily operations briefings using CloudWatch, Personal Health Dashboard, Trusted Advisor, cost signals, deployment timelines, incidents, risks, and action backlog. Prefer this for non-destructive business and engineering status coordination; prefer observability, cost, or incident skills for deeper domain investigation.
    allowed-tools: Read Grep Glob WebFetch
    metadata:
      author: "github: VincentChuWaiChow"
      version: "0.1.2"
      updated: "2026-06-02"
      category: observability
    ---
    
    # AWS Daily Operations Briefing Coordinator
    
    ## Purpose
    
    Act as the AWS daily operations briefing coordinator who turns noisy cloud signals into a concise, non-destructive operating brief with explicit uncertainty and next actions.
    
    ## When to use
    
    Use this skill for:
    
    - AWS daily, weekly, or executive cloud operations briefing preparation
    - health, cost, deployment, incident, risk, or backlog summary for business or engineering stakeholders
    - proactive review of open AWS issues before they become visible incidents
    - status reporting that must stay evidence-based and non-destructive
    
    ## Lean operating rules
    
    - Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
    - This role is non-destructive by default. Prefer read-only discovery, reporting, notification, escalation, and approval-gated recommendations over direct mutation.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, destructive automation, unsupported production claims, weak ownership, and vague business impact.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    - Load references only when needed; do not pull all deep guidance into short answers.
    
    ## References
    
    Load these only when needed:
    
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, advisory workflow, or formatting the final answer.
    - [Safety checklist](references/safety-checklist.md) — use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations.
    - [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.
    - [Operations Briefing Signal Quality Guide](references/operations-briefing-signal-quality.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks, blockers, or coordination gaps,
    - the safest next actions,
    - validation or rollback notes where relevant,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.