Read data from a Google Sheet and create a formatted Google Docs report.

Apply Gmail labels to matching messages and archive them to keep your inbox clean.

Create a Google Drive folder structure and move files into the right locations.

Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.

Move a Google Calendar event to a new time and automatically notify all attendees.

Find Gmail messages with attachments and save them to a Google Drive folder.

Share a Google Docs document with edit access and email collaborators the link.

Share a Google Drive folder and all its contents with a list of collaborators.

Feature engineering patterns with recipes, including imputation, encoding, normalization, interactions, and leakage control.

Set up the initial file system for a new sandbox. Fetches the account's organizations and artists via the Recoup REST API and scaffolds the folder structure. Use when a sandbox has just been created and has no existing file system. Before running, check if the sandbox already has an orgs/ directory — if it does, this skill is not needed.

Generate all valid arrangements using backtracking with pruning. Use when solving permutations, combinations, subsets, N-queens, sudoku, or constraint satisfaction problems.

Refactors code to improve readability, reduce complexity, and enhance maintainability without altering functionality. Use when the user says "refactor", "simplify this code", "clean up", "reduce complexity", "extract method", "this is too complex", or asks to improve naming/structure without changing behavior. Preserves all public APIs unless explicitly authorized.

Improve the shape of existing code without changing behavior.

Guide safe, incremental refactoring that improves code quality without changing behavior.

Guide for safe and effective code refactoring. Focuses on improving code structure without changing external behavior. Covers patterns like extraction, inlining, and naming improvements.

Format professional references properly and prepare reference materials

Fix grammar, spelling, and cut filler in writing without rewriting. Use when asked to "proofread", "edit my writing", "fix grammar", "clean up this text", or to copy-edit a document.

Pattern recognition across your product decisions. Analyzes saved strategy sessions to surface themes, recurring risks, and suggested next steps.

When evidence is missing, write a structured REFUSAL.md and stop. No override, no force-complete. Refusal is a feature.

Automates releases and package publishing with changesets or semantic-release. Handles versioning, changelog generation, git tags, and release notes. Use for "release automation", "semantic versioning", "package publishing", or "changelog generation".

Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills.

Ground answers in the repository by reading relevant files, configs, and code paths. Use when the user asks to modify/debug code, configuration, CI/CD, or wants repo-specific reasoning.

Detect active repos by the owner not cloned locally and request confirmation before acting

Save and load timestamped reports. Keyword routing for fast lookup. Cron jobs save output as reports; the agent or user queries them by keyword.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Fetch productivity data from RescueTime. Use when the user asks about their screen time, productivity score, app usage, time tracking, how they spent their day/week, or wants reports on their computer activity. Requires API key in TOOLS.md or passed directly.

Read-only external knowledge gathering via ODIN's 5-tier doc ladder (Official docs → API refs → Books/papers → Tutorials → Community). For library APIs, framework behavior, SDK migrations, version-specific docs, vendor announcements, RFCs. Verifies claims against primary sources. Invoke on "how does X library work", "migration guide", "docs for", or any named library/framework/SDK/API/CLI/service.

How to conduct good research and write exploitable reports, whatever the format of the sources and of the final report

Use this when starting a new research project or managing a complex, multi-step research workflow.

Thorough multi-angle research exploration with evidence requirements and structured output

Helps transform a vague research interest into a concrete, tractable research question. Use when asked to refine a research idea, develop a research question, scope a research project, or figure out what to work on. Walks through systematic refinement with feasibility analysis.

Synthesize user research into themes, insights, and recommendations

Research topics via web search, synthesize detailed summaries with sources and screenshots

Gather standards, best practices, applicable criteria before validation planning. Maps standards (WCAG, HIG, security) to Shannon validation skills.

Search the web using Perplexity AI. Use when needing to search, look up, research, find current information, best practices, compare technologies, or answer factual questions about tools and libraries.

Manage received (inbound) emails and attachments via Resend API. Use when user asks about their emails, received messages, or email attachments.

MCP Response Analyzer pattern - Write large responses to temp files, load summaries into context

Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.

Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.

Ensure ATS-friendly formatting and create clean scannable layouts

Find opportunities to add metrics and estimate numbers when exact data unavailable

Track different resume versions, maintain master resume, manage tailored versions

This skill enables Claude to act as a specialist in Retail Media Networks. Use when a user asks for help with advertising on platforms like Amazon Advertising, Walmart Connect, or other retailer websites. It helps with strategy, execution, and optimization of retail media campaigns.

Retro Vern - We solved this with cron jobs and a CSV in 2004. Grizzled veteran, historical perspective.

Debug and emulate specific code fragments or functions using the Unicorn engine. Activate when the user wants to emulate a function with Unicorn, trace binary execution without running the full program, decrypt or decode data by emulating the algorithm, or bypass environment dependencies (JNI, syscalls, libc) during emulation.

Review and critique a scientific manuscript, identifying critical issues with detailed explanations and recommendations. Produces a structured review with accept/revise/reject recommendation.

Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.

Configure human-in-the-loop gating for AI agent review actions in Claude Code. Use when setting up a project where an agent may post PR reviews, comments, merges, or edit CI configuration, and you want a cryptographically auditable approval trail with Cedar-enforced gates.

Review code against specs, designs, and decision compliance

Use when the user asks to "review this", "review the diff", "review my changes", "review my branch", "review against main", "open a review", or runs /review-diff. Opens the diff in a local browser for MR-style inline commenting — uncommitted changes if there are any, otherwise the committed branch vs its base — then reads the submitted comments back and addresses them.

Deep code/plan review for architecture, subtle bugs, and test quality. Use after sonnet review for thorough analysis.

Validate implementation plans against requirements and design. Use after creating a plan to ensure full coverage and no ambiguities.

Pull request review checklist.

Fast code/plan review for quality, security, and tests. Use for quick reviews before deeper analysis.

Get code review from Codex AI for implementation quality, bug detection, and best practices. Use when asked to review code, check for bugs, find security issues, or get feedback on implementation patterns.

Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for backend-only or non-UI work, or inside ring:running-dev-cycle-frontend, which already runs these in Gate 0.

Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save session', or 'context transfer'. Skip when context is minimal or work is fully complete with no resume planned.

Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.

Delegating tasks to Gandalf, a Lerian AI teammate reachable over Tailscale, and returning its response. Use when you need to publish an HTML/markdown report to Alfarrabio and get a URL, post a Slack notification, or ask Gandalf for business/product context via a full agent session. Tailscale-network only, no auth token. Skip when off the Tailscale network or the task can be done locally.

Planning the lightweight 5-gate Small Track pre-dev workflow (research, PRD with design validation, TRD, phases and epics, delivery planning) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use ring:planning-large-features instead. Plans only — no edits.

Researching codebase patterns, external best practices, framework constraints, and UX/product context into research.md (with file:line refs) before any planning document is written. Gate 0 of ring:using-pm-team; runs parallel discovery and selects a greenfield/modification/integration mode. Use before pre-dev planning a new feature or modification. Skip for trivial changes or when a recent research.md already exists.

Enforcing the RED-GREEN-REFACTOR loop: write one failing test and watch it fail, write minimal code to pass, then refactor green. Use when starting implementation of a new feature or bugfix, or writing any new production code. Requires pasted failure output as proof of RED; code written before its test must be deleted, not stashed. Skip for exploratory spikes or when only modifying existing tests.

Hardening a skill so it resists rationalization under pressure: run combined-pressure scenarios on a subagent without the skill (RED), capture excuses verbatim, write/edit the skill (GREEN), then plug loopholes (REFACTOR) until compliance holds. Use when deploying or editing a discipline-enforcing skill that an agent could rationalize away. Skip for pure reference skills with no rules to violate.

Selecting and dispatching the right Ring developer specialist agent (backend Go/TS, frontend, UI designer/engineer, Helm, frontend QA, prompt reviewer) for a technology task. Use when you need deep stack expertise and must decide which agent to invoke via the Task tool, including parallel dispatch of independent work. Skip for general code review (use ring:reviewing-code).

Using the ring-tw-team plugin and orchestrating its documentation specialists in parallel: guide-writer (guides/concepts/tutorials), api-writer (REST API reference), and docs-reviewer (quality review). Use when creating functional or API documentation, or reviewing doc quality. Skip when writing code (use dev-team) or writing plans (use pm-team).

Validating a completed task against its acceptance criteria, mapping each AC to evidence, and gating completion on explicit user sign-off (self-approval prohibited). Gate 5 of ring:running-dev-cycle / ring:running-dev-cycle-frontend, run at task cadence after ring:reviewing-code. Use when implementation and tests are done and you need approval to close the task. Skip outside a dev-cycle, or for doc-only or non-code tasks.

Writing a structured markdown dev report for a completed development epic: reads accumulated epic metrics (TDD, coverage, delivery, lint, file-size, license), computes a quality score with tiers, and records root-cause and next-cycle improvements. Use after an epic completes in ring:running-dev-cycle or when asked for a development feedback report. Skip for documentation-only epics or outside a dev cycle.

Remove a tidbit from your terminal reference

Use when implementing client-server communication in Roblox, firing events between LocalScripts and Scripts, passing data across the network boundary, syncing game state, or defending against exploits that abuse RemoteEvents or RemoteFunctions.

Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over".

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.

Teaches route-based code splitting for single-page applications. Use when different routes load distinct feature sets and you want to avoid loading all route code upfront.

myfy web routing with FastAPI-like decorators. Use when working with WebModule, @route decorators, path parameters, query parameters, request bodies, AuthModule for authentication, RateLimitModule for rate limiting, or error handling.

Benchmark agent skills by generating eval cases, comparing skill-guided vs baseline runs, and recording artifacts under skills-test/{skill-name}.

Apply ordered rules for string transformations like pig latin, atbash, or rot. Use when translating words with specific prefix/suffix rules and ordered predicate matching.

Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.

Execute all tasks in a blueprint using build-task workflow

Run Postman collection tests using Postman CLI - use when user says "run tests", "run collection", "run my postman tests", "verify changes", "check if tests pass", or wants to execute API test suites after code changes

Detects the optimal way to run KrakenD (native binary vs Docker) and provides correct execution commands

Retrieve the latest Runway API reference from docs.dev.runwayml.com and use it as the authoritative source before any integration work

Generate audio using the Runway API via runnable scripts. Supports TTS, sound effects, voice isolation, dubbing, and voice conversion.

Evaluate and maintain knowledge freshness - detect and fix stale knowledge

Use when working on Lightning Web Components — wire adapters, events, lifecycle, state, performance, testing.

Use when generating Apex tests, designing test data factories, sanitising sandbox data, or improving Apex test coverage / quality.

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Save brand knowledge to memory. Use when: persisting campaign learnings, guidelines, or competitive intel for retrieval.

Save current session progress and context to memory

Builds a comprehensive, multi-channel demand generation strategy to attract and convert a business's ideal customers. Use this skill when you need to develop a holistic marketing plan, from top-of-funnel awareness to bottom-of-funnel conversion.

Scan local repositories and compare with tracked repos

Design the Zod output schema of a Smithers <Task> as the contract between steps. Use when a step's output feeds a later step (or a branch/loop condition) and must be reliable — design the schema first, keep it minimal, and prefer typed fields over prose so downstream rendering can depend on it.