Choose where to use your Bot
The Bot Pack contains the Bot's instructions: its job, the information it may use, the answer or file it should make, the actions that need your approval, and a first task to try.
To use the Bot in ChatGPT or Claude, create an agent or skill in that app, copy its instructions, connect the required accounts, and set its approval controls. Then try the first task. The Hermes profile is an install file for Hermes.
- Use an ongoing agent when the job needs its own files, memory, connections, schedule or a name your team can use.
- Use a skill when your existing assistant only needs a repeatable method.
- Use a one-time task when the work does not need to continue after the result is delivered.
- Use several agents only when separate access, independent review or a real handoff makes the result better or safer.
Start with the Portable Bot Pack
Download the Markdown Bot Pack and Agent Skill from the Bot's page. Read them before uploading anything. Keep the job, inputs, output, stop rules and approval points. Replace the platform section with the setup for the service you choose.
Connections never move automatically. Add only the calendar, files, messages or other accounts the job truly needs. If a service cannot enforce one of the Bot's approval rules, keep that action outside the Bot and do it yourself.
ChatGPT Business, Enterprise or Edu: build a Workspace Agent
For a continuing work role, use a ChatGPT Workspace Agent. Give it the Bot Pack's job and limits, add the Agent Skill, then add only the files and apps needed for that job. Choose whether each connection belongs to the person running the agent or to a shared service account.
Leave write actions on Ask by default. Add narrower action limits for sending, editing, posting or deleting. Run the Bot Pack's first test privately before sharing the agent or adding a schedule. ChatGPT Work can handle a long one-time task, but a reusable company role belongs in a Workspace Agent or Skill.
- Name the agent and paste the job instructions from the Bot Pack.
- Upload the Agent Skill and only the approved reference files.
- Connect the minimum apps required for the job.
- Set write approvals and action limits before the first run.
- Run the named first test, correct the setup, then decide who may use it.
- Add a schedule only after the same job succeeds more than once.
Claude: use a Cowork plugin or skill
For a general work role, Cowork is the better fit. A Claude plugin can bundle the Bot's skills, connections and optional helper agents. Start with one skill and the fewest connections. Use Manual approval while you test. A schedule can come later if the job truly needs to run on its own.
Claude Code is the right home only when the Bot's job lives in a codebase or local project folder. A release checker, documentation maintainer or code reviewer may fit there. A general Chief of Staff usually belongs in Cowork, not Claude Code. Claude Artifacts can be useful outputs, but an Artifact is not the standing agent itself.
- Create or customize a plugin from the Bot Pack and Agent Skill.
- Add project or folder instructions only when the job belongs to that project.
- Connect the minimum services and start in Manual approval mode.
- Run the named first test and save the complete output.
- Share the plugin or add a schedule only after its permissions and result have been checked.
Example: Chief of Staff
Chief of Staff turns approved meeting notes and work records into a short brief with decisions, owners, deadlines, conflicts and questions. It may prepare drafts, but a person decides what is sent, scheduled or changed.
In ChatGPT, make it a private Workspace Agent with the Chief of Staff Skill and approved calendar, file and messaging connections. In Claude, make it a Cowork plugin with the same Skill and connections. In either service, begin with the fictional meeting transcript named in the Bot Pack. Do not connect a live inbox or calendar until the result is useful and the approval rules work.
FIRST TEST
Give the agent the sample meeting transcript from the Chief of Staff Bot Pack.
Ask for: decisions, owners, deadlines, conflicts, unanswered questions and draft follow-ups.
Pass when every claim points back to the transcript, no owner or deadline is invented,
and no message, event or task is created without approval.Other platforms: use the same checklist
For Microsoft, Google or a new agent service, first find the platform's equivalent of standing instructions, reusable skills, connected tools, private files, approvals, schedules and sharing. If one of those controls is missing, simplify the job or keep that step with a person.
Check the app's current official instructions before setting up the Bot. Reuse the Bot's job instructions, then follow the app's own steps for accounts, tools and approvals.
- Where do you save the Bot's job instructions and limits?
- How are tools and accounts connected, and whose account is used?
- Which actions can require approval or be blocked entirely?
- Where are files and continuing memory stored?
- Can the job be shared or scheduled, and who may change it?
- How will you save the exact test input, output, version and correction?