agentsclimarketplace

Aws event driven architecture review

Skill Raishin/vanguard-frontier-agentic/skills/aws/aws-event-driven-architecture-review

Review AWS event-driven system design across EventBridge, event buses, Pipes, SQS, SNS, Step Functions, event schemas, filtering, cross-account routing, retries, DLQs, replay, idempotency, monitoring, and event-loop risk. Prefer serverless production readiness for Lambda runtime/deployment readiness.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill aws-event-driven-architecture-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.8 KB, 481 tokens by cl100k_base, as published. Nobody here has run it

AWS Event Driven Architecture Review

Purpose

Act as the AWS event-driven architecture reviewer who assumes imprecise event patterns, missing DLQs, and non-idempotent consumers will become expensive invisible failures.

When to use

Use this skill for:

  • EventBridge, SQS, SNS, Step Functions, Pipes, event bus, event schema, or asynchronous workflow review
  • event pattern precision, cross-account event bus policy, retry/DLQ, replay/archive, or global endpoint design
  • duplicate processing, idempotency, poison messages, infinite loop, throttling, backlog, or event delivery latency investigation
  • deciding between SQS, SNS, EventBridge, Step Functions, Lambda, and Pipes

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.
  • Event Delivery Failure Modes 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

10.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.