Skill Management

Two Levels

Skill management is split into two layers:

Global skill repository management: admins maintain shared skill sources
Project skill management: managers and owners install shared skills into the current project

Admin Global Skill Management

Entry:

Skill Management in the lower-left Workspace menu
Page path: /workspace/admin/skills

What admins can do:

Add GitHub or other Git repository URLs
Set a branch for a repository
Manually sync a single repository
Search repositories or skills
Collapse or expand repositories
Delete an individual skill
Delete an entire repository

Repository Sync and Parsing

After an admin adds a repository, the system automatically:

Downloads the repository into the global skill storage directory
Recursively scans the repository for SKILL.md
Treats each directory containing SKILL.md as one skill
Parses the skill name, path, and description
Builds the global skill list available to projects

Notes:

The default skill name is the directory name containing SKILL.md
Description parsing prefers the description field in SKILL.md frontmatter
If no frontmatter description exists, the parser falls back to the first valid paragraph in the body

Project Skills Management

Entry:

The Skills button in the project workspace header

Modal layout:

Left side: Installed plus repository list
Right side: skills for the selected group
Top search box: filters skills in the current group

What managers and owners can do:

Select a skill from a repository and install it into the project
Enable or disable a global skill for the current project
Review skills already installed in the project
Remove installed skills

In dev mode, the system also auto-enables two built-in authoring skills from the global read-only skill mount:

agent-authoring
visualizer-authoring

They are available at:

/global/skills/builtin/<skill-name>

Notes:

these are mode-managed built-in skills
they appear automatically in dev mode
they are removed automatically when the project switches back to standard mode
they are not meant to be manually installed, deleted, or imported like regular skills

Storage Location After Install

Installed project skills are stored at:

.agent/skills/<namespace>/<skill-name>

Legacy one-level installs under .agent/skills/<skill-name> remain supported for compatibility. If the target folder name is already used in the current project, the system will not auto-rename it; choose a different install name manually.

Notes:

The right-side Local Workspace tree hides .agent by default
This does not affect /skill:<name> discovery or invocation
Removing an installed skill deletes both the installation record and the local directory

Enabling a Global Skill

If you want a global skill to be available in the current project without copying it into a local install directory, use Enable global.

What this does:

Stores a global enablement record for the current project
Does not create a new installation snapshot under .agent/skills
Keeps the skill pointed at the global repository definition, which is useful when you want a single shared source of truth
You can later turn it off with Disable global

Recommended Practice

Prefer maintaining shared skills through global repositories instead of manually editing project .agent/skills
After updating a repository, admins should sync it first, then projects can reinstall as needed
If a repository contains multiple SKILL.md files, keep directory names clear so project managers can identify the right skill

If you need to create or modify file preview plugins, prefer the built-in visualizer-authoring skill:

it guides creation of .agent/visualizers/<namespace>/<name>/
it provides a starting structure for VISUALIZER.yaml and web/index.html
it includes templates and examples, including a CSV visualizer example

Skill Import/Export

Installed project skills support export and batch import for cross-project migration and backup.

Export Skills

In the project Skills modal, you can:

Select installed Skills to export (multi-select supported)
Click the export button
The system packages selected Skills as a zip archive for download

Exported zip file structure:

skills-20260401-120000.zip
├── manifest.json           # Metadata manifest
└── skills/                 # Skills directory
    └── <namespace>/<skill-name>/  # Skill directory
        ├── SKILL.md
        └── ...other files

Import Skills from Other Projects

Besides importing zip archives, you can also directly import installed Skills from other projects:

Operation path:

Click the "Import from Project" button in the project Skills modal
Select a source project from the dropdown (shows all accessible projects)
The system automatically loads the list of installed Skills from the source project
Review Skill name, title, description, and installation path
Click the "Import from Project" button to import a single Skill

Import features:

Skills with matching names show a "Name Match" badge for easy identification
Sorted by name match priority, then alphabetically by title
Only shows installed Skills (excludes dev mode agent-authoring)
Automatically copies Skill directory and creates installation record

Use cases:

Quickly copy validated Skills from other projects
Avoid reinstalling the same Skills from repositories
Team members share pre-configured Skill combinations

Notes:

Import fails if a Skill with the same name already exists in the target project
Imported Skills use the current version snapshot from the source project
Requires access permissions to the source project to see its Skills

Import Skills

In the project Skills modal, you can:

Click the import button
Upload a Skills zip archive
The system automatically parses manifest.json and installs Skills

Import process:

Parses manifest.json from the zip file
Copies Skills directories to project's .agent/skills/
Creates database installation records

Notes:

If a Skill with the same name already exists in the project, import will fail with a conflict message
Imported Skills are immediately available for Agent invocation
Verify skill source trustworthiness before importing

Skill Management

On this page