Skip to main content

update Command

Update installed skills to the latest versions from their sources. Updates skills.lock with new versions.

Usage

Options

Examples

Update All Skills

Update all installed skills to latest compatible versions:
This:
  • Reads all skills from skill-project.toml dependencies
  • Resolves latest versions from configured repositories
  • Updates skills in .claude/skills/
  • Updates skills.lock with new versions

Update Specific Skill

Update only a specific skill:

Check for Updates

Check which skills have updates available without installing:
Use --check to see what’s available before updating. Useful for reviewing changes before applying them.

Dry Run

Preview what would be updated without making changes:

Update to Specific Version

Update a skill to a specific version:

Update with Patch Strategy

Update skills to latest patch version only (no minor or major changes):

Update with Minor Strategy

Update skills to latest minor version (allows minor features, no breaking changes):

Update with Major Strategy

Update skills to latest major version (allows breaking changes):

Update Strategies

Update strategies determine which versions are considered for updates:

Strategy Examples

Behavior

The update command:
  1. Locates Project File: Finds skill-project.toml at project root
  2. Loads Dependencies: Reads [dependencies] section
  3. Filters Skills: If skill_id is specified, only updates that skill
  4. Resolves Updates: For each skill:
    • If --version is set: Resolves specific version
    • Otherwise: Resolves version based on strategy (latest/patch/minor/major)
    • If --source is set: Uses specific source
    • Otherwise: Uses source from dependency definition
  5. Updates Skills: Downloads and installs updated versions into .claude/skills/
  6. Updates Lockfile: Writes new versions to skills.lock

Update Modes

Update Mode (default)

Updates skills and modifies lockfile:
Output:

Check Mode

Shows available updates without installing:
Output:

Dry Run Mode

Shows what would be updated without making changes:
Output:

Output Examples

Update All Skills

Update Single Skill

Update with Strategy

Check for Updates

Update Workflow

Standard Update Workflow

Controlled Production Update

Automated Update (CI/CD)

Version Constraint Examples

Update to Specific Version

Update from Specific Source

Combined with Strategy

Dependency Management

Update Order

Skills are updated alphabetically for deterministic output:

Update Failures

If one skill fails to update, the command continues with remaining skills:

Error Handling

Skill Not Found

Solution: Check skill ID in skill-project.toml or add it first with fastskill add.

Version Not Found

Solution: Check available versions with fastskill repos versions web-scraper.

No Updates Available

Network Errors

Solution: Check network connection and retry failed skills individually.

Best Practices

1

Check before updating

Use fastskill update --check to see what’s available before applying updates. Review changes, especially for major version bumps.
2

Use appropriate strategies

  • Use --strategy patch for bug fixes only
  • Use --strategy minor for new features without breaking changes
  • Use --strategy major when you’re ready for breaking changes
  • Use --strategy latest for bleeding edge (not recommended for production)
3

Reindex after updates

Always run fastskill reindex after updating skills to keep search index current.
4

Commit lockfile after updates

Commit skills.lock after successful updates to track version changes in version control.
5

Test updates in development first

Test skill updates in development environment before deploying to production, especially for major version updates.

See Also