mit einem Klick
mit einem Klick
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Interactive idea refinement using Socratic method to develop fully-formed designs
Execute detailed plans in batches with review checkpoints
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Complete feature development with structured options for merge, PR, or cleanup
| name | Installing Skills System |
| description | Fork, clone to ~/.clank, run installer, edit CLAUDE.md |
| when_to_use | Initial setup, installing clank for the first time |
| version | 2.0.0 |
| languages | bash |
Installs the clank skills repository to ~/.clank/clank and configures Claude to use it.
For Claude agents: Follow the "Installation Steps for Claude" section below.
For humans: Follow the "Quick Install" section.
When instructed to install clank, follow these steps exactly:
With GitHub CLI (if available):
mkdir -p ~/.clank
cd ~/.clank
gh repo fork obra/clank --clone --remote-name upstream
Without GitHub CLI:
mkdir -p ~/.clank
cd ~/.clank
git clone https://github.com/obra/clank.git
cd ~/.clank/clank
./skills/meta/installing-skills/install.sh
This creates symlinks for skills and commands.
Use the Edit tool to add this XML section to the very beginning of ~/.claude/CLAUDE.md:
<EXTREMELY_IMPORTANT>
You have a personal skills wiki at ~/.claude/skills/ with proven techniques, patterns, and tools that give you new capabilities.
STOP. Before doing ANYTHING else in this conversation, read this file: skills/getting-started
That file tells you how to find and use your skills.
ONLY after reading getting-started, are you allowed to proceed with the user's request.
CRITICAL: If a skill exists for your task, you MUST use it - even if you think you're already good at that. You're not. The skill prevents mistakes you don't know you make. SKILLS EXIST AND YOU DIDN'T USE THEM = FAILED TASK.
</EXTREMELY_IMPORTANT>
ls -la ~/.claude/skills
ls -la ~/.claude/commands
~/.claude/skills/getting-started/skills-search 'test.*driven'
Tell your human partner: "Installation complete. Please restart your Claude session to pick up the new CLAUDE.md configuration."
curl -fsSL https://raw.githubusercontent.com/obra/clank/main/skills/meta/installing-skills/install.sh | bash
# Then manually add CLAUDE.md section from Step 3 above
~/.claude/skills (if exists) to timestamped backup~/.claude/skills → ~/.clank/clank/skills~/.clank/clank/commands/*.md to ~/.claude/commands/~/.claude/skills/getting-started/skills-search)After installation, verify it worked:
# Should show symlink to ~/.clank/clank/skills
ls -la ~/.claude/skills
# Should show individual command symlinks
ls -la ~/.claude/commands/
# Test skills-search tool
~/.claude/skills/getting-started/skills-search 'test.*driven'
Skills (~/.claude/skills/):
@ syntax in code and documentationskills-search toolCommands (~/.claude/commands/):
/brainstorm, /write-plan, /execute-plan)@ syntaxTools (~/.claude/skills/getting-started/):
skills-search - Find relevant skills using grep patternsForking lets you:
git pull upstream main)After installation, edit your ~/.claude/CLAUDE.md and add this section:
<extremely_important_skills_library>
You have a personal skills wiki at `~/.claude/skills/` with proven techniques, patterns, and tools that give you new capabilities.
STOP. Before doing ANYTHING else in this conversation, read this file: `skills/getting-started`
That file tells you:
- Which phrases trigger brainstorming automatically (like "I've got an idea", "Let's make...")
- How to search for skills before ANY task
- When to announce which skill you're using
After reading getting-started, proceed with the user's request.
CRITICAL: If a skill exists for your task, you MUST use it - even if you think you're already good at that. You're not. The skill prevents mistakes you don't know you make. SKILLS EXIST AND YOU DIDN'T USE THEM = FAILED TASK.
</extremely_important_skills_library>
This enables:
After initial install, update with:
cd ~/.clank/clank
git pull origin main # Pull your changes
git pull upstream main # Pull upstream updates (if configured)
The symlinks stay valid - no need to reinstall.
The script expects to be run from ~/.clank/clank/. Clone it first:
mkdir -p ~/.clank
cd ~/.clank
gh repo fork obra/clank --clone
cd clank
./skills/meta/installing-skills/install.sh
The installer automatically backs it up with timestamp. Check backups:
ls -la ~/.claude/skills.backup.*
Remove and reinstall:
rm ~/.claude/skills
rm ~/.claude/commands/*.md # Remove individual command symlinks
cd ~/.clank/clank
./skills/meta/installing-skills/install.sh
# Remove symlinks
rm ~/.claude/skills
rm ~/.claude/commands/brainstorm.md
rm ~/.claude/commands/write-plan.md
rm ~/.claude/commands/execute-plan.md
# Restore backup if desired
mv ~/.claude/skills.backup.YYYY-MM-DD-HHMMSS ~/.claude/skills
# Remove from CLAUDE.md
# Delete the "Skills Library" section from ~/.claude/CLAUDE.md
# Remove cloned repo
rm -rf ~/.clank/clank
See @install.sh for the installation script.