skillinstaller

Install the same Agent Skill across many providers from a single .skill/ source, with correct project vs user scope and deterministic path resolution.

Library-first: embed the installer engine in your tooling. The CLI is a thin utility wrapper over the same engine.

One .skill/ in, many providers out, with deterministic targets and deduplicated shared paths.

What it solves

• Provider path sprawl: each provider uses different skills directory conventions.
• Scope confusion: project vs user installs should be explicit and predictable.
• Duplicate installs: providers sharing .agents/skills should resolve to one physical target.

Primary Use: Embed as a Library

This project is intended to be consumed as a reusable installer engine by:

• internal platform CLIs
• setup/bootstrap tools
• CI/CD automation
• MCP/server-side skill orchestration

Core contract:

• parseSkill(source) -> ParsedSkill
• supportedProviders() -> ProviderInfo[]
• detectProviders(projectRoot?) -> DetectedProvider[]
• promptProviderSelection(options?) -> InteractiveProviderSelectionResult
• resolveInstallTarget(provider, scope, projectRoot?) -> InstallTarget
• install(request) -> InstallResult

Quick flow:

skill = parseSkill(source)
providers = detectProviders(projectRoot)
result = install({ source, providers, scope, projectRoot, method, force })

Shared types:

• Scope: project | user
• ProviderId: provider slug (claude-code, cursor, codex, etc.)
• SkillSource: source containing .skill/
• InstallRequest: { source, providers, scope, projectRoot?, method, force? }
• InstallResult: installed targets, normalized providers, warnings

Normalization rule:

• Providers using .agents/skills map to universal to avoid duplicate installs.
• Interactive selection helper keeps .agents providers locked/included via universal and only lets users select non-universal providers.

CLI (Utility)

cargo run --bin install-skill -- install \
  --source ./path/to/skill-repo \
  --providers claude-code,cursor \
  --scope project \
  --project-root /path/to/project

Source Format

The source must contain:

.skill/
  SKILL.md
  ...any extra files/folders

SKILL.md is parsed for frontmatter (name required), and the full .skill/* payload is installed.

Options

Examples

# List supported providers
cargo run --bin install-skill -- providers

# Detect installed providers from machine/project signals
cargo run --bin install-skill -- detect --project-root /path/to/project

# Install to user scope for all providers
cargo run --bin install-skill -- install \
  --source ./my-skill-source \
  --providers '*' \
  --scope user \
  --method symlink \
  --force

Installation Scope

Provider behavior

• Providers that use .agents/skills are normalized to universal.
• This avoids duplicate installs when multiple selected providers share the same physical path.
• Non-.agents providers are installed to provider-specific paths.

Supported Providers

Commands

What are Agent Skills?

Agent Skills are reusable instruction packages defined by SKILL.md + optional supporting files.

• Spec reference: https://agentskills.io/specification
• Provider path model inspiration: https://github.com/vercel-labs/skills

Notes

• This README documents the installer contract, independent of implementation language.
• The CLI exists for local testing and operational convenience.
• Interactive prompts are available behind the interactive feature flag in Rust (features = ["interactive"]).