installing-skills
npx machina-cli add skill oaustegard/claude-skills/installing-skills --openclawInstalling Skills
Install skills from github.com/oaustegard/claude-skills to /mnt/skills/user, making them available in the current and future conversations.
Execution
Run the installation script:
bash /mnt/skills/user/installing-skills/scripts/install.sh
The script:
- Fetches repository contents via GitHub API
- Downloads SKILL.md for each skill directory
- Reports installed/updated/skipped counts
- Excludes: templates, .github, .claude, .uploads directories
Network Requirements
Requires access to:
api.github.com- Repository structure listingraw.githubusercontent.com- File downloads
If blocked, report the specific endpoint and suggest checking network settings.
Triggers
Execute installation automatically when:
- User explicitly requests skill installation/update
- User references a skill not present in
/mnt/skills/user - User mentions missing capabilities that match known skill patterns
After installation, proceed with user's original request.
Verification
Installed skills appear in system's <available_skills> automatically. Manual verification:
ls /mnt/skills/user
Manual Installation
For single skills or testing:
mkdir -p /mnt/skills/user/{skill-name}
curl -s "https://raw.githubusercontent.com/oaustegard/claude-skills/main/{skill-name}/SKILL.md" \
-o "/mnt/skills/user/{skill-name}/SKILL.md"
Source
git clone https://github.com/oaustegard/claude-skills/blob/main/installing-skills/SKILL.mdView on GitHub Overview
Install skills from github.com/oaustegard/claude-skills into /mnt/skills/user, making them available in current and future conversations. It uses a scripted fetch to enumerate skill dirs, pull SKILL.md files via the GitHub API, and report installed/updated/skipped counts while excluding templates and internal dirs.
How This Skill Works
Run the installation script at /mnt/skills/user/installing-skills/scripts/install.sh. The script fetches repository contents via the GitHub API, downloads SKILL.md for each skill directory, and reports installed/updated/skipped counts. It excludes templates, .github, .claude, and .uploads directories to keep the skill set clean.
When to Use It
- When the user explicitly requests skill installation or update.
- When the user references a skill not present in /mnt/skills/user.
- When the user mentions missing capabilities that match known skill patterns.
- When preparing to tackle a task that requires newly added skills.
- When performing a sanity check after a manual install of a single skill.
Quick Start
- Step 1: Run bash /mnt/skills/user/installing-skills/scripts/install.sh
- Step 2: Check /mnt/skills/user to verify installed SKILL.md files are present
- Step 3: Proceed with the user's request using the newly installed skills
Best Practices
- Ensure network access to api.github.com and raw.githubusercontent.com before running the installer.
- Install only when explicitly requested or when a required skill is missing.
- Review the installer output for counts of installed, updated, and skipped skills.
- Verify new skill directories exist under /mnt/skills/user after installation.
- Test newly installed skills in a safe, non-critical conversation before relying on them in production.
Example Use Cases
- A user asks to install skills to bring in a new invoice-processing capability that isn't currently installed.
- You receive a request to update skills to include a recently added sentiment-analysis skill.
- The user mentions a missing capability that matches a known skill pattern, prompting automatic installation.
- You test a single skill by manually installing it via the single-skill method and then invoke it in a task.
- After installation, you proceed with the user's request using the newly loaded skills.