Skipper for Salesforce

Skipper is a keyboard-first command palette for Salesforce admins, developers, architects and consultants. Press Cmd+Shift+K (Mac) or Ctrl+Shift+K (Windows/Linux) on any Salesforce page to jump anywhere in your org. FIND ANYTHING IN YOUR ORG, INSTANTLY Press Cmd+Shift+K / Ctrl+Shift+K anywhere in Salesforce to fuzzy-search every object, flow, app. - @object — jump straight to Fields & Relationships, Validation Rules, Page Layouts, Triggers, Record Types - @flow — browse every active and inactive flow - @app — jump to any Lightning app - @cmd — open Custom Metadata records or definitions - @label — search Custom Labels by name, API name, or value - @user — look up any org user - @permset — open any permission set by name - @setup — filter the full Setup pages registry without leaving the palette GROUNDED AI, NOT A GUESSING GAME Ask a generic LLM about your org and it hands you confident answers about fields, flows, and queries that don't exist. Skipper goes the other way: every AI feature pulls live context from your org, real field API names, picklist values, flow metadata, Apex source. - @ask — screenshots any page and ask what's going on; the model runs read-only SOQL, describes, and source searches to answer from your actual org, not a guess - @soql — describe a query in plain English and get back a SELECT that only uses fields that really exist, validated against the Salesforce planner - @debug — paste a Flow debug log and get a summary, root cause, and suggested fix, grounded in the flow's real metadata - Bring your own key — Gemini, Claude, or ChatGPT, Openrouter WORKS ACROSS ORGS, NO SETUP - Switch from a prod tab to a sandbox tab and Skipper automatically follows — separate caches, separate session, same shortcut - Works in production and sandboxes alike - Uses your existing access — Skipper acts as your logged-in user, so it only sees what your profile already allows. @debug and @ask read Flow and Apex source via the Tooling API PRIVACY AND SECURITY - Strictly read-only — no DML, no anonymous Apex, no metadata writes, enforced at the network layer - No backend, no analytics, no telemetry — your data stays in your browser - Your API key is stored locally and never touches infrastructure we control - AI providers only see a prompt when you actively use an AI feature, and only if you've configured a key