Skill Pages in XTM One

This page complements Skills in XTM One.

That guide explains what a skill is. This page explains what the user sees on the skill pages and how the main UX works.

In the left navigation, this area appears as Skills.

The list page title is also Skills.

Skills list page

The list page is a reusable behavior library.

Use this page to:

search skills by name, description, or known purpose when you remember what a skill does but not its exact title
filter by visibility to separate private skills, shared skills, and company-managed skills in larger workspaces
filter by tags to narrow the list to one topic, team, workflow, or use case
check whether a skill is enabled, which tells you whether the skill is currently injected into agents that use it
understand whether the skill comes from a URL or direct content, which changes how it should be maintained later
compare existing skills before creating a new one, so you do not duplicate something that is already shared
create a new skill when you have permission, usually to standardize a method across several agents

The header includes:

page title Skills
a short description referencing the Agent Skills specification
Add Skill

The filter row includes:

search field
visibility filter
tag filter
result count

Each skill card shows:

skill name
short description
Enabled or Disabled
Company-managed or Shared state
whether it is URL-based or Direct content
fetch recency for URL-based skills
compatibility label when present
tags

Those card signals matter because they answer three immediate questions without opening the detail page:

is this skill currently active
is this skill centrally maintained or locally owned
if something needs updating, should I edit it here or refresh it from the source URL

Empty states on the list page

If no skills exist yet, the page suggests creating the first skill by URL, paste, or file upload.

If filters remove all visible skills, the page shows No skills match your filter.

Skill detail header

The skill detail header gives the user immediate context:

back button to Skills
skill name
source type label such as URL-based Skill or Direct Content Skill
enabled or disabled badge
company-managed, shared, and read-only states when relevant

For URL-based skills, the header also includes Refresh.

That action re-fetches the content from the source URL and is one of the most important buttons on the page.

For end users, Refresh is the quickest way to answer a common operational question:

did the source skill change outside XTM One, and do I need to pull the latest version into this workspace

Tabs on the detail page

The skill detail page contains:

Overview
Configuration
Activity

Overview tab

The Overview tab helps the user judge whether the skill is active, up to date, and widely used.

The KPI row can show:

agents using the skill
content size
assignment run count
last refresh for URL-based skills
last activity

Together, these indicators help the user judge:

whether the skill is widely reused or only experimental
whether the skill is likely to be large and method-heavy or short and focused
whether the skill was refreshed recently enough to trust its current source-backed version
whether the skill is still active in day-to-day operations

The main overview card can show:

description
source URL or direct content origin
compatibility label
content preview
tags
created and updated timestamps

At the bottom, the Agents Using card shows which agents currently depend on the skill.

Configuration tab

The Configuration tab is where you inspect or edit how the skill is defined.

In read mode, the user sees:

name
status
URL
compatibility
description
tags

This read view is useful when the user mainly wants to inspect the skill before deciding whether to reuse it, refresh it, or ask an admin to change it.

In edit mode, you can change:

name
compatibility
source URL
tags
description
markdown content
enabled or disabled state
Hide from chat
sharing and visibility settings
public catalog state when available

These fields are not equal in purpose:

name, description, and tags help others find and understand the skill
URL matters when the skill is maintained outside XTM One and should be refreshed from a source of truth
markdown content is where the actual operating method lives
Enabled controls whether the skill currently affects agents
Hide from chat controls discoverability in chat contexts, not whether the skill exists
sharing and catalog settings control who can reuse the skill

The content editor includes a variable insert control. This matters when skills need reusable values in their instructions.

The Enabled switch changes whether the skill is injected into agent prompts. In practice, that means the skill can stay saved but stop affecting agents immediately.

Activity tab

The Activity tab is the audit and history view for the skill.

Users come here when they need to understand:

whether a skill changed recently
whether a refresh happened
whether a behavior change came from content edits rather than from the agent itself

That makes Activity especially useful during troubleshooting, because it helps distinguish:

a skill change
an agent configuration change
a normal difference in model behavior

Read-only states you notice

Some skills behave as read-only because of ownership or product policy:

company-managed skills can be read-only for non-admins
shared skills can still be editable in a group context
some built-in skills can behave as non-editable resources

When the page is read-only, the inspection experience remains useful even if editing is not allowed.

Good habits on these pages

Check whether a skill is enabled before blaming the agent for missing behavior.
Use Refresh on URL-based skills when the source was updated.
Review Agents Using before changing a shared skill.
Keep compatibility and description fields meaningful so reuse stays easy.