Prepare a workflow or AI skill

Open Library and choose Add to library. The first screen asks what you are saving. A workflow export: choose the JSON file n8n or Make gave you; the draft opens with the file in place and the title read from the export. An AI skill: import a SKILL.md, whose name and description fill the title and summary, or write it here. From a client workflow: pick a workflow on the record; the draft keeps a private link to it and copies no client information.

On a completed request with workspace editing access, Worth keeping? offers Save this to your library. That opens Start from this delivery, which lists the details already recorded on the workflow and your verification note, with nothing ticked, and shows the draft filling in as you tick. Rows that usually name a client are marked. The client, their request and their approval are never offered.

The item is one page. The name, version, what it does and the files or instructions come first; Who it is for and what it needs, Setup and an example result and Checks, limitations and support are named sections that say what is still missing. Preview shows what a reader sees and says whether it is your saved version or unsaved edits. After you save, Use for client work and Share by private link sit under the heading; the private Source workflow and Used in client work are under About this item.

Open Library, then Catalog. It holds workflows and AI skills from public repositories, license-checked, each with its author, license and a link to the source. Search it, Preview an item, and choose Save to library (or Add to my library on the item page) for a private copy you can edit and use for client work.

The copy is taken as published; AgentHub has not verified it, so review it before a client sees it. It is someone else's work under their license, so it cannot be listed for sale.

From your library or saved package, select Use for client work. Choose a managed client or, as an owner or admin, enter a new client, name the workflow, select the platform, and describe what the client needs. Select Create client request. AgentHub creates a draft workflow and a request awaiting review. The record includes the package name, version and saved revision; instructions and files remain in your library. Review and export those files separately for your chosen tools. A workspace trial or active plan and an operator role are required.

The Reusable starting point card keeps the original package reference. Later package edits do not update the client workflow. Opening your current draft may show a newer version. Scope approval, implementation and checks remain separate steps.

Your library marks each package that has Started client work with a count, so you can see which packages you actually reuse. The count records the requests you started from that package. It is not a record that the client approved the result, paid, or that delivery succeeded, and client work in a workspace you can no longer read is not counted. The package itself shows the detail: Used in client work, under the steps in the editor, lists the client work you started from it, the saved version each one started from, and whether you have saved edits since. It is private to you and stays out of previews, exports and anything a buyer sees. Client work in a workspace you can no longer read is omitted by workspace access controls.

On a purchase that is ready to use, select Use this with a client, then Use for client work. Choose a managed client or, as an owner or admin, enter a new one, name the workflow, select the platform, and describe what the client needs. AgentHub creates a draft workflow and a request awaiting review, keeping the offer name and the version you bought. The purchased files stay in your purchase; download and set them up in your own tools. Nothing is installed, run, approved, verified or sent for you.

Access is checked again when you submit, not when the page loads. A refund, dispute, payment hold, revoked access or a withdrawn offer stops a new start. Client work you already started stays exactly as it is: the request, the scope you approved and the checks you recorded are your record of your own work.

Starting client work needs a workspace with operator access. Without one, the purchase is unchanged and stays available. On the change record, Purchased starting point shows the offer name and version to everyone who can read that client record. Which purchase it came from, and the fact that you bought it, stay private to you. The seller is not told which clients you use their offer with.

Open Library, then Selling. Under Your profile, save your name, relevant experience, and optional website. Back in the package, open its Your profile section and select Add my profile to add a copy of the profile to the package. Use latest profile refreshes that draft copy; Remove removes it from the draft. Existing shared copies and downloaded files retain their original details.

At the top of the item, name the package, set a version such as 1.0.0, choose AI skill or Workflow under What is it?, and say what it helps someone do. Open Who it is for and what it needs for the audience, supported tools and inputs. Select Save draft to save your progress privately.

Under Package instructions, paste your method or select Import a Markdown file to read a file under 40 KB. Add JSON, Markdown, text or CSV files with Add files (a workflow) or Add supporting files (a skill). Workflows need a JSON export. Each file must be under 64 KB, with at most 12 files and 120 KB in total. Then fill Setup and an example result and Checks, limitations and support; each section says what is still missing. Use fictional examples and remove credentials or confidential client material.

Open Pricing and selling and choose Prepare a paid listing. Enter a One-time price (USD), or leave it blank while deciding. The estimate shows AgentHub’s 20% commission and illustrative processing fees separately. Actual processing fees are deducted from creator proceeds; AgentHub pays its own platform overhead. Save draft stores pricing privately. This does not publish a listing, enable purchases, or change free share links. Selling is not open yet.

Select Preview to review See the expected result, requirements, and Your first use. The full skill instructions are in the export, not the listing. Open Export a copy: it lists anything still missing (select an item to go to its field), then confirm your distribution review and select Export package ZIP for workflows or packages with supporting files, or Export SKILL.md for an AI skill without files. This exports the current editor contents. It does not save edits or publish anything.

Not open yet. The marketplace is not open, so this step is not available in your workspace. Open Library → Selling → Payout setup after saving your creator profile. Payout setup is currently available only in configured test environments. When enabled, first choose where you or your business is legally based. The test flow supports United States payout accounts only; choosing Outside the United States does not create a US account or restrict your general use of AgentHub. Stripe collects business and bank details directly. If a Stripe link expires, return to Payout setup, confirm your country and continue to reopen the same account. Returning to AgentHub checks the current status; it does not enable marketplace selling or live payouts.

The payout screen explains the 20% platform fee, the processing fee deducted from creator proceeds, and the 14-full-day hold after verified successful payment. Unresolved refund or dispute cases can extend the hold. Release also requires available funds and a ready Stripe account. The release date is eligibility for transfer to your Stripe balance, not a bank-arrival promise.

Open Pricing and selling in the item, choose Prepare a paid listing, set the price and save. Then select Review this version for sale. The page shows what a buyer receives, the price and fees, and the support included. Select See the buyer’s view to check the saved title, sample, requirements, creator details, price and support without the paid instruction body. Open The complete README.md (workflow) or The complete SKILL.md (AI skill) and each file under Review all included files, confirm permission to distribute the package, then select Prepare this version. The prepared version stays on the same page, with the date it was prepared; draft edits do not change it. Earlier versions are listed under Other prepared versions. This prepares a private version; marketplace publication, checkout and payouts are not enabled.

Not open yet. The marketplace is not open, so this step is not available in your workspace. In environments with listing review enabled, Automated checks appears on the same page once a version is prepared. Read the complete file, all included files and the Standard client-use license, then confirm your rights and privacy review. Select Submit for checks. The license allows one buyer or business to use and modify the skill for its own work and client projects, including a configured client handover. Standalone resale and distribution are prohibited. Future updates are included only when the offer states that.

The status becomes Checks pending. You can Withdraw submission while checks are pending or after checks pass. Changes needed explains flagged findings: address them in your draft, prepare a new version, and submit that version. Not yet supported means AgentHub cannot validate a capability yet. It is not a finding of malware. Keep that version private; do not remove necessary functionality just to pass checks. If both findings and unsupported capabilities are reported, both must be resolved before publication. Checks passed does not publish the skill or enable purchases. If a scan cannot finish, choose Retry checks; a scanner error does not require file edits. Unsupported formats remain private until the automated checks support them. Automated checks do not guarantee safety, functionality, or suitability for a buyer’s setup. A package may send data to external services or act using permissions the buyer grants. Buyers should review destinations and permissions and test with sample data before use.

Not open yet. The marketplace is not open, so this step is not available in your workspace. After the exact version passes automated checks, open your preserved version, review the public offer and price, confirm the publication statement, and select Publish this version. View public offer opens the listing without exposing the paid instruction body.

Use Unlist this version to hide the offer from new buyers. Eligible existing purchases retain access. An operator removal also blocks downloads and cannot be reversed by the creator. Publication history records the actions and any removal reason. Publishing an offer does not enable checkout by itself.

Save the complete draft, then select Share by private link. The page shows what the link shows; open The complete README.md (workflow) or The complete SKILL.md (AI skill) and each file under Review all included files, confirm permission to share, and select Create private link. Copy the link immediately. Anyone with it can preview and download without an account. Later edits do not change that copy.

Under Links, select Revoke link. Confirm the action. This stops future access and downloads but cannot recall files already downloaded. A lost link cannot be recovered; revoke it and create another.