Skip to main content
Glama

skillporter_export

Package a workspace skill environment into a portable .skillpack archive, bundling skills into one distributable file for sharing or migration. Requires write access enabled.

Instructions

[WRITE] Package the workspace skill environment into a portable .skillpack archive inside the workspace (requires SKILLPORTER_MCP_ALLOW_WRITES=1).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "output": "<output>"
    },
    "name": "skillporter_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
outputYesWorkspace-relative output .skillpack path
managed_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds that an archive file is created on disk and that an environment flag must be enabled, which an agent cannot learn from the annotations. It omits whether an existing file at the output path is overwritten and what is returned on success, but the write-gating disclosure is substantive beyond the structured fields.

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

Conciseness5/5

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

A single sentence plus a bracketed operation tag; the write nature, the artifact produced, and the gating requirement are all front-loaded with no filler.

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

Completeness3/5

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

With no output schema and three parameters, the description should at minimum cover what is returned and what the undocumented parameters do. It handles the mutation/gating story well but leaves the two unlabeled parameters and the overwrite/return behavior unexplained for a tool that writes files to the workspace.

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

Parameters2/5

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

Schema coverage is only 33% — only 'output' carries a description. The description adds that output is workspace-relative/inside-workspace, but 'path' (source directory, default '.') and especially 'managed_only' receive no explanation anywhere, so an agent cannot tell what managed_only filters or how path interacts with the packaged content.

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

Purpose4/5

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

Specific verb plus resource: 'Package the workspace skill environment into a portable .skillpack archive.' The '[WRITE]' tag and the archive format make the operation easy to distinguish from read-oriented siblings like skillporter_scan or skillporter_inspect. It stops short of naming the complementary sibling (skillporter_import) explicitly.

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

Usage Guidelines3/5

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

It gives a real precondition (SKILLPORTER_MCP_ALLOW_WRITES=1) and a scope constraint (archive lands inside the workspace), which implies when the tool is callable. It never states when to use this versus export-adjacent siblings such as skillporter_sync or skillporter_consolidate_preview, so routing is left to inference.

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