القائمة
AWS expert guardrails — IAM least-privilege, data boundaries, cost controls, residency, and official-source validation. Trigger when designing or reviewing any AWS workload, especially agents, LLMs (Bedrock), or multi-account systems.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules that prevent coherent, consistent, complete delivery.
Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.
Decompose an epic into atomic parallelizable tasks and route each task to the right skill. Use this as a meta-router when you have more than one skill available and need to decide which applies. Trigger at the start of any multi-track epic or when the skill count in your harness exceeds ~12.
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.
Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
| name | aws-expert |
| description | AWS expert guardrails — IAM least-privilege, data boundaries, cost controls, residency, and official-source validation. Trigger when designing or reviewing any AWS workload, especially agents, LLMs (Bedrock), or multi-account systems. |
The Well-Architected pillars are the floor, not the ceiling. On AWS, IAM and cost are where agent workloads blow up first.
This skill enforces the discipline that makes AWS workloads production-safe: identity, data boundaries, cost controls, and regional residency. It is not an AWS feature tour — it is a checklist of the things that cause incidents and compliance failures when skipped.
Identity and IAM — verify least-privilege for every role and human principal:
Action: "*" with Resource: "*" on any role. Managed policies scoped to the specific function.Data boundaries — for every data store in the design:
Data residency — for each resource:
Cost controls — for every LLM, compute, or storage resource:
Network and egress — confirm:
Observability — confirm:
Run the Adversarial Gate — common AWS failure modes: wildcard IAM, public S3, uncapped Bedrock spend, missing CloudTrail data events, global endpoints on residency-sensitive data.
docs.aws.amazon.com · Well-Architected: docs.aws.amazon.com/wellarchitectedawslabs/mcp monorepo includes the AWS Documentation MCP Server — fetch current docs instead of relying on memory.github.com/awslabs · github.com/aws-ia · github.com/aws-samplesgithub.com/strands-agents/sdk-python · Bedrock agent samples under github.com/aws-samples