Chrome Skills vs Core

Google launched Skills for Chrome on April 14, 2026, bringing reusable AI workflows directly into the browser sidebar. The core idea is deceptively simple: any Gemini prompt you find useful can be saved as a "Skill" and triggered later with a forward slash (/) command — no copy-pasting, no re-explaining context. You can also run a Skill across multiple tabs simultaneously, or remix community Skills from Google's growing library of pre-built workflows. The Skills library covers categories like productivity, shopping, recipes, and budgeting. Power users can build multi-step workflows — summarize, translate, then draft a reply — and trigger the whole chain with a single command. Privacy-sensitive actions (adding calendar events, sending emails) require explicit confirmation. The rollout began on macOS, Windows, and ChromeOS for English-US users signed into Gemini. This matters because it's the first time a major browser has made AI-native workflows a first-class citizen, not a plugin or extension. It's also a quiet shot across Perplexity, Copilot, and any browser extension trying to bolt AI onto the web. If you're already in the Google ecosystem, this starts to make the browser feel like an operating system.

Core is an open-source "AI operating system" built around a single premise: AI should remove operational friction, not just build-time friction. While most AI tools require you to brief them every session and manually synthesize their outputs, Core ships with Alfred — a persistent, named butler agent that executes scheduled tasks autonomously and surfaces results where you already work. The philosophical distinction is between directive AI (you tell it what to do each time) and ambient AI (it runs your backlog while you focus on other things). Alfred maintains context across sessions, executes routine operations on schedule, and doesn't wait to be invoked. Think scheduled research summaries, automated triage, or recurring data pulls — tasks that currently require either expensive automation platforms or manual check-ins. The project is self-hostable via GitHub and is currently in waitlist mode for the hosted version. It's early-stage, but the architecture — a persistent agent with long-running task support and integrations into existing workflows rather than a separate chat interface — points toward a category of tooling that's been largely missing. Most AI assistants are reactive; Core is explicitly designed to be proactive.