agentsclimarketplace
Sign in

Event driven architecture eda integrity evaluator

Skill anyulled/architecture-guardrails-skills/skills/event-driven-architecture-eda-integrity-evaluator

Evaluate event-driven architectures for payload design, consumer autonomy, broker entanglement, and synchronous callback anti-patterns. Use when reviewing schemas, publishers, consumers, or broker configurations.From its SKILL.md

Install
npx -y skills add anyulled/architecture-guardrails-skills --skill event-driven-architecture-eda-integrity-evaluator

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

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 444 tokens by cl100k_base, as published. Nobody here has run it

Event-Driven Architecture (EDA) Integrity Evaluator

Analyze event-driven systems for autonomy, payload quality, and broker coupling.

When to Use

  • PRs that change event schemas, publishers, or consumers
  • Message broker configuration changes
  • Architectural audits of async or event-driven services

Scope

  • Scans: event publishers and consumers, schema registry definitions such as proto/avsc files, and broker configuration for topics, queues, exchanges, or subscriptions.
  • Exclusions: direct synchronous APIs, maintenance scripts, and documented notification envelopes that intentionally do not carry full state.
  • Fallback: if payload autonomy is unclear, use the shared conventions fallback and report warning with low confidence.
  • Routing: defer synchronous workflow concerns to Distributed Workflow and Integration Analyzer and shared-table or read-model ownership to Data and Database Coupling Evaluator.

Workflow

  1. Analyze payload state.
    • Distinguish notification events from event-carried state transfer.
    • Flag minimal events that force synchronous lookups after publication.
  2. Verify consumer autonomy.
    • Trace consumer execution for immediate downstream calls.
    • Flag consumers that cannot process events from local data alone.
  3. Check broker entanglement.
    • Detect business logic embedded in broker routing or stream configuration.
    • Flag overly broad or fat topics with excessive unrelated subscribers.
  4. Report findings.
    • Identify synchronous callback anti-patterns.
    • List consumers and topics that violate autonomy.

Rules

  • Use static analysis only.
  • Inspect schemas, broker config, and source code only.
  • Keep analysis deterministic and language-agnostic.
  • Prefer bounded-context autonomy over shared middleware logic.

Shared Conventions

  • Follow the repository-wide conventions in shared-skill-conventions.
  • Use the canonical output contract, severity levels, confidence rubric, routing rules, and false-positive downgrades defined there.
  • If this skill is not the closest match, defer to the routing guidance in the shared conventions file.

Output

Return:

  • Event topics with synchronous callback risk
  • Consumers lacking autonomy
  • Broker entanglement findings
  • CI-ready pass or fail output

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most architecture codebase skills give in 444 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • distinguish notification events from event-carried state transfer
  • flag minimal events forcing synchronous lookups
  • trace consumer execution for downstream calls
  • flag consumers lacking local data processing
  • detect business logic in broker routing
  • flag overly broad topics with unrelated subscribers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,679. 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.