Skip to main content
Glama
@skills-hub-ai/mcp

@skills-hub-ai/mcp

install_skill

Install a skill from skills-hub.ai into your local Claude Code or Cursor skills directory. Specify a skill slug and optional target to make it available to compatible AI clients.

Instructions

Install a skill from skills-hub.ai to the local skills directory

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": {
      "slug": "<slug>"
    },
    "name": "install_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSkill slug to install
targetNoInstall target (default: claude-code)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the two key traits of source (remote skills-hub.ai, i.e. network required) and destination (writes to local skills directory). It says nothing about overwriting or idempotency when the skill is already installed, permissions, or failure modes, which are material for an install operation.

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 zero filler; the operation, source and destination all appear immediately. It is efficiently sized, though the compression is part of why behavioral and prerequisite details are absent.

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

Completeness2/5

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

For a mutating, network-dependent tool with no annotations and no output schema, the definition should cover overwrite behavior, whether the slug must come from a prior lookup, and what is returned on success or failure. None of that is present, leaving the agent unable to predict reinstall or error behavior.

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 both slug and target (with its enum and default) are already fully documented in the schema, setting the baseline at 3. The description adds no syntax, format or validation detail beyond what the schema provides.

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 specific verb ("Install") plus resource ("a skill from skills-hub.ai") and destination ("local skills directory"), which separates it cleanly from the read-only siblings get_skill_detail, list_installed_skills and search_skills. No explicit sibling differentiation is written, so it stops short of a 5.

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?

Usage is only implied: an agent infers it should call search_skills or get_skill_detail first to obtain a slug, but the description never states that prerequisite. No when-not conditions and no named alternative (e.g. "use list_installed_skills to verify before installing").

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