Skip to main content
Agent Creator turns a plain-language specialist description into a reusable agent package. Describe the specialist you want, and it drafts the full package: a title, a Soul, and a set of slash-command skills. The result lands in your Marketplace under User Made, reusable in any team or solo workspace.

​
Create a specialist

1

Open Agent Creator

From the Marketplace’s Add flow, or from the solo agent path (“Describe a new specialist and generate a reusable skillset.”).
2

Describe the agent

Be concrete about what it reviews, produces, and cares about. The placeholder gives the shape:
“A launch operations specialist that writes release checklists, audits blockers, prepares launch comms, and coordinates post-launch monitoring.”
The custom agent modal with a description field

Describe the specialist you want

3

Generate

Click Generate Agent (in some flows Build Skillset). Status messages stream while Agent Creator works: “Designing the specialist…”, “Writing the command set…”, “Building the reusable skill package…”.
4

Review the draft

You get the package title, description, package ID, and a card per generated skill with its slash command and description.
A generated Launch Readiness Reviewer package with its skill cards and Save to Marketplace button

A generated draft, ready to revise or save

5

Revise if needed

Use the “Want changes before saving?” box to redirect, for example: “Make this more tactical, add a quality review command, and remove anything about analytics.” Click Revise Draft. Repeat until satisfied.
6

Save

Save to Marketplace publishes the package under User Made. From there, add it to teams or solo agents like any specialization.

​
Edit a package later

Open the package in the Marketplace and click Edit. Describe the change (“What should Agent Creator change?”) and Apply Change.
Saved Soul and skill edits cannot be undone automatically. Keep a copy of anything you might want back.

​
Writing good descriptions

  • Name the role, the artifacts it works on, and the actions it takes (“reviews pitch decks, pressure-tests the narrative, creates slide guidance”).
  • Mention the workflows you expect; each tends to become a command.
  • Leave out tooling and model choices: those are configured on the agent afterward, not baked into the package.