home / skills / aviz85 / claude-skills-library / aviz-skills-installer

aviz-skills-installer skill

safe

/plugin/skills/aviz-skills-installer

This skill helps you discover, install, and manage AVIZ Skills Library skills with real-time fetch and guided setup.

npx playbooks add skill aviz85/claude-skills-library --skill aviz-skills-installer

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

2.6 KB

---
name: aviz-skills-installer
description: Install skills from the AVIZ Skills Library. Use when user wants to install a skill, browse available skills, set up Claude Code skills, or asks about skill installation. Triggers on "install skill", "add skill", "setup skill", "available skills", "skill library", "browse skills".
---

# AVIZ Skills Installer

A conversational guide to installing skills from the AVIZ Skills Library.

## Important: Fetch Real-Time Data

**DO NOT use hardcoded skill lists.** Always fetch current data from these sources:

1. **Skills List & Setup Guides**: https://aviz.github.io/claude-skills-library/
2. **GitHub Repository**: https://github.com/aviz85/claude-skills-library
3. **Individual Skill Pages**: https://aviz.github.io/claude-skills-library/skills/{skill-name}.html

Use WebFetch or WebSearch to get the latest available skills and their setup instructions.

## Conversational Flow

### Step 1: Discover Intent
Ask the user what they want:
- See available skills → Fetch from site
- Install a specific skill → Proceed to installation
- Learn about a skill → Fetch its documentation page

### Step 2: Fetch Available Skills
Use WebFetch on https://aviz.github.io/claude-skills-library/ to get the current list of skills.

### Step 3: Choose Installation Scope
Ask the user:
```
Where would you like to install this skill?
1. User-based (~/.claude/skills/) - Personal, available everywhere
2. Project-based (.claude/skills/) - Shared with team via git
```

### Step 4: Install the Skill
```bash
# Clone and copy
TEMP=$(mktemp -d)
git clone https://github.com/aviz85/claude-skills-library.git "$TEMP/lib" --depth 1

# For user-based:
mkdir -p ~/.claude/skills
cp -r "$TEMP/lib/skills/SKILL_NAME" ~/.claude/skills/

# For project-based:
mkdir -p .claude/skills
cp -r "$TEMP/lib/skills/SKILL_NAME" .claude/skills/

# Cleanup
rm -rf "$TEMP"
```

### Step 5: Install Dependencies (if needed)
```bash
cd DESTINATION/SKILL_NAME/scripts
npm install 2>/dev/null || true
```

### Step 6: Provide Setup Guide
Fetch the skill's documentation page and guide the user through any required configuration:
```
https://aviz.github.io/claude-skills-library/skills/{skill-name}.html
```

## Conventions for Skill Documentation

Each skill in the library MUST have:
1. **SKILL.md** - Main skill file with YAML frontmatter
2. **Setup page on GitHub Pages** - At `docs/skills/{skill-name}.html`

Skills requiring API keys should include:
- `.env.example` file with required variables
- Setup instructions on their documentation page

## See Also

- Library Website: https://aviz.github.io/claude-skills-library/
- GitHub Repository: https://github.com/aviz85/claude-skills-library

Overview

This skill installs and configures skills from the AVIZ Skills Library so you can extend Claude with community skills. It helps you browse the live library, pick a skill, choose an installation scope (user or project), and complete any post-install setup such as dependency install or API key configuration. It always fetches current data from the library website and skill pages before acting.

How this skill works

On request it fetches the current skills index from the AVIZ Skills Library site and displays available skills or a chosen skill's documentation page. When the user selects a skill, it clones the library, copies the selected skill into either a user-wide or project-local skills folder, installs any npm dependencies if present, and points the user to the skill’s setup page for additional configuration. It uses live web fetch/search to avoid stale lists or instructions.

When to use it

You want to install a skill from the AVIZ Skills Library into your personal Claude skills directory.
You need to add a skill to a project so team members get the same setup via version control.
You want to browse currently available skills and read their setup guides before installing.
You need help configuring a skill that requires API keys or additional environment variables.
You’re setting up Claude Code skills and want step-by-step install guidance.

Best practices

Always fetch the live skills index and the skill’s documentation page before installing to get up-to-date instructions.
Decide installation scope: use ~/.claude/skills for personal use or .claude/skills in a repo for project-shared skills.
After copying a skill, run dependency installation in the skill’s scripts directory (npm install) if present.
Check the skill documentation page for required env vars or API keys and follow any provided .env.example guidance.
Clean up temporary clones after copying to avoid leaving large temp folders on disk.

Example use cases

Browse available skills when you want a new tool (e.g., code runners, formatters, or integrations) and read setup steps before installing.
Install a personal skill into ~/.claude/skills so it’s available across your sessions on your machine.
Add a skill into a project’s .claude/skills folder so the entire team gets consistent behavior via git.
Set up a skill that requires an external API key: install the skill, copy .env.example to .env, and follow the skill page’s configuration steps.
Troubleshoot a failing skill by reinstalling dependencies and re-reading the skill’s docs for missing steps.

FAQ

How does the tool ensure the skill list is up to date?

It fetches the live skills index from the AVIZ Skills Library website each time, so it never relies on a hardcoded list.

Where should I install a skill for team use?

Install into your project’s .claude/skills directory so the skill can be tracked in version control and shared with teammates.

What if a skill needs API keys or environment variables?

Open the skill’s documentation page and follow its setup instructions. Look for an example env file and copy required variables into your local .env.