// Workflow Automation

Automation Acceptance Replay Harness

Replay automation traces against explicit rules for required steps, order, retries, approvals, idempotency, external side effects, duration, and terminal success.

Get it on Agensi Find another skill $19 one-time

What problem does Automation Acceptance Replay Harness solve?

An automation can end on a green node while a required step failed, an email or write happened twice, an external action lacked idempotency, a gated action skipped human approval, or the execution log cannot support client acceptance.

Use it to

Replay production-like executions before approving an automation release
Catch duplicate emails, writes, charges, or other side effects across retries
Verify configured human approval occurs before a gated action
Create a portable client acceptance record after workflow changes

What it returns

Severity-ranked findings CSV for each execution
Execution summary CSV with ACCEPT, REVIEW, or REJECT disposition
JSON acceptance recommendation and severity totals
Markdown handoff tied to the exact contract and supplied trace

A representative input and result

fixture-backed sample

input Contract: required ingest,classify,approve,send,record; email_sent requires idempotency and prior human_review; max retries 2. Trace: email_sent succeeded twice with side_effect_key email:lead-99; first send had no idempotency key; no approved review event; classification failed; terminal completed.

result Recommendation: REJECT Critical: duplicate successful email side effect. Critical: missing idempotency key and human approval. Critical: terminal completed after required classification failed. High: required approval and record steps missing; retry limit exceeded.

Access and approval boundaries

Read access to a user-supplied JSON contract and CSV execution trace.
Write access only to the selected local audit output directory.
No workflow platform, connector, browser, email, CRM, payment, or network access is required.

Known limitations

The result is limited to events represented in the supplied trace; missing logging can resemble missing execution.
A clean fixture does not prove that every input, connector failure, race condition, or replay scenario is covered.
External provider state must be checked separately when acceptance depends on whether an email, write, charge, or deletion actually occurred.

// choose with context

Is Automation Acceptance Replay Harness the right skill?

Best fit

An automation can end on a green node while a required step failed, an email or write happened twice, an external action lacked idempotency, a gated action skipped human approval, or the execution log cannot support client acceptance.

It returns

Severity-ranked findings CSV for each execution. Execution summary CSV with ACCEPT, REVIEW, or REJECT disposition.

Do not use it as

It does not execute a workflow, call connectors, send messages, modify systems, or verify provider state.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: automation-acceptance-input/**, automation-acceptance-output/**, *.csv, *.json.
Compatibility: CSV execution traces exported or mapped from n8n, Zapier, Make, agent frameworks, or custom workflow systems. A JSON acceptance contract using the documented platform-neutral schema. Python 3 for the included deterministic local replay helper.
Version: 1.0.0
Licence: Review the package licence and seller terms at the linked destination.

What happens next

The Agensi listing opens at the current offer. Complete purchase there, inspect SKILL.md and its bundled files, then add the complete folder to your agent.

Questions

Does it execute or replay my live workflow?

No. It replays the logic of acceptance checks over an exported trace. It does not call connectors or change external systems.

Which automation platforms work?

Any platform can work after its execution records are mapped to the documented CSV fields, including n8n, Zapier, Make, agent frameworks, and custom systems.

How does it detect a duplicate side effect?

It flags more than one successful allowed side effect sharing a side-effect key or idempotency key inside an execution trace.

How is human approval represented?

A gated action must be preceded by an event with event_type human_review and status approved in the same execution.

Does ACCEPT prove the workflow is correct?

No. ACCEPT means the supplied executions cleared the declared contract. Coverage, log completeness, semantic output quality, and external state remain separate questions.

Does it need my n8n or Zapier credentials?

No. The helper runs locally on exported files and requires no platform, connector, browser, or network access.