Skip to main content

install Command

Install skills from skill-project.toml [dependencies] section into .claude/skills/. Creates or updates skills.lock for reproducible installations.

Usage

Options

Examples

Install All Dependencies

Install all skills declared in skill-project.toml:
This:
  • Reads dependencies from skill-project.toml at project root
  • Resolves skills from configured repositories
  • Installs skills into .claude/skills/
  • Creates or updates skills.lock with exact versions

Install Without Dev Skills

Install production skills only, excluding dev group:
This is useful for CI/CD pipelines where you want lean production deployments without development dependencies.

Install Only Specific Groups

Install only skills from specific groups:

Reproducible Installation

Install exact versions from skills.lock:
Use --lock for production deployments to ensure you install the exact same versions that were used in development.

Combined Example: Production Deployment

Install production skills with exact versions:

Behavior

The install command:
  1. Locates Project File: Finds skill-project.toml at project root or walks up directory tree
  2. Loads Dependencies: Reads [dependencies] section from skill-project.toml
  3. Applies Group Filters: Filters dependencies based on --without and --only flags
  4. Resolves Skills: For each dependency:
    • If --lock is set: Resolves exact versions from skills.lock
    • Otherwise: Resolves latest compatible versions from repositories
  5. Installs Skills: Downloads and installs skills into .claude/skills/
  6. Updates Lockfile: Writes exact versions to skills.lock at project root

Dependency Groups

Skills can be organized into groups for selective installation. Specify groups in skill-project.toml:
skill-project.toml
If no groups are specified, the skill belongs to no groups and will always be installed.

Default Group Behavior

Skills Lock File

The skills.lock file ensures reproducible installations across environments.

Lock File Structure

skills.lock

Lock File Usage

Development Mode (with skill-project.toml):
Production Mode (with skills.lock):

Lock File Workflow

Dependency Resolution

The install command resolves dependencies from multiple sources:

Source Types

skill-project.toml

Repository Priority

Skills are resolved from repositories configured in [tool.fastskill.repositories]:
skill-project.toml
Lower priority numbers take precedence. In this example, public-registry (priority 0) is checked before team-registry (priority 1).

Output Examples

Successful Installation

With Group Filters

Reproducible Installation

Error Handling

Missing Lock File

Solution: Run fastskill install without --lock to create the lockfile first.

Missing skill-project.toml

Solution: Run fastskill init to create skill-project.toml or use fastskill add to add individual skills.

Unresolved Dependencies

Solution: Check the skill ID and ensure repositories are configured correctly with fastskill repos.

Conflicting Group Flags

Solution: Use either --without or --only, but not both at the same time.

Workflow Examples

Initial Project Setup

Development Workflow

Production Deployment

CI/CD Pipeline

Best Practices

1

Commit both skill-project.toml and skills.lock

Always commit both files to version control. This ensures all team members install the same versions.
2

Use groups for environment-specific dependencies

Separate dev, test, and production dependencies into groups. Use --without dev for production builds.
3

Run fastskill install before committing

Run fastskill install after modifying skill-project.toml to update skills.lock with new versions.
4

Use --lock for production deployments

Always use --lock flag in production to ensure exact version matches.
5

Reindex after installation

Run fastskill reindex after installation to update the semantic search index.

See Also