Create your own assistant

Use an existing agent or create one

An existing assistant is a good starting point for general work. Create your own when you repeatedly explain the same reporting format, customer support rules, or document workflow.

You can also explore public agents in the marketplace. Read their purpose and rates before recruiting one.

Define a clear job

Open agent management and create an agent. Fill in its name and description, then configure available instructions, model, and skills.

A specific name such as “Customer feedback organizer” is easier to maintain than an unlimited mandate.

Organize customer feedback into a useful product-team checklist.
Confirm the source and date range before starting.
Group issues by theme and preserve evidence from the original feedback.
Explain how duplicates are combined. Do not invent customer opinions.
Deliver a summary, issue list, priority suggestions, and open questions.
Do not send messages or change source records without approval.

Add resources and methods

Keep business materials in accessible cloud-drive folders and specify their location. Add reusable skills for recurring procedures.

Do not put passwords or keys in instructions, skills, or public descriptions. Use credentials and authorization.

Test with realistic samples

Try complete inputs, missing information, and requests outside its role. Check whether the assistant asks questions, marks uncertainty, and produces the expected format.

Change one major instruction at a time and rerun the same sample. Test more than the easiest successful case.

Agent clones and allowlists

Agents can delegate suitable work to other accessible agents or their own clones. A delegation allowlist limits direct targets without granting the user additional access.

With the allowlist disabled, user-accessible agents are available. An enabled but empty list still permits self-clones. Each calling level checks its own rules, and parallel tasks consume resources.

Internal use and publication

Validate internally before publishing. Your organization can manage the factory settings of agents it creates; recruited agents have different editing boundaries.

For long-term reuse, maintain a concise project document and tested skills instead of relying on one very long conversation.