SuperSkill

Overview Schema Source Related Servers Discussions Admin

skill_install

Destructive

Install skills from a GitHub repo (e.g. owner/repo or full URL). Resolves the skill list and gen/socket/snyk audits via skills.sh; fail-audit skills are blocked, and the unaudited GitHub fallback is used only when skills.sh is unreachable.

Instructions

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>"
    },
    "name": "skill_install"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	GitHub source: owner/repo, github:owner/repo, or full URL
`select_skills`	No	Optional list of skill names to install (installs all if omitted)
`allow_unaudited`	No	Allow fail-closed installs from the unaudited GitHub fallback (default false)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.13.0Oct 12, 2026

addedInput schema / properties / allow_unaudited

Added value: +{
+  "description": "Allow fail-closed installs from the unaudited GitHub fallback (default false)",
+  "type": "boolean"
+}

First observedv0.6.1Aug 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations only declare destructiveHint=true; the description adds real behavioral context beyond that: resolution goes through skills.sh and its gen/socket/snyk audits, failing audits are blocked, and the unaudited GitHub path is a fallback gated on reachability. It still omits what gets overwritten on install and whether auth is required, so not a 5.

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?

Two tightly packed sentences that front-load the action and source format before the audit policy. The audit sentence is dense but each clause carries distinct information, so only minor trimming is possible.

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?

Given three params, full schema coverage, no output schema, and a destructive annotation, the description covers the audit/safety gate that the annotation does not. It is nearly complete, missing only install-target/overwrite and permission details.

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 schema already documents source, select_skills, and allow_unaudited. The description only restates the source format (owner/repo or full URL) and adds nothing about selection semantics or the unaudited flag beyond the schema.

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?

Specific verb (Install) plus resource (skills) plus source format (owner/repo or full URL). It is clearly distinct from the sibling skill_remove and skill_list_installed without opening any schema.

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?

States conditional behavior (fail-audit skills blocked, unaudited fallback only when skills.sh is unreachable) but never says when an agent should prefer this over skill_validate or superskill, nor lists prerequisites. Usage context is implied rather than stated.

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