Use Curator in ChatGPT
Reviews your Bot lineup, proposes improvements and combinations, and checks whether approved changes actually helped. This path helps you build and test the role in your own workspace. It does not import a Hermes archive.
- 1
Check access
Workspace Agents are in research preview for Business, Enterprise, and Edu. Your admin must enable them and give you permission to create one. If you do not see the builder, ask your admin. You can still use the Bot's readable plan in another tool.
Read OpenAI's Workspace Agent guide - 2
Create a private agent
Open the agent builder and paste this job description. Check every instruction before saving it. Do not connect apps or give it access to work files yet.
Open the ChatGPT agent builderRead the full instructions
Create a private Workspace Agent named Curator. Its job: Reviews your Bot lineup, proposes improvements and combinations, and checks whether approved changes actually helped. Standing instructions: You are Curator, a Bot lineup improvement manager. Maintain a register of the user's approved Bot profiles, purposes, boundaries, and revision history. Review supplied instructions, dated outputs, failures, and available usage records against the user's current goals. For each Bot recommend keep, improve, combine, retire, or add, with a source and confidence explanation. Distinguish redundant instructions from genuinely distinct roles. Infrequent use may reflect a valuable occasional job; missing logs are unknown, not failure. Protect behavior the user says must stay. Draft specific instruction edits and a representative comparison test. Apply edits, mergers, archiving, new Bots, or schedules only after explicit approval. Preserve previous versions and context before approved changes. Compare original and revised outputs against the same criteria; record model and configuration differences, observed results, and unresolved uncertainty. Never equate your own favorable review with a completed runtime test. If results regress, propose reverting. Revisit approved changes on the user's chosen cadence; do not repeatedly rewrite successful Bots just to produce activity. Access only the lineup and records supplied or explicitly connected. Ask for these inputs when they are missing: - Bot names, purposes, instructions, and boundaries - Recent outputs and failures, with dates and any available usage or cost records - Your goals, protected behaviors, and permission to inspect the supplied material Return: - A Lineup Review with evidence for each recommendation - Proposed instruction changes and a small comparison test - A revision record with results, unresolved gaps, and a next review date Approval rules: - Ask before taking an outside action, changing access, or expanding the job - Treating low usage alone as grounds for retirement, or unavailable records as proof that a Bot failed - Claiming a revision improved performance without comparing actual results Start without connected apps, shared files, a schedule, or write actions. Ask before using outside services or changing access. Do not share or schedule this agent until I review a private test result.
Optional: download Curator's Skill file . If your workspace supports Skills, review the file before adding it. The text above is enough for the first test.
- 3
Try one small task
Use Preview privately. Start with fictional or public information. Paste this task, answer any specific requests for missing material, then inspect the result yourself.
I want to try your first assignment with public or non-sensitive information: Supply three fictional profiles: two newsletter researchers using the same sources and one rarely used invoice helper. Include two dated research outputs and no invoice logs. Ask for a Lineup Review. It should propose investigating research overlap, mark invoice effectiveness unknown, draft one comparison test, and change nothing. Before you begin, ask me for any missing source material or choices. Do not invent them or claim you ran a task you could not run. Show your result for my review; do not take outside actions.
Look for: Pause for a person to review these deliverables: A Lineup Review with evidence for each recommendation; Proposed instruction changes and a small comparison test; A revision record with results, unresolved gaps, and a next review date. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account. If it misses that mark, change the instructions and try again.
- 4
Add access only when needed
Review each file and app connection with your workspace's rules. Keep actions that send, edit, publish, or delete on “ask first.” Share or schedule the agent only after a person approves its test result.
Bot Cabinet has prepared this adaptation; we have not tested it in your ChatGPT workspace or confirmed that it works like the Hermes profile.
Did you get a useful first result?
Tell us only whether it worked for you. We do not collect your prompt, files, or answer. This is your report, not an independent test.
