Skip to main content
Glama

AgentPlaybooks

by ai.agentplaybooks
OverviewDiscussionsAdmin

Create skill

create_skill

Create a new skill for this playbook. Use this to expand capabilities. Requires full or skills:write permission; with skills:propose the skill is saved as a proposal (status pending_review) that the owner or an editor approves before it exists. Use update_skill to change an existing skill and list_skills to check for name collisions first. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAgent Skills-compatible name (lowercase kebab-case, e.g. data-analyzer)
contentYesThe SKILL.md document. Its YAML frontmatter may carry a demonstrations list of {provider, ref, fidelity, role, title, sha256, segments}, where segments are {start, end, label, comment} in seconds; the list order is the order the demonstrations are performed in. A malformed block is rejected.
priorityNoPriority level (default 50)
descriptionNoWhat the skill does and when the agent should use it
playbook_idYesUUID or GUID of the target playbook

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"The instructions/prompt/code for the skill"New value: +"The SKILL.md document. Its YAML frontmatter may carry a demonstrations list of {provider, ref, fidelity, role, title, sha256, segments}, where segments are {start, end, label, comment} in seconds; the list order is the order the demonstrations are performed in. A malformed block is rejected."
  2. Changed7 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"Full markdown content (SKILL.md body)"New value: +"The instructions/prompt/code for the skill"
    • changedInput schema / properties / description / description
      Previous value: -"Description of what the skill does"New value: +"What the skill does and when the agent should use it"
    • removedInput schema / properties / licence
      Removed value: -{
-  "description": "License information (e.g., MIT, Apache 2.0)",
-  "type": "string"
-}
    • changedInput schema / properties / name / description
      Previous value: -"Agent Skills-compatible name (lowercase kebab-case, e.g., 'code-review')"New value: +"Agent Skills-compatible name (lowercase kebab-case, e.g. data-analyzer)"
    • changedInput schema / properties / playbook_id / description
      Previous value: -"UUID of the playbook"New value: +"UUID or GUID of the target playbook"
    • addedInput schema / properties / priority
      Added value: +{
+  "description": "Priority level (default 50)",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "playbook_id",
-  "name",
-  "description"
-]New value: +[
+  "playbook_id",
+  "name",
+  "content"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description goes further by disclosing the permission tiers and the approval workflow that determines whether the skill actually exists. It does not cover failure behavior (e.g. what happens on a name collision or malformed frontmatter) or what the call returns, so it stops short of full behavioral disclosure.

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?

Four sentences, front-loaded with the core action and then permissions, alternatives, and the target identifier. Efficient overall, though the closing playbook_id sentence largely duplicates the schema and could be dropped.

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?

No output schema exists, and the description never indicates what a successful create returns (e.g. the new skill id) or how to follow up. Everything else an agent needs to invoke the tool correctly — permissions, proposal mode, collision-check workflow, target playbook — is present.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's only parameter content is restating that playbook_id is a UUID/GUID, which the schema already says verbatim; it adds no syntax, format, or constraint detail beyond the structured fields.

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?

States a specific verb and resource (create a skill scoped to a playbook) and explicitly separates itself from update_skill and list_skills. An agent can identify this as the creation path without opening a schema.

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

Usage Guidelines5/5

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

Gives the precondition for use (full or skills:write permission), the divergent behavior under skills:propose (saved as pending_review proposal), and routes the agent to update_skill for existing skills and list_skills for collision checks. This is explicit when-to-use plus named alternatives.

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

All AgentPlaybooks toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources