Skill Claude Code
QA engineer that smoke-tests changes in the browser, validates behavior, plans fixes or test gaps, and updates documentation. Acts as a "second dev" focused on testing what was built. Use when ready to validate work before committing. Trigger on phrases like "qa", "smoke test", "test this", "validate", "check my…
Skill Claude Code
Save session learnings to the Obsidian vault. Use at the end of a work session to capture what was learned, decided, or discovered. Trigger on phrases like "recap", "save session", "what did we learn", "wrap up".
Skill Claude Code
Code review in 2 modes. Autonomous (default): spawns parallel security/performance/quality reviewers + red-team auditor, presents verdict. Pair: walks changed files one-by-one with you, collects comments, posts only on approval. Accepts prompt, GitHub/Linear URL, PRD path, or no args. Use when: review, code review…
Skill Claude Code
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Skill Claude Code
Discovery before building. Reproduce and observe real behavior, collect evidence, close a mini bag of 1-3 small issues. Use when the ask is fuzzy: a vague bug, "is this at parity?", a feature idea, "migrate X". Feeds /step or /pair, which ride the bag.
Skill Claude Code
Work in the smallest next step, staying in the loop. Browser-first RED, TDD, evidence, before/then. Handles refining a requirement, researching alternatives, or building — and switches between them as the task shifts. Keeps a tiny optional buffer. Output stays short and critical. Use when: step, let's build this, next…
Skill Claude Code
Scout the current project, diff against existing CLAUDE.md and .claude/rules, propose updates to reflect stack and conventions. Idempotent. Does not copy user-level skills or agents (user-level always wins). Use when: sync, forge, tune, init project, bootstrap, prepare project, refresh rules.
Skill Claude Code
Test TUI applications using tu (terminal-use). Launch apps in virtual terminals, take screenshots, type text, press keys, wait for conditions, and verify output. Use for smoke testing terminal UIs, interactive CLIs, and TUI apps. Trigger on phrases like "test the TUI", "terminal test", "tu test", "test in terminal"…
Skill Claude Code
Search and retrieve notes from the Obsidian vault. Use when the user wants to find notes, recall past ideas, get context on a topic, look up references, browse blog drafts, get live stream ideas, consolidate notes for writing, or load knowledge from their second brain into the conversation. Trigger on phrases like…
Skill Claude Code
Navigate a code review in chunks, with the user. Works on a PR (theirs or a colleague's) or on uncommitted work, across repos. Each chunk is one reviewable decision: surface affected, before/after, the call made, security/perf/quality flags, and blind spots. Feedback accumulates in an annotation bag; ends in a staged…
Skill Claude Code
Learn a subject on demand, problem first. Takes a prompt, link, snippet, screenshot or a previous masterclass and teaches it by socratic questioning, one question per turn, until the user reaches the solution themselves. Ships as a quick one-shot, a single topic, or a multi-topic class. Runs in the terminal, ships an…
Skill Claude Code
Team-lead orchestration of a multi-unit goal with PERSISTENT agents — spawn one agent per track, keep it alive across units, talk to it by message instead of re-briefing from scratch. Wrapper over the /goal stop-hook: crew is the engine, /goal is the safety net. Use when the user says: crew, run this goal, roda o…
Skill Claude Code
Authorized security assessment of the user's own project, any stack: map the repository and the running system, classify every component (web app, API, native app, daemon or socket, CLI or binary, runner or CI, containers and infra, database, media server, supply chain, data at rest), ask the scoping questions, route…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: