Reuse and Deduplication in XTM One

XTM One works best when teams reuse shared building blocks instead of recreating the same setup many times.

Why this matters

Without a clear reuse model, teams quickly end up with:

• duplicate agents that do nearly the same thing
• copied prompts that drift apart
• repeated tool configuration
• confusion about which version is the real one

This page explains how to avoid that.

Reuse first

Before creating something new, check whether the platform already has:

• a shared agent
• a reusable prompt
• a reusable skill
• an existing knowledge base
• a configured MCP server or integration
• a catalog item you can add instead of rebuilding

In many environments, reuse is the right default.

When XTM One reuses the same object

The platform keeps one shared object when:

• multiple agents point to the same prompt, skill, MCP server, or knowledge base
• a company-managed or group-shared object is intentionally reused by many people
• a flow references agents that already exist

In these cases, the object stays shared. It is not silently duplicated.

When XTM One creates a copy

The platform creates or expects a copy when:

• you duplicate an agent
• you add a catalog item to your own account
• you export and re-import an object as a separate item

This is useful when you need a safe variation instead of changing the original.

When to duplicate on purpose

Create a copy when:

• you need different instructions or behavior
• you are testing a private variation
• you do not have edit rights on the shared original
• the shared object should stay stable for everyone else

Do not create a copy just because you found the shared version first.

Shared edits versus copied edits

A practical rule:

• edit the shared object when the whole team should benefit
• duplicate it when only your version should change

This is especially important for prompts, skills, and agents.

Operational deduplication

XTM One also applies deduplication ideas operationally, not only organizationally.

Examples include:

• agent memory maintenance that avoids storing the same fact again and again
• shared resources that can be attached to many agents instead of re-created
• catalog and template workflows that reduce copy-and-paste configuration work

From a user perspective, the key idea is simple: prefer a stable shared source when one already exists.

How to avoid duplicate setups

• Search before creating.
• Check whether a company-managed or shared version already exists.
• Use Duplicate only when behavior must diverge.
• Reuse prompts, skills, MCP servers, and knowledge bases whenever possible.
• Use the AI Catalog when you want a structured starting point rather than a manual rebuild.

Next step

Continue with Trust, review, and confidence, which explains how to judge AI output and understand operational trust signals in XTM One.