AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Distributed Consensus

skill-kentoshimizu-sw-agent-skills-distributed-consensus · by KentoShimizu

Consensus workflow for quorum, leader election, commit semantics, and membership change safety. Use when replicated-state correctness requires coordinated agreement across nodes under faults; do not use for non-replicated single-node workflows.

↗ Repository
— No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-kentoshimizu-sw-agent-skills-distributed-consensus

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Distributed Consensus? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Distributed Consensus

Overview

Use this skill when system correctness depends on multiple nodes agreeing on state transitions under crash and partition conditions.

Scope Boundaries

  • Replicated writes require explicit safety/liveness guarantees.
  • Quorum and leadership behavior determine correctness.
  • Membership changes and failover policy must be defined safely.

Shared References

  • Consensus policy rules:
  • references/consensus-policy-rules.md

Templates And Assets

  • Consensus policy template:
  • assets/consensus-policy-template.md

Inputs To Gather

  • Replicated state machine requirements.
  • Fault model (crash, partition, byzantine assumptions).
  • Latency/availability targets and quorum constraints.
  • Membership change and recovery expectations.

Deliverables

  • Consensus policy decisions (quorum, election, commit semantics).
  • Safety/liveness assumptions and risks.
  • Operational policy for split-brain and degraded mode.
  • Validation plan for failover and rejoin scenarios.

Workflow

  1. Capture policy baseline in assets/consensus-policy-template.md.
  2. Define safety invariants and availability targets.
  3. Select quorum, leadership, and commit rules using references/consensus-policy-rules.md.
  4. Define partition, degraded-mode, and recovery behavior.
  5. Define membership change strategy and validation sequence.
  6. Validate with failure simulation and state convergence checks.

Quality Standard

  • Safety invariants are explicit (no divergent committed state).
  • Liveness tradeoffs are acknowledged under partition conditions.
  • Membership changes preserve quorum guarantees.
  • Recovery/rejoin behavior is deterministic and tested.

Failure Conditions

  • Stop when quorum or commit semantics are undefined.
  • Stop when partition behavior can cause split-brain writes.
  • Escalate when membership change procedure risks safety violation.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills