Agent Distribution Readiness Pack
Audit release consistency, discovery surfaces, supported claims, evidence freshness, and Product Hunt or Show HN readiness before distributing an agent product.
What problem does Agent Distribution Readiness Pack solve?
An agent product can be technically live while its homepage, documentation, pricing, registry, package, source release, transport capabilities, and promotional claims disagree or rely on stale evidence.
Use it to
- Reconcile an MCP server's homepage, docs, pricing, registry identity, transport, support, and security evidence before announcing it
- Catch version, canonical URL, or price drift across an agent skill release
- Block promotional claims that do not cite supplied release evidence
- Review Product Hunt or Show HN constraints before a human chooses to publish
What it returns
- Deterministic READY, REVIEW, or BLOCK gate with severity counts
- Stable finding ledger for release, discovery, evidence, claim, version, canonical, price, and channel-rule issues
- Required-surface coverage metrics for MCP servers, agent skills, and paid APIs
- JSON and Markdown readiness reports with a SHA-256 evidence receipt
A representative input and result
Access and approval boundaries
- Terminal permission to run the bundled local Python audit helper.
- Read access to one user-supplied normalized UTF-8 JSON evidence packet.
- Write access only to the selected local JSON and Markdown report paths.
- No browser, network, credential, account, environment-variable, registry, or publication permission is required.
Known limitations
- The audit relies on normalized owner-supplied observations and does not crawl, log in to, or independently authenticate live surfaces.
- Channel references were reviewed on 2026-08-01 and require human revalidation when platform guidance may have changed.
- READY only means no automated blocking finding appears in the supplied packet. It does not predict acceptance, ranking, demand, or revenue.
- The SHA-256 receipt proves deterministic processing of the packet and report core, not that the underlying observations are true.
- The package does not create marketing copy, publish a launch, draft HN comments, solicit votes, or control any account.
Questions
Does it open my live product pages or accounts?
No. You supply normalized observations in the documented JSON format. The bundled helper runs locally and makes no network request.
What product types does version 1 support?
MCP servers, agent skills, and paid APIs, each with an explicit required set of release and discovery surfaces.
Does it write Product Hunt or Show HN copy?
No. It audits the recorded readiness evidence and rules. It does not draft promotional copy or HN comments, publish anything, or solicit engagement.
What makes an audit BLOCK instead of REVIEW?
Unavailable or missing required surfaces, contract drift, unsupported claims, absent transport capabilities, and disallowed channel plans create blocking findings. Evidence gaps that still require judgment can produce REVIEW.
Does READY mean a platform will feature or accept the product?
No. READY only means the supplied evidence has no automated blocking finding. It is not a prediction of acceptance, ranking, attention, demand, or revenue.
Can teams compare repeated audits?
Yes. Finding codes and normalized SHA-256 receipts are deterministic, so the same evidence packet produces the same core result.
Does the receipt prove the evidence is true?
No. It proves which normalized packet and report core were processed. Human or provider verification is still required for the underlying observations.
Agent Distribution Readiness Pack keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Agent Distribution Readiness Pack on Agensi