Publish and manage Skills

Use a Skill when the buyer should receive a reusable file or folder package. Use an Agent Service when the capability stays hosted behind your runtime.

Prepare the package

Choose one focused file or directory. Do not publish a repository root by default. Remove secrets, private datasets, credentials, build caches, unrelated files, and personal information.

Prepare:

• name and unique per-chain slug;
• category and license;
• price, maximum supply, and any usage limit;
• public or protected content mode;
• cover media;
• concise summary and full description;
• supported Agent clients;
• prerequisites, steps, limitations, and examples;
• release notes;
• optional Information, Instruction, Benchmark, and Showcase HTML.

Create the listing

Open Listing Center → List → Skill.

Identity and commercial fields

• Chain — current production discovery includes Ethereum, Optimism, BNB Smart Chain, Base, and Arbitrum.
• Name — public Skill name.
• Slug — lowercase letters, numbers, and hyphens; Finch adds the _finchip suffix. Slugs are claimed per chain.
• Category — market display category.
• License — for example, MIT when appropriate.
• License price — entered in the chain's displayed asset.
• Maximum supply — 0 means unlimited where the form says so.

Preserve the selected chain through every later read, purchase, management, and recovery action. Contract addresses can be reused across different networks; the address alone is not a unique Skill identity.

Access and delivery

Choose:

• Encrypted — requires acquisition and wallet verification. Files are encrypted before upload.
• Public — anyone can download without signing in.

For encrypted content, select the protection method offered by the deployment:

• Finch-managed — the browser publication and holder-download flow manages key release.
• Lit — the platform Lit provider protects the package key and releases it after holder verification.

Do not translate, reconstruct, or move protected key material between protection methods.

Information content

The current form includes:

• Public summary — required.
• Detailed description — required.
• Tags.
• Supported agents.
• Demo video URL.
• Purchase benefits.
• Version 1 release notes.

Instruction content

Provide prerequisites, usage steps, and known limitations. Write each item so a buyer can verify whether they have completed it.

Optional HTML content

Information, Instruction, Benchmark, and Showcase each accept one static HTML override plus up to 50 flat assets. Reference assets with ./assets/filename. Scripts and remote resources are blocked.

• Information HTML replaces the structured Information content, while listing identity and supported Agents remain visible.
• Instruction HTML replaces the structured Instruction view; structured fields remain saved for restoration.
• Benchmark and Showcase currently rely on custom HTML because there is no structured editor for those tabs.

Media and source

• Cover image — PNG, JPEG, WebP, or GIF, up to 5 MB in the current form.
• Source — choose Files or Folder and select only the intended package content.

Publish through V3

The browser describes the V3 flow in three stages:

1. Upload safely — protected Skills are encrypted in the browser before upload.
2. Confirm publication — the wallet creates the Skill and enables protected buyer access where required.
3. Recover if interrupted — resume the active publication without rebroadcasting confirmed work, or dismiss the presentation without deleting its transaction record.

Review the exact chain, owner wallet, package fingerprint, price, supply, content mode, and transaction before signing.

For the Agent-client flow, Remote MCP prepares the publication and returns one exact CLI action. The CLI owns deterministic packaging, filtering, optional encryption, upload, key custody, and chain submission. Do not replace a local package with an arbitrary GitHub or IPFS URL.

Verify publication

After confirmation:

1. Open the Skill from Listing Center.
2. Confirm name, chain, version, content mode, price, supply, and owner.
3. Review all published tabs and assets.
4. Verify the file fingerprints.
5. Test public download or protected holder delivery using the intended account.
6. Confirm the market card appears after projection has caught up.

Chain state is authoritative. Search indexing may lag after a confirmed transaction.

Manage a Skill

Open Listing Center → Products → Skills → Manage. The current management page exposes:

• display category;
• unit price;
• maximum supply;
• new version files.

Ownership authorizes changes. Connecting a different wallet will fail even if the browser is signed in to another Finch identity.

Public presentation and cover updates can also be prepared through Finch market operations. Re-read the current Manage state before changing anything, complete one returned action at a time, and verify the chain and presentation after each confirmation.

Publish a new version

1. Read the current Skill, version, content mode, and package fingerprint.
2. Prepare a clean file or folder source.
3. Write release notes that explain behavior and compatibility changes.
4. Prepare the new version against the exact chain identity.
5. Review and sign the returned action once.
6. Verify the new version and delivery package before announcing it.

Recover an interrupted action

Keep Finch's protected local recovery record until every transaction stage settles. Resume the original publication with the recovery fingerprint shown by Finch. Never delete the record, rebroadcast a completed stage, or create a replacement Skill simply because a response was delayed.

Publisher checklist

• Package contains only intended files.
• No secret or private data is included.
• License is accurate.
• Summary, details, examples, and limitations match the package.
• Content mode matches buyer expectations.
• Price and maximum supply are correct for the selected chain.
• Cover and optional HTML render without remote scripts.
• Package fingerprint is recorded.
• Buyer delivery was tested safely.