Aws daily operations briefing coordinator
Skill Raishin/vanguard-frontier-agentic/skills/aws/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, or incident skills for deeper domain investigation.From its SKILL.md
npx -y skills add Raishin/vanguard-frontier-agentic --skill aws-daily-operations-briefing-coordinatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.9 KB, 463 tokens by cl100k_base, as published. Nobody here has run it
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 — use when executing the full review, advisory workflow, or formatting the final answer.
- Safety checklist — use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- Operations Briefing Signal Quality Guide — 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.
What ships with it: 5 files
8.0 KB alongside SKILL.md
references/
- metadata.json1.2 KB