Skip to main content
Glama

save_skill

Create or update a skill with automatic validation and backup. Ensures descriptions meet length and clarity requirements, and body instructions are actionable.

Instructions

Create or update a skill. Validates before saving, auto-backs up before overwrite.

This tool enforces quality gates — if the skill fails validation, it will be REJECTED with specific error messages explaining what to fix. Fix the issues and call save_skill again.

Validation checks:

  • Description must be >= 50 chars and explain WHAT + WHEN

  • Body must be 3-500 lines of actionable instructions

  • Description should include trigger conditions

  • Body should avoid overly rigid language (explain WHY instead)

Args: name: Skill identifier (lowercase, hyphens, max 64 chars). description: What the skill does and when to trigger (>= 50 chars). Front-load the key use case. Include trigger conditions like 'Use this skill when...' or 'Activate whenever...'. body: Markdown body (3-500 lines). Follow the skill writing guide. extra_frontmatter: Optional JSON of additional frontmatter fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionYes
bodyYes
extra_frontmatterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses validation, auto-backup, rejection with errors. Without annotations, description carries burden; it's fairly transparent but lacks some details on overwrite reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with bullet points and args list. Slightly verbose but efficient overall. Could trim redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers validation, error handling, and parameter details. Output schema exists but description doesn't reference return values; still adequate for tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description fully compensates: explains name format, description length/content, body lines, extra_frontmatter usage. Adds significant meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Create or update a skill.' and elaborates on validation and backup. Distinguishes from siblings like delete_skill, get_skill, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when to use (create/update), validation checks, and retry on rejection. No explicit 'when not to use' but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CatVinci-Studio/skillForge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server