← ClaudeAtlas

jeffallan-skillslisted

Reference to the Jeffallan/claude-skills bundle (66 full-stack pair-programmer skills covering backend, frontend, infrastructure, testing, security, documentation). Use as a catalog to cherry-pick individual skills — do NOT install all 66 at once, the context bloat is significant.
izo/Ulk · ★ 1 · Testing & QA · score 68
Install: claude install-skill izo/Ulk
# Jeffallan Claude Skills (bundle, cherry-pick reference) The Jeffallan/claude-skills repo ships **66 full-stack skills** — backend, frontend, infrastructure, testing, security, documentation. This stub is a **catalog reference**, not an auto-installer. ## Why this is a stub ulk already ships 87 specialised agents and a curated set of community skills. Auto-installing 66 more would: - Bloat the skill index Claude sees on every session. - Create overlap with ulk's specialised agents (api-builder, frontend-qa, ed209, etc.). - Make `/context-audit` warnings noisy. **Recommended approach**: read the upstream catalog, identify the **2–3 skills** that fill a real gap in your project, install only those. ## Browsing the catalog ```bash curl.md https://raw.githubusercontent.com/Jeffallan/claude-skills/main/README.md # Lists all 66 skills with one-line descriptions and folder paths. ``` ## Cherry-picking a single skill ```bash # Replace <skill-name> with the exact folder name from upstream SKILL=<skill-name> mkdir -p ~/.claude/skills/jeffallan-$SKILL curl.md https://raw.githubusercontent.com/Jeffallan/claude-skills/main/$SKILL/SKILL.md > ~/.claude/skills/jeffallan-$SKILL/SKILL.md ``` (Prefix with `jeffallan-` to avoid name collisions with ulk-bundled skills.) ## Routing rule When you'd consider a Jeffallan skill, first check ulk's coverage: | Domain | ulk's coverage | |--------|----------------| | Backend/API | `happy` (49) — OpenAPI doc generator; `api-builder` agents |