human-review
Present open questions to human for resolution using batched AskUserQuestion prompts, then update the specification with answers.
pr-review
Perform thorough, constructive pull request reviews using parallel specialized agents. Use when user wants to review a PR, provide code review feedback, or assess code changes. Features confidence-scored issues, validation filtering, and batched GitHub comments.
collect-for-pr
Collect pending worktree commits into a PR for review. Use this skill when subdirectory worktrees have accumulated 4-7+ commits that should be batched together and submitted for review. Invoked with /collect-for-pr or automatically when monitoring worktree status.
issue-lifecycle
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
plan-execution
Batch execution with checkpoints. Trigger: When executing plans with batched tasks.
gymnasium-vector-envs
Gymnasium vector environment API — SyncVectorEnv, AsyncVectorEnv, batched step/reset semantics, autoreset modes, and vector wrappers for parallel RL.
Amplitude Automation
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, and user identification. Always search tools first for current schemas (call RUBE_SEARCH_TOOLS first). This Skill orchestrates connection management (RUBE_MANAGE_CONNECTIONS), schema discovery, and common workflows such as sending events, retrieving user activity, managing cohorts, and identifying users. Features include batched event ingestion (events with event_type, user_id or device_id, event_properties, user_properties, and millisecond timestamps), connection activation via returned auth links, schema-driven validation, and asynchronous processing with retry-friendly patterns. Use it when integrating app telemetry, automating user analytics pipelines, or building server-side tracking without manual API calls. Core advantages are centralized orchestration, enforced schema compliance, simplified auth flows, and reduced engineering overhead—while observing pitfalls like required user/device IDs, 13-digit epoch times, and batch limits.
executing-plans
Execute an approved implementation plan in a separate session with checkpoint reviews. Use after writing-plans when the user wants batched progress updates before more work continues.