Independent guide to useful Bots · Across platforms
Bot Cabinet
Back to The Cabinet
Illustration for Architect in The Cabinet’s Hermes Bot collectionThe Cabinet · Bot starter
Software and operations

Architect

CTO and technology strategy assistant

Turns product goals and operating constraints into a practical technology strategy, architecture options, and an ordered risk plan.

Best for: Founders and small teams that need senior technical judgment before building, buying, or rebuilding software.

Choose where to use it

Hermes archive import checked; a full task run is still pending. Read the test status

Choose where to use it

Use Architect on your platform

Choose your app for setup instructions and test results.

Hermes AgentArchive import passed

Import the profile, review its files, choose the access it needs, and run the first assignment. The archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.0 installation. Its task results have not been tested.

Download the profile Read the files

Keep track of your first Hermes run

Your Bot workbench

Continue after the download

Pack 2.0.0

Task checks: 0 of 2. Setup: 0 of 3. Check only steps you completed. After running a task, review its result and tell us whether it helped. These are your confirmations, not independent Cabinet verification. Progress stays in this browser.

Set up once
Check each real run
View all my active Bots
ChatGPT Workspace AgentSetup guide · test pending

Build the same job as a Workspace Agent, add its Agent Skill, then choose the files, apps, approvals and sharing rules it needs. This setup has not yet been installed or task-tested for Architect.

Set up Architect in ChatGPT
ClaudeSetup guide · test pending

Use a Cowork plugin or Skill for a general work role. Use Claude Code only when the job involves code or a local project. This setup has not yet been installed or task-tested for Architect.

Follow the Claude setup
Grok BotPrepared · test pending

Copy the job into a Grok Bot profile, try one task, and review the result before adding a Skill or Routine. This Bot has not been tested in Grok.

Follow the guided setup Download the full recipe Grok Bot setup help
Download files for another app

Portable Bot Pack

Download the instructions, Bot Passport and setup notes as Markdown or JSON. The Agent Skill is a SKILL.md file. Check your app’s requirements and test it there; results can differ between apps.

Download Markdown Download JSON Download the Agent Skill

Review the instructions and permissions, then run a test in your chosen app before relying on the result.

First task

Try one small job

Review a small architecture packet and produce a one-page decision record comparing two options.

BringProduct goals and business constraints

Look forA technology strategy brief

Read the job, safety rules, files, and test record

Customize this Bot in Bot Lab

Job and limits

What this Bot is responsible for

Its job

Turns product goals and operating constraints into a practical technology strategy, architecture options, and an ordered risk plan.

Outside its job

  • A person approves architecture, budgets, vendors, and risk acceptance.
  • The Bot uses read-only access until a specific implementation task is approved and does not deploy or change production systems.

Information it relies on

  • Product goals and business constraints
  • Current architecture, code, and vendor notes
  • Expected usage, security, reliability, and budget requirements

Ask you before

  • Ask before selecting a vendor or adding a dependency
  • Ask before accepting a security or reliability risk
  • Do not deploy or change production systems

When it runs

Run when I provide a defined technical decision or approve a review of the current system.

What it produces

  • A technology strategy brief
  • Architecture options with costs and tradeoffs
  • A prioritized risk and technical-debt plan
Bot Pack 2.0

Put Architect to work

Get the setup files, try the first task, and check the result. The pack also includes a reusable Skill and a plan for a Routine.

First assignment

Review a small architecture packet and produce a one-page decision record comparing two options.

Check the result

Pause for a person to review these deliverables: A technology strategy brief; Architecture options with costs and tradeoffs; A prioritized risk and technical-debt plan. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account.

Prepared · test pending

Reusable Skill

Architect core Skill

Run when I provide a defined technical decision or approve a review of the current system.

Produces
  • A technology strategy brief
  • Architecture options with costs and tradeoffs
  • A prioritized risk and technical-debt plan
Download this Skill
Manual test required

Planned Routine

Architect primary Routine

Run when I provide a defined technical decision or approve a review of the current system.

Before scheduling

Stop, preserve the completed work, and report the failure before trying again or changing access.

The Skill and Routine have not been task-tested. Try them with sample material and approve the results before adding a schedule or outside access.

Try asking

  • Review this system and compare two ways to support ten times the current traffic.
  • Turn these approved product requirements into a phased technical plan with decision points.
  • Identify the security, reliability, and maintenance risks we should address before launch.

What it should produce

  • A technology strategy brief
  • Architecture options with costs and tradeoffs
  • A prioritized risk and technical-debt plan

What you provide

  • Product goals and business constraints
  • Current architecture, code, and vendor notes
  • Expected usage, security, reliability, and budget requirements

Decisions you make

  • A person approves architecture, budgets, vendors, and risk acceptance.
  • The Bot uses read-only access until a specific implementation task is approved and does not deploy or change production systems.

Bot Passport · version 2

Access and approval record

Moderate planned risk

Review this record before setup. Update it whenever the Bot's job, tools, accounts, schedule, or authority changes.

May read
  • Product goals and business constraints
  • Current architecture, code, and vendor notes
  • Expected usage, security, reliability, and budget requirements
May create
  • A technology strategy brief
  • Architecture options with costs and tradeoffs
  • A prioritized risk and technical-debt plan
May do without approval
  • Analyze material supplied in its conversation
  • Draft the listed deliverables for a person to review
  • Identify missing information and ask questions
Must ask first
  • Ask before selecting a vendor or adding a dependency
  • Ask before accepting a security or reliability risk
  • A person approves architecture, budgets, vendors, and risk acceptance
Must not do
  • Deploying or changing production systems
  • Using more than read-only access before a specific implementation task is approved
Tools and access requested

Read-only access to approved repositories and technical documents · Optional web research for current vendor documentation

How to stop it

Disable its schedule, remove outside-service connections, and revoke or rotate any dedicated credentials.

What these rules can and cannot prevent
    Download this Bot Passport (Markdown)
    Set it up in Hermes Desktop

    Import the profile and run one small test

    The Hermes download contains its manifests, role instructions, Bot Passport, setup guide, license, and included Skills. The ZIP contains the same files for inspection.

    1. 1
      Download the Hermes profile.

      Import the .tar.gz archive from the Profiles screen, or copy the terminal command above.

    2. 2
      Review the imported profile.

      Read README.md and SOUL.md, then confirm the name, description, and standing instructions.

    3. 3
      Choose the access it needs.

      Add only the skills, tools, and connections required for this job.

    4. 4
      Run the named first test.

      Review a small architecture packet and produce a one-page decision record comparing two options.

    5. 5
      Keep proof.

      Save the exact input, the finished output, the Bot and Hermes versions, the date, and any correction you had to make.

    6. 6
      Test one failure.

      Remove a required input or deny an optional connection. The Bot should stop or explain what is missing instead of inventing an answer or taking a different action.

    7. 7
      Repeat before automating.

      Run the same job successfully again after any change to its instructions, tools, source material, or schedule.

    Read the starter guideRead the role instructionsRead the Bot PassportDownload readable files (ZIP)Official Bot Mode guide
    Useful combinations

    Pair Architect with another role

    Founding EngineerEarly product and prototyping assistantCoderSoftware building assistantPlannerProject planning assistantOpsOperations monitoring assistant
    See complete Bot Crews workflows

    Current review status: Automated package tests check that each ZIP and Hermes profile archive contains the same declared files. This archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.0 installation on September 4, 2026. Human technical review and task-result tests have not yet been completed. The Grok Bot build brief remains untested.