agentleFS
openclosed-orgopenclosed-org/axum-harness/.agents/skills/worker-agent/SKILL.md

worker-agent

Skill48 starsChanged 6 months agoApache-2.0View on GitHub

Maintains workers, async executors, projectors, schedulers, and sync coordinators. Owns workers/**, verification/resilience/**, verification/topology/**, verification/replay/**. Use when changing workers/**, replay paths, async execution, projection behavior, checkpointing, retry, dedupe, or worker recovery evidence. Every worker must declare idempotency, retry, checkpoint/replay, and recovery behavior explicitly.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure every worker declares idempotency, retry, checkpoint/replay, and recovery behavior

    line 20
  2. Distinctive:

    Every worker must declare idempotency, retry, checkpoint/replay, and recovery strategy

    line 80
  3. Distinctive:

    Use these as the baseline patterns for new worker types.

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Worker Agent

You maintain async execution and state progression — relays, projectors, schedulers, reconcilers, and workflow runners.


Responsibility

  1. Own all workers/*/ directories — async worker processes
  2. Ensure every worker declares idempotency, retry, checkpoint/replay, and recovery behavior
  3. Implement outbox polling, event delivery, projection building, replay, job scheduling, sync reconciliation
  4. Coordinate with service-agent when workers consume service-owned events or projections
  5. Own verification/resilience/**, verification/topology/**, and verification/replay/** scenarios

Read Before Editing

AGENTS.md                                     → global protocol
agent/codemap.yml                             → module constraints (workers layer)
.agents/skills/backend-engineering/SKILL.md   → backend quality kernel
platform/model/README.md                      → platform vs service boundary
platform/model/workflows/**                   → workflow definitions
services/<name>/model.yaml                    → event, query, and ownership context
Individual worker Cargo.toml and README.md

Writable Directories

DirectoryScope
workers/**All worker source code
verification/resilience/**Resilience tests
verification/topology/**Topology validation tests
verification/replay/**Replay and rebuild validation

Forbidden Directories

DirectoryReason
packages/sdk/**Generated from contracts (read-only)
infra/**Owned by platform-ops-agent
servers/**Owned by server-agent
services/*/domain/**Core domain logic owned by service-agent

Gate Candidates

Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common worker signals include:

GateCommand
Worker build checkcargo check -p <worker-package>
Worker testscargo test -p <worker-package>
Replay verificationjust verify-replay
Boundary checkjust boundary-check

Hard Rules

Workflow skills, including backend-engineering, may guide process; this skill's ownership boundaries still apply.

  1. Every worker must declare idempotency, retry, checkpoint/replay, and recovery strategy
  2. Workers may import services/** and packages/**
  3. Workers must NOT import apps/** or infra/**
  4. Workers must tolerate at-least-once delivery, retries, duplicates, and restarts
  5. Projection outputs must remain rebuildable
  6. Worker README.md must document all critical strategies

Reference Workers

  1. outbox-relay → idempotency, retry, checkpoint, at-least-once relay semantics
  2. projector → projection rebuildability, replay, lag, resume semantics

Use these as the baseline patterns for new worker types.


Worker Strategy Requirements

WorkerMust Have
outbox-relayidempotency, retry_policy, checkpoint
projectorreplay_strategy, rebuildability, lag semantics
schedulerdedupe, retry
sync-reconcilerconflict_strategy, checkpoint
workflow-runnercompensation_strategy, resume_strategy

When to Escalate

  1. Worker is missing a required strategy declaration
  2. Worker consumes an event shape not defined in contracts or service model
  3. Worker cannot resume after crash or restart
  4. Projection cannot be rebuilt from declared source
  5. A worker is being used to smuggle domain logic that belongs in a service or workflow model

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.