Partner Guide
How to submit your Claude Code Agentic Workflow
An agentic workflow or automation built to run in Claude Code.
You deliver
An agentic workflow that runs inside Claude Code.
Accepted
A .zip (either just a .claude/ folder, or a whole extractable project repo) or a link to a public GitHub repo. Any file type is accepted for this type, so a repo archive is fine.
How to package
Two shapes work. (1) Just the workflow: zip a .claude/ directory at the archive root: commands/*.md (one per slash command, with frontmatter description + argument-hint), optional hooks/*.sh (executable), optional settings.json with a conservative permissions allow/deny list, and a top-level README.md; the buyer unzips it at their repo root. (2) A whole project the agent operates on: zip the entire repo with the .claude/ folder inside it, but strip .git/, node_modules/ and build output first and include an .env.example (placeholders only). Either way, keep the agent config as plain Markdown/JSON so it can be read before it is run.
Pricing
Base price, plus optional installation price and a yearly maintenance package.
Setup guide
Required. Prerequisites and accounts needed, step-by-step install/import, required credentials or environment variables (describe them, never paste real secrets), a quick test to confirm it works, and common errors with fixes. Cover where to drop the .claude/ folder, which commands to run in what order, what each hook does and how to disable it, and every permission the settings.json grants. The buyer sees it after purchase, next to the download.
The .claude/ folder layout
Package it as a single .zip whose root is a .claude/ folder the buyer drops into their repo:
your-workflow.zip
└── .claude/
├── commands/
│ ├── plan.md # frontmatter: description, argument-hint
│ ├── build.md
│ └── ship.md
├── hooks/
│ ├── format-changed.sh # chmod +x; must never hard-fail
│ └── pre-commit-tests.sh
├── settings.json # conservative permissions allow/deny
└── README.md # what it is, install, the command order- Every command file needs YAML frontmatter with a
description; add anargument-hintif it takes input. - Keep
settings.jsonpermissions tight and readable: deny force-push, hard reset,rm -rf, reading.env. - Ship only plain Markdown and JSON so a buyer can read the whole thing before running it.
- The setup guide (after purchase) says where the folder goes, which commands to run in what order, what each hook does and how to turn it off, and every permission granted.