Meta Gobii

Meta Gobii lets you ask one Gobii to help set up and manage other Gobiis. Instead of configuring every Gobii by hand, you can describe the business outcome you want, review the proposed changes, and approve the work that should happen.

Use Meta Gobii when you want help turning a goal into one Gobii, a coordinated team of Gobiis, or a cleaner setup for Gobiis you already have.

Meta Gobii should turn setup and management requests into visible proposals before it creates or changes other Gobiis.

What Meta Gobii Can Help With

Meta Gobii can help you:

• Create a new Gobii from a business goal.
• Create a team of Gobiis with different responsibilities.
• Connect Gobiis so they can coordinate with each other.
• Brief Gobiis with roles, responsibilities, and next steps.
• Review existing Gobiis, including their names, standing instructions, activity state, resource settings, contact setup, files, and recent work history when available.
• Update names, responsibilities, standing instructions, active or paused state, resource settings, intelligence level, daily credit limits, contact rules, and preferred contact routes where those controls are available.
• Archive Gobiis that are no longer needed.
• Reorganize responsibilities across an existing set of Gobiis.
• Add or review small files for a Gobii when file support is available.
• Review, add, remove, approve, or reject contact access where contact controls are available.
• Help shape ongoing work through clear standing instructions and timing hints.

Meta Gobii is best for setup and management work. It does not replace the Gobiis doing the business work. For example, Meta Gobii can create and brief a sales research team; the sales research Gobiis then do the research.

How To Ask

Start with the result you want. Meta Gobii can fill in a practical structure, but better context usually produces a better proposal.

Useful details include:

• The business area: recruiting, sales, research, customer support, marketing, operations, finance, or another function.
• The outcome: create a demo team, clean up existing Gobiis, set up a weekly customer report, brief one Gobii, archive old Gobiis, or connect two Gobiis.
• Constraints: one-time setup, no recurring check-ins, keep credit use low, use a higher intelligence level for complex research, pause anything old, or ask before changing contacts.
• Inputs: job roles, target accounts, research topics, support queues, campaign themes, vendor names, or files you want a Gobii to use.

Example:

Create a demo recruiting team for our customer success hiring push. I want one Gobii to source candidates, one to screen resumes, and one to prepare interview briefs. This is just setup for now, with no recurring check-ins.

Expected outcome: Meta Gobii should propose the Gobiis, their responsibilities, and any links or briefing messages needed. It should not add ongoing schedules because the request is setup-only.

Creating One Gobii

Ask Meta Gobii for a single Gobii when one clear role is enough.

Example prompts:

• "Create a Gobii that researches target accounts before sales calls. Keep it lightweight and ask me before sending anything externally."
• "Set up one Gobii to summarize customer feedback from files I provide."
• "Make a Gobii for vendor research. It should compare pricing, risks, and renewal timing."

Expected outcome: Meta Gobii should propose the name, role, standing instructions, and any settings that matter. After you approve, it can create the Gobii and brief it with the starting context.

Creating Teams Of Gobiis

Teams are useful when a business process has multiple roles. Meta Gobii can split the work into focused Gobiis, connect the ones that need to coordinate, and brief each one with its responsibilities.

Recruiting

Prompt:

Create a recruiting team for a support manager role. I need one Gobii to find candidates, one to screen resumes, and one to prepare interview packets. Do not set up recurring outreach yet.

Expected outcome: A proposed team with separate sourcing, screening, and interview-briefing responsibilities. Links may be proposed where coordination helps. No recurring schedule should be added unless you ask for one.

Sales

Prompt:

Build a sales prep team for the Northeast territory. One Gobii should research target accounts, one should clean up account notes, and one should draft call prep briefs.

Expected outcome: A sales-focused team with clear handoffs. Meta Gobii may propose links so the account researcher and call prep Gobii can coordinate, then ask for approval before creating or connecting anything.

Research

Prompt:

Set up a research team for the electric vehicle charging market. I want one Gobii for competitors, one for regulations, and one for customer segments.

Expected outcome: A research team with separate charters for each topic. If you did not ask for recurring monitoring, the initial setup should stay one-time.

Customer Operations

Prompt:

Create a customer ops team to help us organize support escalations, summarize customer themes, and prepare weekly leadership updates.

Expected outcome: Meta Gobii may propose escalation triage, theme analysis, and leadership update Gobiis. Because "weekly leadership updates" is explicit timing, the proposal should make that recurring update visible in the approval plan before any schedule-related behavior is added.

Marketing And Content

Prompt:

Create a content team for our product launch. One Gobii should collect customer proof points, one should draft post ideas, and one should review the launch calendar.

Expected outcome: A launch-focused team with responsibilities and briefings. Unless you ask for scheduled content ideas or ongoing calendar checks, the team should be set up without a new recurring cadence.

Business Operations

Prompt:

Create an operations team for vendor renewals. I need help tracking vendor details, preparing renewal questions, and keeping leadership briefed monthly.

Expected outcome: Meta Gobii can propose vendor tracking, renewal prep, and leadership briefing Gobiis. Since "monthly" is explicit, any ongoing briefing schedule should be included plainly in the proposal and approval scope.

Connecting And Briefing Gobiis

Meta Gobii can connect Gobiis that need to coordinate. Connected Gobiis can share updates within the limits you approve, which is useful when one Gobii produces input another Gobii needs.

Examples:

• Connect the candidate sourcing Gobii to the resume screening Gobii.
• Link the competitor research Gobii to the weekly market brief Gobii.
• Connect the support escalation Gobii to the customer themes Gobii.

Meta Gobii can also brief Gobiis. A brief is a message that gives context, assigns next steps, or explains how a Gobii should work with another Gobii.

Example:

Brief the account research Gobii that Acme, Globex, and Northstar are the first target accounts. Tell it to prepare concise sales-call notes and avoid sending external messages.

Expected outcome: Meta Gobii should show the briefing action in the approval plan before sending the message.

Managing Existing Gobiis

Meta Gobii can help clean up and maintain the Gobiis you already have.

Common requests:

• "Show me the Gobiis related to recruiting and summarize what each one does."
• "Reorganize my sales Gobiis so account research, list cleanup, and call prep are separate responsibilities."
• "Rename the customer feedback Gobii to Customer Insights Gobii and tighten its instructions."
• "Pause the old market research Gobii."
• "Archive the stale demo Gobiis from last month."
• "Lower the daily credit limit on the content idea Gobii."
• "Use a stronger intelligence level for the legal research Gobii."
• "Connect the account notes Gobii to the call prep Gobii."
• "Remove the link between the old sourcing Gobii and the screening Gobii."

Expected outcome: Meta Gobii can inspect the relevant Gobiis, propose the changes, and ask for approval before making updates.

Charters, Prompts, And Ongoing Work

Each Gobii has standing instructions, often called its charter. The charter describes the Gobii's job, boundaries, and preferred way of working. Your prompts and approvals can update that charter over time.

Some Gobiis also do ongoing work. In normal language, you can steer ongoing behavior by saying what cadence or trigger you want:

• "This is one-time setup only."
• "No recurring check-ins."
• "Send me a weekly brief every Friday."
• "Monitor this daily and summarize changes."
• "Check the inbox every morning."
• "Stop the recurring update for this Gobii."
• "Change the monthly vendor review to the first Monday of each month."

Behind the scenes, Gobii uses the charter and timing instructions to decide what it should do over time. You do not need to write technical schedule rules. Clear business language is enough.

If you ask for a demo team, a setup-only team, a one-time research pass, a cleanup task, or a project team without ongoing timing, Meta Gobii should leave recurring work out of the initial plan. If wording like "monitor," "follow up," or "keep an eye on" could mean ongoing work but you did not give a cadence or clear recurring intent, Meta Gobii should ask a clarifying question or leave scheduling out of the proposed change.

Resources, Intelligence, And Credit Limits

Where supported by your account, Meta Gobii can help adjust how much capacity a Gobii can use.

Examples:

• "Keep this demo team on low daily credit limits."
• "Use a stronger intelligence level for the technical research Gobii."
• "Reduce the content Gobii's daily credit limit until the campaign starts."
• "Show me which Gobiis have high daily limits."

Higher intelligence can help with complex reasoning, research, or judgment-heavy work. Lower limits can be useful for demos, prototypes, and low-risk background work.

Contacts, Files, And Preferred Contact Routes

Where available, Meta Gobii can help manage how a Gobii communicates and what supporting material it can use.

Contacts:

• Review who is allowed to communicate with a Gobii.
• Add or remove approved contacts.
• Approve or reject pending contact requests.
• Set whether an approved contact can only communicate or can also help configure the Gobii.

Preferred contact routes:

• Set or clear the preferred way a Gobii should reach you when that route is available and safe for your account.

Files:

• Add small files you provide to a Gobii's workspace.
• List files already available to a Gobii.
• Brief a Gobii to use files that are already in its workspace.

Meta Gobii should ask before changing contacts, preferred contact routes, or files. It should also avoid exposing unnecessary private contact details in summaries.

Approvals And Safety Boundaries

Meta Gobii can inspect your accessible Gobiis to prepare a proposal, but important changes require your approval.

It should ask before:

• Creating a Gobii.
• Updating a Gobii's name, charter, active state, settings, resource limits, intelligence level, or ongoing work.
• Connecting or disconnecting Gobiis.
• Sending a briefing message to another Gobii.
• Uploading a file for a Gobii.
• Adding, removing, approving, or rejecting contacts.
• Setting or clearing preferred contact routes.
• Archiving a Gobii.

The approval plan should say what will change. If a proposal includes ongoing work, the timing should be visible in the approval scope. If the request did not ask for ongoing work, the approval plan should not quietly include it.

Meta Gobii can only manage Gobiis and settings it is allowed to access in your personal or organization workspace. It should not make changes outside that scope.

Practical Prompt Patterns

Use these patterns as starting points.

Create one Gobii:

Create a Gobii to research enterprise healthcare accounts before sales calls. It should prepare concise account briefs and stay internal-only unless I approve otherwise.

Create a team:

Create a three-Gobii research team for the warehouse robotics market: competitors, customer segments, and regulatory risk. This is a one-time setup with no recurring check-ins.

Connect and brief:

Connect the competitor research Gobii to the executive brief Gobii, then brief the executive brief Gobii to use competitor updates only as input for weekly leadership summaries.

Reorganize:

Review my customer ops Gobiis and propose a cleaner split of responsibilities for escalations, customer themes, and leadership updates. Do not change anything until I approve.

Adjust resources:

Show me the Gobiis with the highest daily credit limits and propose lower limits for the ones that are only used for demos.

Ongoing work:

Update the vendor renewal Gobii so it prepares a monthly renewal-risk brief for leadership. Include the timing in the approval plan before making changes.

Stop ongoing work:

Stop the recurring check-in for the old product launch Gobii, but keep the Gobii available for one-off questions.