Guides installation of AVIZ Skills Library skills into Claude Code via user (~/.claude/skills) or project (.claude/skills) directories using git clone/copy, npm deps, and real-time doc fetching.
npx claudepluginhub aviz85/claude-skills-library --plugin aviz-skills-installerThis skill uses the workspace's default tool permissions.
A conversational guide to installing skills from the AVIZ Skills Library.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A conversational guide to installing skills from the AVIZ Skills Library.
DO NOT use hardcoded skill lists. Always fetch current data from these sources:
Use WebFetch or WebSearch to get the latest available skills and their setup instructions.
Ask the user what they want:
Use WebFetch on https://aviz.github.io/claude-skills-library/ to get the current list of skills.
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
# 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"
cd DESTINATION/SKILL_NAME/scripts
npm install 2>/dev/null || true
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
Each skill in the library MUST have:
docs/skills/{skill-name}.htmlSkills requiring API keys should include:
.env.example file with required variables