High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.
Enhanced web search and real-time content retrieval via Grok API with forced tool routing. Use when: (1) Web search / information retrieval / fact-checking, (2) Webpage content extraction / URL parsing, (3) Breaking knowledge cutoff limits for current information, (4) Real-time news and technical documentation, (5) Multi-source information aggregation. Triggers: "search for", "find information about", "latest news", "current", "fetch webpage", "get content from URL". IMPORTANT: This skill REPLACES built-in WebSearch/WebFetch with Grok Search tools.
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.
Performs multiplication correctly
Define the shared architecture for browser games across 2D and 3D. Use when the user needs engine choice, system boundaries, input strategy, asset organization, save/debug/performance structure, or shared browser-game architecture.
Build React-hosted 3D browser games with React Three Fiber and the pmndrs stack. Use when the user wants a 3D scene inside a React app, declarative scene composition, shared app state, or React-native UI coordination around a clean low-chrome 3D experience.
Review browser games with a structured playtest and frontend QA workflow. Use when the user wants smoke tests, FE review, screenshot-led QA, Playwright-style browser checks, or issue finding across 2D and 3D browser games, including obstructive HUD or overlay issues.
Summarize Slack channels and threads, draft post-ready Slack messages, and format content in Slack markdwn through connected Slack data. Use when the user wants to review unread activity, distill long threads, prepare status updates, reply in the right tone, or translate notes into Slack-ready message formatting.
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
Generate and normalize 2D sprite animations for browser games. Use when the user wants sprite sheets, animated strips, consistent character frames, or a repeatable workflow for turning one approved frame into a production-ready animation candidate.
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
Triage Outlook inboxes, summarize email threads, extract action items, and draft replies or forwards through connected Outlook data. Use when the user wants to inspect a mailbox or thread, understand the latest status, identify what still needs a response, or prepare a safe draft without sending it by default.
Design game HUDs, menus, and browser-facing frontend surfaces with intentional visual direction and protected playfield space. Use when the user needs polished game UI, low-chrome 3D overlays, menu systems, HUD hierarchy, responsive behavior, or prompt guidance that avoids generic app-like frontend output.
Manage Google Calendar scheduling, availability, and event changes through connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, schedule or reschedule events, review conflicts, or prepare clear event-change proposals with timezone-aware details.
Compare Outlook Calendar availability, review event details, and plan safe create, update, reschedule, or cancel actions through connected Outlook calendar data. Use when the user wants to inspect a schedule, compare candidate slots, review conflicts, or prepare an exact event change before applying it.
Create a polished, human-readable day brief from Google Calendar events, including a top summary, agenda table, conflict callouts, free windows, and remaining meetings. Use when the user asks for a summary of today, tomorrow, a specific day, "my schedule", "my day", an agenda, or a calendar brief and the Google Calendar app/connector from this plugin is available.
Iteratively inspect and polish connected Google Slides presentations in Codex using slide thumbnails plus raw Slides edits. Use when a user asks to fix spacing, alignment, overlap, crowding, hierarchy, or deck-wide visual consistency in Google Slides, especially when the work should follow a thumbnail -> diagnose -> batch_update -> re-thumbnail verification loop.