Skip to main content
Glama

skillporter_add

Install AI agent skills from a workspace path, archive, or GitHub repository into target harnesses, with controls for overwriting conflicts and accepting security findings.

Instructions

[WRITE] Install skills from a workspace directory, archive, or repository into target harnesses (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": {
      "source": "<source>",
      "harnesses": "<harnesses>"
    },
    "name": "skillporter_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoWorkspace-relative root path (default: '.')
forceNoOverwrite conflicting existing installations (never bypasses security findings)
sourceYesWorkspace-relative path or GitHub owner/repo specifier
strategyNocopy
harnessesYesTarget harness IDs (e.g. ['claude-code', 'codex', 'cursor'])
accept_riskNoExplicitly accept non-structural security findings after inspection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.6/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 genuinely new context by disclosing the environment-variable write gate, which the agent cannot learn from the schema or annotations. It stops short of describing conflict behavior, what gets written to disk, or whether a security scan runs first, but for a tool with annotation coverage this is solid added value.

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?

A single front-loaded sentence with the write marker first, the action second, and the prerequisite trailing in parentheses — no filler. The only mild cost is that the bracketed tag is a convention the agent must decode rather than plain prose.

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?

For a six-parameter mutation tool with no output schema, the description covers what it does and the write prerequisite but leaves out the outcome (what appears in the target harnesses), failure/conflict handling, and the relationship between accept_risk and any pre-install security scan. Adequate but with clear gaps for a write operation.

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 coverage is 83%, so the schema already documents nearly every parameter including defaults for force, accept_risk, strategy, and path. The description adds only that 'source' may also be an archive, a small extension beyond the schema's 'workspace-relative path or GitHub owner/repo specifier' — the baseline 3 applies when the schema carries the load.

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?

States a concrete verb and resource ('Install skills') plus the three source forms (workspace directory, archive, repository) and the destination ('target harnesses'). An agent immediately knows what the tool does, but nothing distinguishes it from the close sibling skillporter_install or skillporter_import, which an agent could easily pick instead.

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?

The '[WRITE]' prefix and the parenthetical 'requires SKILLPORTER_MCP_ALLOW_WRITES=1' give a clear precondition for calling it, which is useful gating. However, there is no statement of when to prefer this over skillporter_install, skillporter_import, or skillporter_sync, so the routing decision 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.