Skip to main content
Glama

Cloud Skill Manage Tool

skill_manage

Create, manage, and execute reusable AI skills including LLM prompts, connectors, rules, and guardrails. Supports direct execution of code, browser, and multi-model tasks.

Instructions

AI skills — reusable units agents invoke (LLM prompt templates, connector calls, rules, hybrid pipelines, guardrails). Skill executions are versioned (SkillVersion) and metered against the team budget. Direct execution actions (guardrail, multi_model, code_exec, browser) bypass the agent layer for ad-hoc invocation by humans/assistants.

When to use: build reusable prompt or workflow primitives that multiple agents share, or run a one-off skill (e.g. code_exec to evaluate Python in a sandbox). Do NOT use for raw LLM calls — use assistant_manage instead.

CRUD actions:

  • list (read) — optional: type (llm|connector|rule|hybrid|guardrail), status, limit (default 50).

  • get (read) — skill_id. Returns full config + latest version.

  • create (write) — name, type, config (type-specific JSON). Returns skill_id.

  • update (write) — skill_id + any creatable field. Bumps version; old version retained.

  • delete (DESTRUCTIVE) — skill_id. Soft-deletes; existing version history retained for 30 days.

  • versions (read) — skill_id. Version log with diffs and created_by AiRun id.

Direct execution (each costs credits; rate-limited per skill):

  • guardrail (read — costs ~1-3 LLM credits) — input (string), rules (array). Returns { passed: bool, violations: [...] }.

  • multi_model (write — costs ~N × LLM credits where N=models[].length) — prompt, models[]. Runs same prompt across providers and returns consensus.

  • code_exec (DESTRUCTIVE — runs in sandboxed Docker, costs sandbox-minute credits) — code, language (python|node|bash). Network-disabled by default; max 60s wall-clock; max 256 MB memory.

  • browser (write — costs browser-minute credits) — url, actions (array of {type, selector, value}). Headless Chromium with SSRF guards.

Cloud note: supabase_edge_function not exposed in cloud (use integration_execute with a Supabase integration instead). Errors: 401, 403, 404, 422, 429, 503 (sandbox/browser worker pool exhausted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, get, create, update, delete, versions, guardrail, multi_model, code_exec, browser
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
typeNoFilter by type: llm, connector, rule, hybrid
frameworkNoFilter by framework key (e.g. rice, spin, bant, okrs, unit_economics). See framework_list for full enum.
limitNoMax results to return (default 10, max 100)
skill_idYesThe skill UUID
nameYesSkill name
descriptionNoSkill description
prompt_templateNoSystem prompt template for LLM-backed skills
data_classificationNoData classification level: public, internal, confidential, restricted.
step_idNoFor get_result. The playbook step UUID.
workflow_node_idNoFor set_node_guardrail / remove_node_guardrail. The workflow node UUID.
guardrail_skill_idNoFor set_node_guardrail. The guardrail skill UUID to attach.
execution_idNoFor get_execution: the SkillExecution UUID.
worktree_execution_idNoFor get_execution / get_diff: the WorktreeExecution UUID.
statusNoFor list_executions: filter by status (pending_approval, completed, failed, approved, rejected).
Behavior5/5

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

With no annotations, the description fully shoulders the burden. It details the effects of each action (read/write/destructive), versioning behavior, soft-delete with 30-day retention, costs and rate limits for direct execution, sandbox restrictions (network-disabled, max 60s, 256 MB), and lists possible error codes. This is comprehensive.

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?

The description is lengthy (over 500 words) but well-organized with sections for CRUD, direct execution, cloud notes, and errors. Given the tool's complexity (multiple actions, 16 parameters, no output schema), the detail is necessary. A minor reduction could improve conciseness, but it remains clear and scannable.

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

Completeness5/5

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

The description fully covers the tool's purpose, all actions, parameter usage, error handling, cost implications, and cloud-specific limitations. Despite lacking an output schema, the description provides enough context for an agent to select and invoke the tool correctly across all scenarios.

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?

Although schema description coverage is 100%, the description adds significant context beyond parameter names and types. It groups parameters under actions (e.g., 'create (write) — name, type, config (type-specific JSON). Returns skill_id.'), explains the meaning of type, framework, and data_classification, and clarifies defaults and constraints for limit, deadline_ms, etc.

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?

The description clearly defines the tool as managing AI skills (reusable units) and lists all CRUD and direct execution actions. It explicitly distinguishes from siblings, such as warning not to use for raw LLM calls (use assistant_manage) and noting that supabase_edge_function is not exposed in cloud (use integration_execute).

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?

The description includes a 'When to use' section that specifies appropriate use cases (building reusable primitives, one-off skill execution) and explicitly says what not to do ('Do NOT use for raw LLM calls'). It provides clear alternatives (assistant_manage, integration_execute) and context-specific guidance.

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/escapeboy/agent-fleet-o'

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