install Command
Install skills fromskill-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 inskill-project.toml:
- Reads dependencies from
skill-project.tomlat project root - Resolves skills from configured repositories
- Installs skills into
.claude/skills/ - Creates or updates
skills.lockwith 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 fromskills.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
Theinstall command:
- Locates Project File: Finds
skill-project.tomlat project root or walks up directory tree - Loads Dependencies: Reads
[dependencies]section fromskill-project.toml - Applies Group Filters: Filters dependencies based on
--withoutand--onlyflags - Resolves Skills: For each dependency:
- If
--lockis set: Resolves exact versions fromskills.lock - Otherwise: Resolves latest compatible versions from repositories
- If
- Installs Skills: Downloads and installs skills into
.claude/skills/ - Updates Lockfile: Writes exact versions to
skills.lockat project root
Dependency Groups
Skills can be organized into groups for selective installation. Specify groups inskill-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
Theskills.lock file ensures reproducible installations across environments.
Lock File Structure
skills.lock
Lock File Usage
Development Mode (withskill-project.toml):
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
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
fastskill install without --lock to create the lockfile first.
Missing skill-project.toml
fastskill init to create skill-project.toml or use fastskill add to add individual skills.
Unresolved Dependencies
fastskill repos.
Conflicting Group Flags
--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
- Update Command - Update skills to latest versions
- Add Command - Add individual skills to project
- repos Command - Manage skill repositories
- Manifest System - Understanding skill-project.toml