Aviz Skills Installer

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

# 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)

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

Detailed Installation Guide

Prerequisites

• Git installed: git --version
• Node.js (for npm-based skills): node --version
• Claude Code installed and running

Complete Installation Commands

One-Liner for User-Based Installation

SKILL=skill-name && TEMP=$(mktemp -d) && git clone https://github.com/aviz/claude-skills-library.git "$TEMP/lib" --depth 1 && mkdir -p ~/.claude/skills && cp -r "$TEMP/lib/skills/$SKILL" ~/.claude/skills/ && rm -rf "$TEMP" && echo "Installed $SKILL to ~/.claude/skills/"

One-Liner for Project-Based Installation

SKILL=skill-name && TEMP=$(mktemp -d) && git clone https://github.com/aviz/claude-skills-library.git "$TEMP/lib" --depth 1 && mkdir -p .claude/skills && cp -r "$TEMP/lib/skills/$SKILL" .claude/skills/ && rm -rf "$TEMP" && echo "Installed $SKILL to .claude/skills/"

Step-by-Step Manual Installation

1. Clone the Library

# Create temp directory
TEMP_DIR=$(mktemp -d)

# Clone with minimal depth
git clone https://github.com/aviz/claude-skills-library.git "$TEMP_DIR/lib" --depth 1

# Verify clone
ls "$TEMP_DIR/lib/skills/"

2. Choose Your Scope

For User-Based (personal, all projects):

DEST=~/.claude/skills
mkdir -p "$DEST"

For Project-Based (shared via git):

DEST=.claude/skills
mkdir -p "$DEST"

3. Copy the Skill

SKILL_NAME=whatsapp  # Replace with desired skill

cp -r "$TEMP_DIR/lib/skills/$SKILL_NAME" "$DEST/"

# Verify copy
ls -la "$DEST/$SKILL_NAME/"

4. Install Dependencies (if needed)

Check if the skill has a package.json:

if [ -f "$DEST/$SKILL_NAME/scripts/package.json" ]; then
    cd "$DEST/$SKILL_NAME/scripts"
    npm install
    cd -
fi

5. Configure Environment (if needed)

Check for .env.example:

if [ -f "$DEST/$SKILL_NAME/.env.example" ]; then
    cp "$DEST/$SKILL_NAME/.env.example" "$DEST/$SKILL_NAME/.env"
    echo "IMPORTANT: Edit $DEST/$SKILL_NAME/.env with your API keys"
fi

6. Cleanup

rm -rf "$TEMP_DIR"

7. Verify Installation

# Check SKILL.md exists
cat "$DEST/$SKILL_NAME/SKILL.md" | head -20

8. Restart Claude Code

Close and reopen your terminal, then start a new Claude Code session.

Skill-Specific Setup

whatsapp

Requires Green API credentials: 1. Sign up at https://green-api.com/ 2. Create an instance and get credentials 3. Edit .env:

   GREEN_API_ID=your_instance_id
   GREEN_API_TOKEN=your_api_token

speech-generator

Requires ElevenLabs API key: 1. Sign up at https://elevenlabs.io/ 2. Get API key from settings 3. Edit .env:

   ELEVENLABS_API_KEY=your_api_key

nano-banana-poster

Requires Google Gemini API key: 1. Get key from https://makersuite.google.com/app/apikey 2. Edit .env:

   GEMINI_API_KEY=your_api_key

wordpress-publisher

Requires WordPress credentials: 1. Get your WordPress site URL 2. Create an application password in WordPress 3. Edit .env:

   WP_URL=https://your-site.com
   WP_USERNAME=your_username
   WP_PASSWORD=your_app_password

html-to-pdf / html-to-pptx

No API keys needed, but requires npm install:

cd ~/.claude/skills/html-to-pdf/scripts && npm install
cd ~/.claude/skills/html-to-pptx/scripts && npm install

calendar

Requires Google Apps Script setup: 1. Create a new Google Apps Script project 2. Deploy as web app 3. Follow instructions in SKILL.md

supabase-helper

Requires Supabase project credentials: 1. Create project at https://supabase.com/ 2. Get project URL and anon key 3. Configure as specified in SKILL.md

Installing Multiple Skills

# Install multiple skills at once
SKILLS="whatsapp speech-generator html-to-pdf"
TEMP=$(mktemp -d)
git clone https://github.com/aviz/claude-skills-library.git "$TEMP/lib" --depth 1

for SKILL in $SKILLS; do
    cp -r "$TEMP/lib/skills/$SKILL" ~/.claude/skills/
    echo "Installed: $SKILL"
done

rm -rf "$TEMP"

Updating a Skill

SKILL=whatsapp
DEST=~/.claude/skills

# Backup existing
mv "$DEST/$SKILL" "$DEST/${SKILL}_backup_$(date +%Y%m%d)"

# Reinstall
TEMP=$(mktemp -d)
git clone https://github.com/aviz/claude-skills-library.git "$TEMP/lib" --depth 1
cp -r "$TEMP/lib/skills/$SKILL" "$DEST/"
rm -rf "$TEMP"

# Restore .env if exists
if [ -f "$DEST/${SKILL}_backup_$(date +%Y%m%d)/.env" ]; then
    cp "$DEST/${SKILL}_backup_$(date +%Y%m%d)/.env" "$DEST/$SKILL/"
fi

Uninstalling a Skill

SKILL=whatsapp
DEST=~/.claude/skills

# Remove the skill
rm -rf "$DEST/$SKILL"

echo "Removed: $SKILL"

Troubleshooting

"Skill not found" after installation

1. Verify file exists:

   ls -la ~/.claude/skills/SKILL_NAME/SKILL.md

2. Check YAML frontmatter:

   head -10 ~/.claude/skills/SKILL_NAME/SKILL.md

Should start with --- and have name: and description: fields.

3. Restart Claude Code session completely.

npm install fails

# Try with legacy peer deps
npm install --legacy-peer-deps

# Or clean install
rm -rf node_modules package-lock.json
npm install

Permission errors

# Fix permissions
chmod -R u+rwX ~/.claude/skills/SKILL_NAME

Git clone fails

# Check git is installed
git --version

# Try HTTPS instead
git clone https://github.com/aviz/claude-skills-library.git

# If behind proxy
git config --global http.proxy http://proxy:port

Understanding Skill Locations and Scopes

The Skill Hierarchy

Claude Code loads skills from multiple locations with this precedence:

Key Rule: If two skills have the same name, higher priority wins.

Personal Scope (~/.claude/skills/)

Characteristics

• Location: Your home directory
• Visibility: Only you
• Persistence: Across all projects
• Version control: NOT in git

Best For

• Personal workflow tools
• Skills you use across multiple projects
• Testing new skills before sharing
• Custom configurations

Structure

~/.claude/
└── skills/
    ├── whatsapp/
    │   └── SKILL.md
    ├── speech-generator/
    │   └── SKILL.md
    └── my-custom-skill/
        └── SKILL.md

Project Scope (.claude/skills/)

Characteristics

• Location: Repository root
• Visibility: Anyone with repo access
• Persistence: Lives with the code
• Version control: Committed to git

Best For

• Team-wide skills
• Project-specific tools
• Onboarding new team members
• Standardized workflows

Structure

my-project/
├── .claude/
│   └── skills/
│       ├── project-helper/
│       │   └── SKILL.md
│       └── deploy-tool/
│           └── SKILL.md
├── src/
└── package.json

Git Commands for Project Skills

# Add skill to version control
git add .claude/skills/skill-name/
git commit -m "Add skill-name skill for team use"
git push

# Team members get it automatically
git pull

When to Use Each Scope

Use Personal Scope When:

• You want the skill in all your projects
• The skill contains personal API keys
• You're testing before sharing
• It's a personal productivity tool

Use Project Scope When:

• The whole team should use it
• It's specific to this codebase
• You want version-controlled skills
• Onboarding should include it

Common Patterns

Pattern 1: Personal Development, Then Share

# 1. Install to personal scope for testing
cp -r skill-name ~/.claude/skills/

# 2. Test and customize

# 3. Move to project scope when ready
cp -r ~/.claude/skills/skill-name .claude/skills/
rm -rf ~/.claude/skills/skill-name
git add .claude/skills/skill-name/
git commit -m "Share skill-name with team"

Pattern 2: Fork and Customize

# 1. Install from library to personal
cp -r lib/skills/whatsapp ~/.claude/skills/

# 2. Customize SKILL.md for your needs
edit ~/.claude/skills/whatsapp/SKILL.md

# 3. Your customizations persist

Pattern 3: Team Standard Override

# Project has a skill, but you want different behavior
# 1. Install same skill to personal scope
cp -r lib/skills/skill-name ~/.claude/skills/

# 2. Personal scope takes precedence
# Your version is used instead of project version

Environment Variables and Secrets

Personal Scope Secrets

# .env files in personal scope are safe
~/.claude/skills/whatsapp/.env  # Only you can access

Project Scope Secrets

# NEVER commit .env to project scope!
# Add to .gitignore
echo ".claude/skills/*/.env" >> .gitignore

# Use .env.example for templates
.claude/skills/whatsapp/.env.example  # Committed, no secrets
.claude/skills/whatsapp/.env          # Gitignored, local secrets

Verifying Skill Location

# Check personal skills
ls ~/.claude/skills/

# Check project skills
ls .claude/skills/

# Find all skills
find ~ -name "SKILL.md" -path "*/.claude/skills/*" 2>/dev/null

Migration Between Scopes

Personal to Project

SKILL=my-skill
cp -r ~/.claude/skills/$SKILL .claude/skills/
git add .claude/skills/$SKILL/
git commit -m "Add $SKILL to project scope"

# Optionally remove from personal
rm -rf ~/.claude/skills/$SKILL

Project to Personal

SKILL=team-skill
cp -r .claude/skills/$SKILL ~/.claude/skills/
git rm -r .claude/skills/$SKILL
git commit -m "Move $SKILL to personal scope"