Manage organization talents

Custom Talents add rules specific to your organization alongside Grace Talents: regulatory constraints, internal conventions, or practices that should not be published in the shared catalog.

Published talents are visible in the Catalog to every member of the active organization. Their content remains limited to that organization and its projects. Only owners and admins can create or manage them through Catalog → Create an organization talent or Organization → Organization talents → New talent.

Choose how the talent is applied

When migrating to these two modes, existing Per task talents become optional. No project selects them automatically: explicitly choose the projects that need them.

Prepare a draft with your AI agent

An owner or admin can explicitly ask their AI agent to create an organization talent. The grace_create_organization_talent tool appears only after an authorized OAuth connection to the current project; it is not available to members or project API keys.

The AI agent then helps you produce one coherent rule:

1. together, you define the expected outcome, scope, prohibitions, exceptions, and observable verification;
2. it proposes Optional for projects by default, reserving the required mode for explicitly universal rules;
3. it shows you the exact name, instruction, mode, and triggers;
4. it waits for your explicit approval of all of them before saving.

The call saves only a draft in the organization that owns the connected project. It does not let you choose another organization and never activates the talent. Then open Organization → Organization talents to review and publish it.

Create and activate a talent

The workflow clearly separates saving the draft from activating it:

1. In the Catalog, choose Create an organization talent; or open Organization → Organization talents, then New talent.
2. At Write, give it a clear name, write an instruction the AI agent can apply directly, and choose how it will be applied.
3. Choose Save draft and continue. The talent is saved but is not yet passed to new tasks.
4. At Review and activate, check the instruction and its scope.
5. For Optional for projects, review the keywords suggested by Grace, correct them if needed, then confirm the list. A keyword can contain up to 80 characters.
6. For Required for all projects, explicitly confirm that the talent should automatically apply to all the organization's projects.
7. Choose Activate talent.

A confirmation then shows that the active talent appears in the organization's catalog with its published version and application mode. A draft does not appear in the catalog and is never passed to AI agents.

View a published talent

From the Catalog, select the Your organization card, as you would for a Grace Talent. The page shows its purpose, version, and application mode. It does not expose the execution instruction or its triggers: Grace passes them only to authorized AI agents on relevant projects. Owners and admins can find the full content under Organization → Organization talents, along with management actions reserved for them.

Select a talent in a project

Open the Catalog from the relevant project:

• an optional talent can be checked and installed like a Grace Talent;
• a required talent is already checked and locked because it applies without project configuration;
• the Your organization card shows the published version and the mode governing its selection.

Search and filter

The page combines search and the status filter in a single bar. The four statuses All, Active, Drafts, and Disabled show their respective counts. The search and selected status remain in the URL, so the view is preserved when returning or sharing it within the organization.

Edit an active talent

Choose Manage for the talent. The screen distinguishes these actions:

• Save changes creates a working version; the active version remains unchanged.
• Publish changes replaces the active version for new tasks.
• Activate talent makes a draft available.
• Reactivate talent makes a disabled talent available again.

Only one primary action is offered at each stage. If another administrator has edited the talent in the meantime, Grace preserves your input and shows a comparison with the latest saved version. You can replace your input or retry with your changes.

Deactivate or reactivate

Deactivation is isolated in a danger zone and requires explicit confirmation:

• Deactivate talent immediately removes it from new resolutions without deleting its history.
• Reactivate talent republishes the approved version and makes it available again.
• Historical tasks, resolutions, and validation reports retain the exact version they used.

Archive a disabled talent

Under Disabled, open Manage, then Archive talent. Finish or discard changes in progress before archiving.

The talent disappears from current lists and appears under Archived. Its versions and task history are retained. Under Archived → Manage, Restore talent returns it to Disabled: it will not be used until you reactivate it.

An active talent must be deactivated first. Archiving does not delete any data and remains restricted to the organization's owners and administrators.

What the agent receives

grace_prepare_task returns a resolutionId. This reference locks in the Grace Talents served and the exact version of each Custom Talent passed for the task. The agent then passes it to grace_review and records the verdicts for reviewable Grace Talent rules and each Custom Talent using grace_record_validation.

An API key used by an automation needs separate permissions:

• validate to read the review plan;
• record_validation only if it needs to record review verdicts.

See Call Grace from a hook for examples and the rules of least privilege.