// Marketing & SEO

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.

Get it on Agensi Browse all skills $19 one-time

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

fixture-backed sample

input An MCP server reports version 0.6.0 and $0.25 on its homepage, while its registry entry reports 0.5.0, its pricing evidence reports $0.15, a launch claim cites no supplied surface, and Show HN evidence says the product is not directly tryable.

result Gate: BLOCK. Stable findings identify PRODUCT_VERSION_DRIFT, PRICE_CONTRACT_DRIFT, DISTRIBUTION_CLAIM_UNSUPPORTED, and SHOW_HN_TRY_PATH_BLOCKED. The report preserves coverage metrics, limitations, and a deterministic SHA-256 receipt.

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.

// choose with context

Is Agent Distribution Readiness Pack the right skill?

Best fit

A skill, MCP server, or paid agent product needs a pre-release consistency check across its package, documentation, pricing, discovery surfaces, evidence, and channel claims.

It returns

A READY, REVIEW, or BLOCK gate, a stable finding ledger, coverage metrics, and JSON and Markdown reports with a SHA-256 receipt.

Do not use it as

It does not crawl or authenticate live surfaces, publish a launch, control an account, or predict acceptance, ranking, demand, or revenue.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: distribution-readiness-input.json, readiness-report.json, readiness-report.md.
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. Documented UTF-8 JSON evidence packets for MCP servers, agent skills, and paid APIs.
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 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.