Bulk data enrichment. Adds web-sourced fields (CEO names, funding, contact info) to lists of companies, people, or products. Use for enriching CSV files or inline data. Supports multi-turn: pass --previous-interaction-id from a prior research task to carry context forward.

Track parcels and check delivery status for Australian and international couriers. Searches Gmail for dispatch/shipping emails and provides tracking links for all major Australian couriers including AusPost, StarTrack, Aramex, CouriersPlease, Sendle, Toll, Team Global Express, DHL, FedEx, TNT, Hunter Express, Border Express, Direct Freight Express, and UPS. Triggers: 'where is my parcel', 'track my order', 'has my package arrived', 'tracking status', 'check tracking', 'where is my delivery'.

Use when revising existing implementation plans, analyzing impact of task changes, exploring modifications to project scope or dependencies, or updating task hierarchies with full impact visibility before execution.

Query R package documentation across all ecosystems at once (CRAN, tidyverse, Bioconductor). Use this skill when: - Looking up R package usage, functions, or vignettes - Comparing packages for the same task (e.g., data.table vs dplyr) - User says "R docs", "how to use this R package", or asks about R functions - Need to find the right R package for a task

Generate a Ralph backlog for a new feature. Use when planning a feature, starting a new project, or when asked to create tasks. Triggers on: create tasks, write prd for, plan this feature, requirements for, spec out, generate TODO-next.md, use the ralph-prd skill.

Use when a task fails, an approach does not work, when encountering errors during implementation, or when tempted to say "I cannot do this" - ensures retry with at least 3 genuinely different approaches before escalating

Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Only activate in MSBuild/.NET build context. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.

Expert GNU sed one-liner generation and transformation. Use this skill whenever the user asks to transform text, edit files in-place, refactor code via CLI, process logs, do bulk find/replace, extract lines, delete patterns, or perform any stream editing task. Trigger on keywords like "sed", "replace in files", "find and replace", "edit in place", "strip lines", "extract pattern", "log filtering", "batch rename content", "remove lines matching", "transform output", or any request that maps to a sed one-liner or pipeline. When in doubt, use this skill — sed is often the right tool.

Comprehensive SessionStart hook showing PhD countdown, project status, uncommitted changes, and loaded todos.

A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

Use when reading Slack messages, searching conversations, sending messages, listing channels, or interacting with Slack workspaces

3. Create Task List

Task lifecycle state transitions with validation gates. Defines states, triggers, and required proofs.

Tasker docstore task management via tool-dispatch. Use for task lists, due today/overdue, week planning, add/move/complete, or explicit /task commands.

This skill should be used when the user asks to "initialize taskwarrior", "set up taskwarrior", "configure taskwarrior for this project", "run /init for taskwarrior", "set up task management", "bootstrap the task plugin", "configure task contexts", or "first-time taskwarrior setup". Guides the complete initial configuration of Taskwarrior so that the task-workflow skill operates correctly.

Manages Dots task tracking with the dot CLI, dependencies, and completion reasons. Use when tracking work items across sessions or coordinating task dependencies.

Use this skill when implementing any feature, bug fix, or plan task. Triggers on "write tests", "add a test", "do TDD", "test-driven", "implement with tests", "implement task", or when dispatched as a subagent for plan execution. Write test first, watch it fail, write minimal code to pass.

Manage Todoist tasks. Use when the user mentions "todoist", "my tasks", "task list", "add a task", "complete task", or wants to interact with their Todoist account.

Travel destination research and daily itinerary creation with logistics planning, budget tracking, and experience optimization. Use when planning trips, creating travel itineraries, comparing destinations, or organizing travel logistics.

Validate a task, gauge its impact, and decide what to do with it

Use when claiming task completion or marking items as done. Covers completion evidence requirements, verification methods, and anti-rationalization patterns.

Use before claiming any task is complete, any feature works, or any bug is fixed - enforces fresh verification evidence through a 5-step HARD-GATE protocol that prevents false completion claims

This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations.

Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

Graph-aware task triage with bv and br. Use when prioritizing work, finding bottlenecks, tracking dependencies, or managing local issues across projects.

Track and manage work items, tasks, issues, and todos with dependencies using bits. Use when user needs to create tasks, track progress, manage blockers, find ready work, claim/release tasks, close completed work, or organize multi-step projects. Triggers on "bits", "task", "issue", "backlog", "blockers", "dependencies", "what's ready", "track this", "add to my list", "what should I work on".

Create feature branches with naming conventions, load full issue context and impact analysis, and decompose acceptance criteria into atomic parallel tasks with dependencies. Use when starting work on a GitHub issue. This skill MUST be consulted because starting code without context causes misaligned implementations and wasted effort.

Prepare for a sales call with account context, attendee research, and suggested agenda. Works standalone with user input and web research, supercharged when you connect your CRM, email, chat, or transcripts. Trigger with "prep me for my call with [company]", "I'm meeting with [company] prep me", "call prep [company]", or "get me ready for [meeting]".

Meta-cognitive decision support that analyzes current context and surfaces intelligent next-step options to the user. Use this skill when: (1) User explicitly invokes /checkpoint, (2) Significant work has been completed and a checkpoint is valuable, (3) Uncertainty or ambiguity exists about requirements or approach, (4) Task complexity has expanded beyond initial scope, (5) Before finalizing or committing to ensure nothing is missed. This skill pauses execution, assesses the situation holistically, and presents 2-5 contextually-appropriate options via AskUserQuestion, with a recommended option and rationale.

Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.

Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.

Teaches the command pattern for decoupling task execution from invocation. Use when you need undo/redo functionality, queued operations, or want to decouple the object that invokes an operation from the one that performs it.

Creates semantic git commits with conventional commit format, stages changes, and pushes to remote. Handles pre-commit hooks and writes meaningful commit messages. Make sure to use this skill whenever the user says "commit", "push changes", "save to git", "commit this", or wants to create a git commit — even if they just say "save my work." Also proactively offer after any implementation task wraps up.

Complete all TODO-marked code in specified area with test-first approach. Use when finishing incomplete implementations, converting TODO placeholders to working code, or completing test-driven development cycles.

Drives the cortex skills recommend-feedback-rate loop. Use when a context change occurs (new file types, domain shift, task pivot) or when a task completes and skill effectiveness should be recorded.

Search and discover R packages on CRAN by topic or task. Use this skill when: - User needs to find R packages for a specific task - Looking up CRAN Task Views for a domain - Checking package dependencies or reverse dependencies - Comparing packages for the same purpose - User says "what R package for...", "find an R package", "CRAN search"

Structured data research: search sources, extract structured data, archive raw sources, maintain canonical tracker pages, deduplicate. Parameterized via YAML recipes for investor updates, donations, company updates, or any email-to-structured-data pipeline.

Sync Docusaurus markdown docs to Confluence, Google Docs, or Notion using docflu CLI. Use when syncing documentation, setting up docflu config, converting diagrams (Mermaid/PlantUML/D2/Graphviz) for Confluence, or managing doc sync workflows. Triggers on 'sync docs', 'push to confluence', 'docflu', 'confluence sync', or when .env contains CONFLUENCE_BASE_URL/DOCFLU_ variables.

Create Domino Launchers - parameterized web forms for self-service job execution. Enable business users to run analyses, generate reports, and trigger batch predictions without coding. Covers parameter types, email notifications, result delivery, and access control. Use when building self-service data products or enabling non-technical users.

Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".

Implements a single task following the next → implement → check → done workflow with TDD support. Use when working on one specific task, implementing a single feature from the backlog, or following TDD red-green-refactor cycle. Triggers on 'next task', 'next feature', 'implement feature', 'work on feature', 'single task mode', 'what should I work on'.

This skill should be used when managing the file-based todo tracking system in the todos/ directory. Triggers on requests like "create a todo", "update todo status", "manage todos", "check todo dependencies".

Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1, fn-1.2) or file paths.

Google Chat: Manage Chat spaces and messages.

Google Workspace Reseller: Manage Workspace subscriptions.

Implements asynchronous programming patterns using Task, ValueTask, and ConfigureAwait in .NET. Use when building non-blocking I/O operations or improving application responsiveness.

Issue tracking and task management using the hive system. Use when creating, updating, or managing work items. Use when you need to track bugs, features, tasks, or epics. Do NOT use for simple one-off questions or explorations.

Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.

Autonomous implementation loop over a focus topic. Reads active scopes, enumerates tasks as todos, then iterates the TDD pipeline (tester→implementer→reviewer) until all tasks are complete. Use when autonomously implementing all pending work for a scope or topic without manual step-by-step oversight.

Creates or enriches entity notes for people in /04-Entities/ from available context — current conversation, Granola meetings, Gmail threads. Use when someone is mentioned and worth noting, or when explicitly asked to create or update a person note.

Export the default plan or spec template to your project's plans/ folder for customization. Supports "plan" and "spec" template types.

Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.

This skill should be used when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Implements Manus-style file-based planning with task_plan.md, findings.md, and progress.md.

Convert PRDs to prd.json format for ralph-tui execution. Creates JSON task files with user stories, acceptance criteria, and dependencies. Triggers on: create prd.json, convert to json, ralph json, create json tasks.

Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Git-aware logical undo at track, phase, or task level with confirmation gates

Review pull requests against task specifications. Use when user wants a code review, PR review, or says "review PR", "review this PR", "check my PR", "code review", "review changes", "is this ready to merge". Reads the task spec and branch diff, verifies acceptance criteria are met, checks test coverage, identifies issues, and produces a structured verdict (approve/request changes).

Executing a phased plan from ring:writing-plans in rolling waves: implements the detailed phase task-by-task with TDD and signed commits via ring:committing-changes, checkpoints at each phase boundary, then elaborates the next phase. Use when a phased plan exists and inline execution is preferred over subagent orchestration. Skip when no plan exists (use ring:writing-plans) or a tasks.md dev cycle is wanted (use ring:running-dev-cycle).

Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted burden of proof. Use for pre-public or post-pivot cleanup. Skip for current diff review (use ring:reviewing-code).

Use when the user wants to divide up, assign, or distribute unscored Jira tickets from the SAAS deet week board (board 252) for scoring/grooming. Triggers on phrases like "score deet week", "split up the unscored tickets", "divide unscored tickets", "assign tickets for scoring", or "who should score these". Mobile tickets always go to Ahmad; the rest get split evenly among the other Platform devs. Posts the result to Slack

Retrieve and summarize full order details for a customer by email, order number, or phone number.

Splits a multi-line fulfillment order into separate shipments for partial or location-specific shipping.

Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type

Improve existing skills after use. When Claude uses a skill and discovers issues (outdated steps, missing edge cases, unclear instructions, wrong assumptions), suggest "/skill-improve" after the current task completes. Also use when user says "fix this skill", "this skill is wrong", "update skill", or "/skill-improve <skill-name>".

Interactive setup wizard for Slack plugin. Guides users through obtaining and configuring Slack credentials (workspace, token, cookie) from their browser session.

Validates Slack configuration and credentials. Checks if config exists, credentials are present, and authentication is working. Used internally by other Slack skills.

Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates

Parse handover notes and auto-resume write-code workflow. Use when continuing interrupted work, resuming from handover documents, or picking up another developer's task.

Parallel execution engine for high-throughput task completion

Execute implementation tasks with quality and awareness. Use when: (1) After TASKS phase in 5D-SDD workflow, (2) Tasks are defined and sequenced, (3) User is ready to write code, (4) User asks to 'implement,' 'build,' or 'code' a task. This phase produces working code while maintaining connection to spec intent.

Break gap analysis into sequenced, actionable tasks. Use when: (1) After GAP ANALYSIS phase in 5D-SDD workflow, (2) User is ready to start implementation, (3) Gaps are identified but not yet organized into work items, (4) User asks for 'task list,' 'breakdown,' or 'what to do first.' This phase creates the implementation roadmap.

This skill should be used when the user mentions "bd", "beads", "what's next", "add task", "add epic", or asks about issue tracking. First check if a .beads directory exists in the project - if not, this skill does not apply.

Your intelligent developer command center -- start here for any Python, wxPython, desktop app, NVDA addon, accessibility tool building, desktop accessibility, or general software engineering task. Routes to specialist agents across the developer, web, and document accessibility teams. Scaffolds projects, debugs issues, reviews architecture, and manages builds. No commands to memorize. Just talk.

Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.

creates draft task file in .specs/tasks/draft/ with original user intent

Scaffold a new adhoc work item under Active\<slug>\ with the standard issue shape but no Jira link. Accepts either explicit `<slug> "<title>"` or a free-form task description (slug + title are inferred and confirmed).

Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders.

Start self-referential development loop until task completion

Autonomous task implementation - research, plan, build, review, fix, ship

Query and manage macOS Calendar events. Use when the user asks about calendar events, appointments, schedules, or wants to create/modify calendar entries.

Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary

Split oversized task into smaller tasks with proper dependency management

Surface code-level debt — TODO/FIXME markers, deprecated APIs, dead code, oversized units, magic numbers. Use when reviewing a module, planning cleanup work, or before a release. Not a linter — observes patterns and assesses impact.

Build a comprehensive customer profile from Intercom data, including conversation history, account context, and interaction timeline. Use when the user asks to "look up a customer", "customer profile", "customer 360", "tell me about this customer", "summarize a customer's history", or provides a customer email or company name and wants a full picture.

Structured development workflow with analysis, implementation, validation, and mandatory checkpoint before commit/push. Use when starting a new feature, bug fix, or refactoring task.

This skill should be used when the user mentions "dots", "dot", "tasks", "task", "todo", "issue", "track", "plan", "breakdown", or asks about task management. Provides guidance for using the dots CLI task tracker.

Generate professional email templates for various business scenarios including sales outreach, customer support, internal communications, follow-ups, and apologies. Creates personalized, tone-appropriate templates with subject lines and formatting. Use when users need to write business emails, cold outreach, or professional communications.

Model routing rules for codebase search. Delegates search/exploration to cheaper models (Haiku/Sonnet) while keeping Opus as the orchestrator. Invoke this skill before any codebase search or exploration task.

Use this skill when planning and designing gridfinity baseplates for 3D printing. This includes calculating optimal grid sizes from given measurements, determining how to slice large grids into printable chunks based on printer bed dimensions, and calculating padding requirements for non-exact fits. The skill handles both metric and imperial measurements and provides guidance for using gridfinity.perplexinglabs.com to generate the actual STL files.

Use the `gws` CLI to interact with Google Workspace services — Gmail, Drive, Sheets, Calendar, Docs, Tasks, Chat, and more. Trigger this skill whenever the user wants to read/send email, manage Drive files, update spreadsheets, check calendars, create tasks, send Chat messages, or run any Google Workspace operation. Also trigger when the user mentions Google Workspace, Google APIs, or asks to automate anything across Gmail/Drive/Sheets/Calendar/Docs/Tasks/Chat. Use this skill even when the request seems simple — gws can handle it in one command.

Google Calendar: Manage calendars and events.

Google People: Manage contacts and profiles.

Implements tasks from .plans/ directories by following implementation guidance, writing code and tests, and updating task status. Use when task file is in implementation/ directory and requires code implementation with comprehensive testing. Launches research agents when stuck.

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units