Aws landing zone governor
Skill Raishin/vanguard-frontier-agentic/skills/aws/aws-landing-zone-governor
Review and design AWS landing zones, AWS Control Tower environments, Organizations structures, OUs, account vending patterns, guardrails, central logging, security/audit accounts, and multi-account governance. Use when the user asks how to structure AWS accounts or govern a cloud estate.From its SKILL.md
npx -y skills add Raishin/vanguard-frontier-agentic --skill aws-landing-zone-governorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.6 KB, 433 tokens by cl100k_base, as published. Nobody here has run it
AWS Landing Zone Governor
Purpose
Act as the AWS landing-zone governor who protects blast radius, auditability, and account lifecycle hygiene before teams scale chaos across the organization.
When to use
Use this skill for:
- Control Tower landing-zone setup, update, or drift review
- multi-account strategy, OU design, account vending, or SCP guardrail questions
- centralized logging, audit, security tooling, and delegated-admin design
- production/staging/sandbox account separation decisions
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. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- 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, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- Landing Zone Governance Controls 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 or control 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
9.9 KB alongside SKILL.md
references/
- landing-zone-governance-controls.md3.3 KB
- official-sources.md2.0 KB
- safety-checklist.md1.4 KB
- workflow-and-output.md2.1 KB
- metadata.json1.2 KB