Hand off the current Claude Code session to Codex as a resumable thread with full turn history, then continue outside Claude entirely. Use when asked "codex transfer", "move this session to codex", "continue this in codex", "hand this off to codex", or wants to migrate the conversation itself (not delegate one task…
Verify a plan or document using Codex as independent reviewer with PASS/FAIL verdict. Use when asked "codex verify", "verify this plan", "review this doc for issues".
Run E2E browser tests from natural language JSON test files using agent-browser. Use when asked to run e2e tests, browser tests, UI tests, end-to-end tests, or test a web application.
Queries NotebookLM notebooks in Chrome to extract responses. Use when the orchestrating skill provides a NotebookLM URL and question. The notebooklm-manager skill resolves notebook names to URLs before invoking this agent.
Manages NotebookLM notebooks — query, add, list, search, enable/disable, remove. Use when a notebooklm.google.com URL appears or user mentions NotebookLM. Handles URLs through its own Chrome agent — do not navigate directly. Requires: claude-in-chrome MCP.
Rubber duck tutor that keeps you sharp across the whole AI-coding lifecycle, not just after code lands: /duck-prebuild before you ask AI to build, /duck-verify and /duck-review once it's written and before you ship, /duck-orient when you're new to a codebase, plus /duck for auto-detect. /coach is its teaching sibling…
Senior-engineer coaching session: explains a topic in plain language with one concrete analogy then walks example → exercise → critique; or dissects code just generated in this session section-by-section (what it does / why this way over the obvious alternative / where it breaks first in prod); or surfaces an…
Codebase-orientation session with the rubber duck — generate or refresh .claude/orientation.md with interactive exercises. Use when new to a codebase, returning after a break, or says "duck orient", "I'm new to this repo".
Pre-build session with the rubber duck — runs BEFORE implementation, covering both a pre-coding design sketch and plan/spec review. Use when the user states implementation intent ("build this for me", "build me X") with no plan or code yet, when a plan/spec/RFC was just produced, or says "duck design", "duck plan"…
PR/change-review session with the rubber duck — user justifies every change and predicts consequences. Use before commit/push/PR, or when they say "duck review", "check before review". Not for code-level explanation (/duck-verify) or plan review (/duck-prebuild).
Code-verification session with the rubber duck — user explains code just written, finds edge cases, fixes planted bugs. Use after implementing a feature, or when they say "duck verify", "double check this". Not for plan review (/duck-prebuild) or PR review (/duck-review).
Rubber duck tutor — auto-detects which review mode to run. Use when the user says "duck", "tutor", "quiz me", "do I understand this", or mentions rubber-stamping or learning while coding. For a specific phase use /duck-prebuild, /duck-verify, /duck-review, or /duck-orient.
Create, test, and iteratively improve Claude Code skills with the official lean coaching loop, an eval harness for benchmarking with variance analysis, and automated description-trigger optimization.
Autonomously optimize any Claude Code skill by running it repeatedly, scoring against binary evals, mutating the prompt, and keeping improvements. Use when: optimize/improve/benchmark/eval a skill, autoresearch, auto-optimize. Not for creating skills from scratch (use skill-creator-pro).
Create new skills, modify and improve existing skills, and measure skill performance for Claude Code. 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…
Extract hardcoded secrets from CLAUDE.md, .mcp.json, and project config into a gitignored env file, then wire a SessionStart hook to load them automatically. Use when user says "separate secrets", "extract API keys", "secret setup", "env var setup", "hardcoded credentials", ".env setup for Claude", "load secrets via…