Skip to main content
Glama
AndreyTsibin

mcp-super-app

by AndreyTsibin

Install skill

install_skill

Copies a bundled skill into a project or runs a proxied skill's CLI to install it. A session restart is required for the installed skill to load.

Instructions

Install a personal skill into a project. Bundled skills are copied into .claude/skills// (idempotent, existing files kept); proxied skills are installed by running their official CLI in the project. IMPORTANT: skills load only at session start — after installing, STOP and ask the user to restart the Claude Code app/session before invoking the skill. Note: .claude/skills/ is gitignored by bootstrap_project — skills are tooling, not project code. manual_only applies to bundled skills only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillYesSkill id — the enum values are the valid ids. Catalog: • frontend-design (bundled) — Frontend Design: Distinctive, production-grade frontend UI that avoids generic AI aesthetics. • fullstack-architect (bundled) — Full-Stack Architect: Turn ideas into production docs: PRD → ARCHITECTURE → PLANNING → TASKS. Wizard/Expert modes. • humanizer-ru (bundled) — Humanizer (RU): Strip AI-writing tells from Russian copy — канцелярит, genitive chains, «является», calques, dash-as-connector. Hybrid of blader/humanizer + humanizer-ru (MIT). Russian only: the id is language-scoped so it can't collide with an English `humanizer` installed globally. • image (bundled) — Image Prompting: Writes model-specific image prompts for Seedream 4.5 and Gemini 3, plus the sizing args to pass — feed the result to create_image. Prompt syntax follows each vendor's official guide. Parts derive from smixs/visual-skills (MIT). • ui-ux-pro-max (proxied, runs `npx --yes ui-ux-pro-max-cli@latest init --ai claude`) — UI/UX Pro Max: Macro-design intelligence: styles, palettes, font pairings, stacks. Installs via its own CLI. • emil-design-skills (proxied, runs `npx --yes skills@latest add emilkowalski/skills`) — Emil Design Skills: Micro-design: animation timing, motion physics, Apple principles. Complements ui-ux-pro-max. bundled = copied from the server's frozen payload; proxied = installed by running the third-party CLI shown above in the project, so the user gets its current release.
manual_onlyNoBundled only: install as manual-only (/name), 0 tokens at rest. Default false.
project_pathYesAbsolute path to the target project directory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
skillYes
invokeYesHow to trigger the skill once installed.
outputNoProxied: tail of the installer output.
commandNoProxied: the CLI command that ran.
createdNo
skippedNo
gitignoredYesPatterns newly added to .gitignore (empty if already covered).
manual_onlyNo
install_pathNoBundled: where the skill was copied (relative to project).
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses idempotency (existing files kept), execution of third-party CLIs for proxied skills, the session-start timing issue, the gitignore behavior relative to bootstrap_project, and the scoping of manual_only. This is exceptionally transparent about side effects and prerequisites.

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 dense but each sentence carries essential information: installation method, restart warning, gitignore note, and manual_only scope. It is not minimal, but the complexity (two installation modes, session caveat) justifies the length. Mildly verbose but well-structured.

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?

For a tool with two distinct install methods and a session-restart caveat, the description covers all critical context: mechanics, side effects, idle-token behavior for manual_only, and integration with existing project tooling. An output schema exists, so omitting return format is appropriate. No significant gaps.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value beyond the schema by clarifying that manual_only only applies to bundled skills, that proxied skills run an official CLI, and that .claude/skills/ is gitignored. These enrich parameter understanding beyond the schema's own field descriptions.

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?

States a specific verb+resource: 'Install a personal skill into a project.' Clearly differentiates between bundled and proxied installation methods, and the tool name itself disambiguates from sibling tools like bootstrap_project or install_guard. Purpose is unmistakable.

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

Usage Guidelines4/5

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

Provides clear context on when and how to use: explains bundled vs. proxied mechanics, and the critical instruction to ask the user to restart after installing. However, it does not explicitly mention alternatives or say 'use this tool when the user wants to install a skill and not for X.' Lacks an explicit exclusion statement, but context is strong.

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/AndreyTsibin/mcp-super-app-public'

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