agentsclimarketplace

Distributed workflow and integration analyzer

Skill anyulled/architecture-guardrails-skills/skills/distributed-workflow-and-integration-analyzer

Agent-agnostic software architecture guardrails skills collection

Install
npx -y skills add anyulled/architecture-guardrails-skills --skill distributed-workflow-and-integration-analyzer

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.

What its author says it does

Copied from the file, not written here

Map inter-service communication, distributed workflows, Saga patterns, and operational coupling across services. Use when reviewing REST, gRPC, brokers, distributed transactions, or temporal coupling risks.

SKILL.md

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

Distributed Workflow and Integration Analyzer

Trace service-to-service communication and classify distributed workflow risks.

When to Use

  • PRs introducing inter-service communication
  • Distributed transaction changes
  • Message broker, REST, or gRPC integration changes
  • Microservice resilience and workflow audits

Scope

  • Scans: HTTP clients, gRPC stubs, GraphQL mutations, Kafka/RabbitMQ/SQS/SNS publishers and consumers, database connection strings, and deployment configs that shape cross-service workflows.
  • Exclusions: single-process helper calls, intra-service sync code, and broker or network details that are not part of a distributed workflow boundary.
  • Fallback: if a workflow boundary is uncertain, use the shared conventions fallback and report warning with low confidence.
  • Routing: defer event-payload autonomy to Event-Driven Architecture Integrity Evaluator and deployability boundaries to Architectural Quantum and Deployability Validator.

Workflow

  1. Trace integration points.
    • Scan HTTP, gRPC, GraphQL, broker, and database connection usage.
    • Build a distributed communication graph.
  2. Classify distributed workflows.
    • Determine synchronous vs asynchronous communication.
    • Determine orchestration vs choreography.
    • Identify saga-like multi-step workflows.
  3. Detect operational coupling.
    • Flag synchronous call chains that create cascade risk.
    • Flag distributed transaction anti-patterns such as 2PC or missing compensations.
  4. Report findings.
    • List the most coupled integration points.
    • Map workflow coordination styles.
    • Include file paths and functions for violations.

Rules

  • Use static analysis and AST parsing only.
  • Do not execute network calls.
  • Keep analysis deterministic and language-agnostic.
  • Prefer architecture-review output that is easy to gate in CI.

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:

  • Top coupled integration points
  • Distributed workflow classifications
  • Temporal coupling violations
  • 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 automation workflows skills give in 459 tokens

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

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Trace integration points
  • Build a distributed communication graph
  • Classify synchronous versus asynchronous communication
  • Determine orchestration versus choreography
  • Identify saga-like multi-step workflows
  • Flag synchronous call chains creating cascade risk

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 327,069. 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.