Managing Skills

Creating a Skill

1. Click New Skill in the skills admin panel.
2. Fill in the fields:

• Skill ID — Short unique identifier (e.g., graphmart_file, query, save). Used in resolve_skill lookups.
• Name — Display name shown to AI assistants in the catalog listing.
• Description — One-line summary shown in the catalog listing.
• Shared Context — Instructions shared with the AI when the skill is expanded. This is the key field — it consolidates guidance that would otherwise be duplicated on every tool.
• Is Sub-Skill Only — When checked, hides this skill from the top-level catalog listing. The skill is only visible when a parent skill references it as a sub-skill.

4. Click Save.

Adding Sub-Skill References

1. Click Add Sub-Skill on a parent skill.
2. Select an existing skill from the dropdown.
3. Enter a display name for the sub-skill reference.
4. Click Save.

The referenced skill becomes a child of the parent. When the AI resolves the parent skill, it sees the sub-skill listed with its tool count and can drill in further.

Adding Tool References

1. Click Add Tool on a skill.
2. Select a tool name from the autocomplete dropdown (populated from registered MCP tools).
3. Enter a one-line Summary.
4. Click Save.

Reordering

Drag skills, tool references, or sub-skill references to reorder them. The display order controls what AI assistants see in the catalog.

Copying a Skill to Another Server

When multiple MCP server endpoints are configured, you can copy a skill from one server's catalog to another by dragging it:

1. Select the source server in the sidebar
2. Drag a skill card from the main panel onto a different server card in the sidebar
3. Valid drop targets highlight with a green border and a "Copy here" chip
4. Drop the skill — a confirmation dialog appears and the skill is cloned into the target server's catalog

This creates an independent copy of the skill (and its tool/sub-skill references) on the target server. After copying, each server's copy can be edited independently.

Copying a skill to a server that was previously sharing the default catalog gives that server its own independent catalog — the same behavior as editing a skill directly on that server.

Editing and Deleting

Click Edit Skill or a tool reference to modify fields. Click Delete Skill or Remove on a tool reference to remove it. Changes take effect immediately — no restart required.

Reset to Defaults

Click Reset to Defaults to restore the built-in skill definitions. This deletes all current skills and replaces them with the defaults shipped with the server.

Import and Export

Skills can be managed via the Admin UI or the REST API.

REST API — Add a Skill with Tool References

Define a skill and its tool references in a single JSON file (e.g., my-skill.json):

{ "skillId": "graphmart", "title": "Graphmart Management", "description": "Create, configure, activate, reload, refresh, and delete graphmarts", "sharedContext": "Always create the graphmart first before adding layers.", "toolReferences": [ { "title": "rest_createGraphmart", "description": "Create and configure a new graphmart" }, { "title": "rest_activateGraphmart", "description": "Activate a graphmart on AnzoGraph" } ] }

Create the skill and add its tool references:

# 1. Create the skill (strip toolReferences — not part of the Skill schema) SKILL_JSON=$(jq 'del(.toolReferences)' my-skill.json) RESPONSE=$(curl -sk -u sysadmin:password -X POST https://localhost:8443/api/skills \ -H "Content-Type: application/json" -d "$SKILL_JSON") SKILL_URI=$(echo "$RESPONSE" | jq -r '.uri')

2. Add each tool reference

ENCODED=$(python3 -c "import urllib.parse,sys; print(urllib.parse.quote(sys.argv[1], safe=''))" "$SKILL_URI") jq -c '.toolReferences[]' my-skill.json | while read -r TOOL; do curl -sk -u sysadmin:password -X POST "https://localhost:8443/api/skills/$ENCODED/toolreferences" \ -H "Content-Type: application/json" -d "$TOOL" done

REST API — Remove a Skill

Deleting a skill removes it and all its tool references:

SKILL_URI="http://cambridgesemantics.com/skills/graphmart" ENCODED=$(python3 -c "import urllib.parse,sys; print(urllib.parse.quote(sys.argv[1], safe=''))" "$SKILL_URI") curl -k -u sysadmin:password -X DELETE "https://localhost:8443/api/skills/$ENCODED"

See the Skills REST API documentation for additional examples (remove single tool reference, manual curl commands).

REST API — Add a Sub-Skill Reference

Link an existing skill as a sub-skill of a parent:

PARENT_URI="http://cambridgesemantics.com/skills/data\_management" ENCODED=$(python3 -c "import urllib.parse,sys; print(urllib.parse.quote(sys.argv[1], safe=''))" "$PARENT_URI") curl -sk -u sysadmin:password -X POST "https://localhost:8443/api/skills/$ENCODED/subskillreferences" \ -H "Content-Type: application/json" \ -d '{"title": "File Staging", "referencesSkill": {"uri": "http://cambridgesemantics.com/skills/file\_staging"}}'

Admin UI — Export / Import

• Export Agent Skills zip: Click Export on a skill → downloads a .zip containing SKILL.md (YAML frontmatter + markdown) and references/tools.md, conforming to the Agent Skills specification.
• Import Agent Skills zip: Click Import → select a .zip with the Agent Skills directory structure