Best fit
Teams often call a channel experiment successful from impressions, owner activity, weak attribution, multiple simultaneous changes, or a reached metric that was never declared before the test.
// Marketing & SEO
Channel Experiment Postmortem
Audit one completed channel test against its predeclared qualified gate, attribution, owner exclusion, budgets, changed variables, and cooldown.
What problem does Channel Experiment Postmortem solve?
Teams often call a channel experiment successful from impressions, owner activity, weak attribution, multiple simultaneous changes, or a reached metric that was never declared before the test.
Use it to
- Close a marketplace or directory test against its predeclared qualified gate
- Exclude impressions, owner activity, weak attribution, and out-of-window events
- Record whether aggregate cost or effort exceeded its stop condition
- Determine when a bounded one-variable follow-up may begin after cooldown
What it returns
- REACHED, NOT_REACHED, or CANNOT_DETERMINE gate verdict
- Eligible-event review with stable exclusions and findings
- Aggregate cost and effort budget receipt
- Isolation assessment, cooldown boundary, and deterministic output receipts
A representative input and result
input A 14-day directory experiment with a predeclared two-checkout-open gate, one changed artifact, two verified external events, zero cost, three effort hours, and a seven-day cooldown.
result REACHED with two eligible checkout openings, READY packet status, no budget overrun, one isolated changed variable, and a reminder that the result does not prove causality or repeatability.
Access and approval boundaries
- Terminal permission to run the bundled local Python auditor.
- Read access to one user-selected UTF-8 JSON input.
- Write access only to one new user-selected local output directory.
- No browser, network, credential, account, environment-variable, messaging, payment, deletion, or publication permission.
Known limitations
- No external paid install or sale exists for this exact product.
- The helper cannot authenticate caller-supplied event evidence or attribution claims.
- A reached gate does not show causality, repeatability, profitability, or durable channel fit.
- The helper evaluates normalized supplied evidence and does not independently retrieve or authenticate source records.
- Malformed inputs and unsafe output paths fail closed without a successful persistence receipt.
// choose with context
Is Channel Experiment Postmortem the right skill?
It returns
REACHED, NOT_REACHED, or CANNOT_DETERMINE gate verdict. Eligible-event review with stable exclusions and findings.
Do not use it as
It does not retrieve analytics, private messages, profiles, credentials, or customer data.
Compatibility, access, version, and licence
- Reads or accesses
- Declared local scope: one owner-selected local JSON input, one new owner-selected local output directory.
- Compatibility
- SKILL.md-compatible agents that can run a local Python helper. Python 3.10 or newer on Windows, macOS, or Linux using only the standard library. One documented normalized UTF-8 JSON input and a new local output directory.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
Do impressions or page views count as a qualified gate?
No. Vanity and operational activity cannot serve as the declared qualified gate.
Does REACHED prove the channel caused the outcome?
No. It reports only that supplied eligible evidence met the predeclared gate.
What makes an event eligible?
It must match the gate metric, fall inside the window, be external and non-owner, and use direct or verified attribution.
How are budgets enforced?
Aggregate experiment cost and effort are compared with their predeclared maxima and preserved in the budget receipt.
Can it follow up automatically?
No. It records the cooldown boundary and performs no message, post, or account action.
What files does it write?
A successful run atomically creates result.json, report.md, and manifest.json in a new selected output directory.
Channel Experiment Postmortem keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Channel Experiment Postmortem on Agensi