install

Sync the Skadi repository into configured Claude config roots.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/LarryHsiao/Skadi --skill install-larryhsiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install
Source: https://github.com/LarryHsiao/Skadi/tree/main/.claude/skills/install
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill install-larryhsiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skadi's /install skill automates deploying its repository into one or more Claude config roots, solving the manual, error-prone process of keeping multiple environments in sync.

Core Features & Use Cases

  • Remembers configured Claude config roots and prompts for input when none are saved.
  • Runs install.sh for each target root to synchronize CLAUDE.md, settings.json, hooks, and skills.
  • Reports per-root installation results and file paths to verify success.

Quick Start

Run /install with a target root to sync Skadi into that Claude config root.

Frequently Asked Questions about install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically sync a repository into multiple Claude config roots?

Automated repository syncing into Claude config roots works by iterating through a memory-based root list and running an install script for each target, ensuring CLAUDE.md, settings, and hooks stay consistent. It prompts for input when no roots are saved.

What is the best way to deploy Skadi across multiple Claude environments?

Deploying Skadi across Claude environments is handled by an automated install skill that remembers configured roots, runs install.sh per target, and reports per-root file paths to verify success. It eliminates manual copy errors.

Does the Skadi install skill require pre-configured Claude roots to work?

Configured Claude roots are not strictly required to start installing Skadi. The skill remembers saved roots but will prompt you to input target paths when none are found in memory, ensuring installation proceeds across new environments.

How do I install Skadi into a specific Claude config root?

Installing Skadi into a specific Claude config root involves running the install command with the target root path. The skill executes install.sh to synchronize CLAUDE.md, settings, hooks, and skills, then reports the resulting file paths.

Why does my Skadi installation report errors across certain Claude roots?

Installation errors across Claude roots often occur when memory files are invalid or target paths are inaccessible. The skill validates memory files and reports per-root results, allowing you to identify which specific root failed synchronization.

Can I use Skadi to synchronize hooks and settings across Claude roots?

Synchronizing hooks, settings, CLAUDE.md, and skills across Claude roots is the core function of the Skadi install skill. It deploys these files into each configured root automatically, ensuring environment consistency.