Three things on this page. Watch the two-minute video tutorials. Read the deep-dive on how the marketplace works and what you can upload. Skim the FAQ when something specific comes up.
Two short HeyGen videos that walk you through what AI Forge is and how to upload your first plugin. Both open in a new tab.
What AI Forge is, why it exists, and how to start using it across the portfolio.
Watch on HeyGenSign in, pick your folder, fill in the details, hit submit. The scrubber strips credentials in your browser before anything uploads.
Watch on HeyGenTwo short walkthroughs. Each one shows the full flow from start to finish. Pick the one that matches what you want to do.
Every automation lives in one of three tiers. Tier determines who maintains it, how trusted it is, and how much polish you can expect.
Issued directly by Kyle's team. Brand-aligned, on an SLA, kept current as APIs change. Mandatory or near-mandatory across the portfolio. You can't submit to Core directly. Plugins get promoted in when they prove themselves.
Started as a Community submission, got cleaned up, documented, and tested by the reviewer. Maintained on an SLA. The Manos quality benchmark.
What you submit lands here. Scrubbed for tokens and tenant IDs, reviewed for safety, then published. No central maintenance promise. Each plugin ships with a diagnostic prompt so your local Claude can walk you through fixes if something breaks.
AI Forge accepts any automation type. Pick what you built it in on the submit page, and the upload zone matches automatically — folder for Claude plugins and scripts, single file for everything else. Below: exactly how to export from each tool.
Skills, commands, MCPs, custom agents, anything built for Claude Code or Claude Cowork. These genuinely need a folder because they ship with a plugin.json manifest plus the skill/command/agent files alongside it.
Installs one-click from the Cowork Directory once it lands in the catalogue. No download needed.
Cloud flows you've built at flow.microsoft.com. AI Forge stores the exported package; the recipient imports it into their own environment and rebinds connections.
People download the .zip from the catalogue, then in Power Automate go to My flows → Import → Package, upload the .zip, and rebind connections to their own accounts.
Different product from Cloud flows. Lives on Windows desktops, exports as .ppd files.
Recipient downloads the .ppd, opens Power Automate Desktop, picks File → Open from file.
Works the same on self-hosted n8n and n8n.io cloud. Exports as a single JSON file.
Recipient downloads the .json, in n8n picks Workflows → Add workflow → Import from file.
Scenarios export as a blueprint JSON file.
Recipient downloads the .json, in Make.com creates a new scenario via Create a new scenario → Import Blueprint.
Python, PowerShell, Node, Bash. Anything that runs from a terminal or scheduled job.
Recipient clones or downloads the folder, installs dependencies per the README, runs the script.
Zapier has no native file export. The closest equivalent is a Share-as-Template URL, so a Zapier submission is really documentation plus a share link.
Recipient clicks the share URL in the README, which opens Zapier with the template ready to install.
Custom GPTs can't be downloaded. Submission is documentation plus a share link, like Zapier.
Recipient clicks the share URL to open the GPT in their own ChatGPT, no setup needed.
Catch-all for VBA macros, Excel templates, Power BI files, Bicep templates, n8n alternatives, anything else useful.
Recipient follows the README. The catalogue shows the tool name you typed so people know what they're looking at.
The complete flow, end to end. Skip what you already know.
Use whatever tool fits the job. Claude Code, Power Automate, n8n, a Python script. The marketplace doesn't care what it's built in, only that it solves a real problem.
One folder per automation. If it's a Claude plugin, follow the plugin folder structure (manifest plus code). If it's a Power Automate flow, export the .zip or the solution into the folder. If it's a script, put the script plus a short README inside. Anything sensitive (API keys, tenant IDs, emails) goes in but will be stripped in the next step.
Sign in, pick the folder, fill in the metadata. Name, slug, what it does in one sentence, the diagnostic prompt for community plugins, the type (Claude / Power Automate / n8n / etc).
Before anything uploads, the scrubber strips OAuth tokens, API keys, emails, tenant IDs, and other credentials, replacing them with named placeholders like {{CONFIG_OUTLOOK_TENANT_ID}}. The reviewer sees the scan report. Your original files never leave your machine, only the cleaned copy.
The cleaned folder commits to the ingest GitHub repo and lands in the reviewer's queue. You get a "Submitted" confirmation.
The reviewer reads the scan report, sandbox-tests the install, edits the manifest if needed, and promotes it to the curated repo. Or asks you a question via Teams. Or declines with a reason.
Once promoted, your automation shows up on the homepage catalogue. Anyone in any of the seven companies can install it (Claude plugins) or download it (everything else) from inside Cowork. Every install ticks your contributor count. The whole portfolio benefits.
"Daily Inbox Summariser" is good. "Kyle inbox v3 final final" is not. The name is what people search and skim. Make it tell them what it does.
The short description has to fit on a catalogue card. Lead with the verb. Mention the inputs and outputs.
Categories are the main way people filter. Internal admin is not the same as Operations. Lead Gen is not Marketing. Pick the one that matches what the automation actually does.
Two to five tags. Lowercase, hyphenated. Tools it talks to, the platform, the workflow stage. e.g. outlook, m365, daily, triage.
Pretend you're handing the plugin off to a Claude that's never seen it. State what the plugin does, what services it depends on, and the three most likely failure modes. Under 400 words.
The scrubber will create placeholders for everything it catches. Add anything it missed manually. The customizer skill uses these slot names when prompting installers.