backup
Commit and push the working directory to its private git backup repo right now. Use when the user asks to back up, save, commit, or push the workspace, or after important changes worth persisting before the next scheduled backup.
briefing
Send the day's briefing - one message with today's weather, daylight, calendar and offers. Use only when the user asks for the briefing itself ("send me the briefing", "brief me", "what does the briefing say"), not for the individual questions behind it.
diagram
Draw something and send it to the user as a picture on WhatsApp - a flowchart, a sequence, a state machine, a timeline, an entity relationship, a mind map. Use when the answer is a shape rather than a sentence - how something flows, what talks to what, what happens in which order, how a set of things relate.
files
Work with files - the ones the user sends you (a PDF, a zip, a spreadsheet, a video) and the ones you send back to them on WhatsApp. Use whenever a file arrives, whenever the user asks for something as a file or a download, and whenever something has to be moved out of a file into the vault or the working directory.
image
Send a picture to the user on WhatsApp - a photo they asked for, an image from the chat archive, a page of a document, a chart, a screenshot. Use whenever they should look at something rather than read a description of it, or when they ask you to send or show them one.
macros
Track daily nutrition - calories and macros (protein, fat, carbs). Use whenever the user mentions food, a meal, eating something, a food photo, calories, protein, macros, their weight, or nutrition goals.
obsidian
Read and write the user's Obsidian vault - notes, recipes, the journal, drafts - and keep it in step with the phone and laptop that edit it too. Use whenever they want something looked up, written down, or changed in their vault ("add this recipe", "what does my X note say", "write that down in Obsidian"), and always after you have edited anything inside it.
offers
Watch supermarket products and report the offers running on them. Use whenever the user wants to follow a product ("watch for an offer for Monster Energy", "tell me when X is cheap"), asks whether something is on offer or what it costs right now, or wants to see, change, or stop their watches.
proton
Use whenever ANY Proton action is taken - reading or changing Proton Mail, Drive, Calendar, Contacts, Pass, or settings via proton. Covers command usage and the confirm-before-mutating policy.
recall
Search past WhatsApp conversation with the user - what they sent (text, voice notes, image captions), your past replies, and delivered skill messages. Use whenever the user refers to something from an earlier conversation that isn't in the current thread, asks "what did I say / what did we decide about X", wants an old photo, or you need a fact from before instead of guessing.
reminders
Create, list, update, and delete reminders. Use whenever the user asks to be reminded of something (after a delay or at a time), or to see, reschedule, change, or cancel their reminders.
weather
Weather and daylight for the user's place - what today or any coming day will be like, and how long the sun is up. Use whenever the user asks about the weather, temperature, rain, sun, UV, wind, sunrise or sunset, how long the day is, or whether to take a jacket.
browser
Drive a real web browser from the terminal via Browserbase's `browse` CLI - navigate pages; inspect them through accessibility snapshots, screenshots, and DOM/markdown reads; interact by clicking, typing, selecting, uploading, and raw mouse/keyboard; capture network traffic; manage tabs and named sessions; run locally or on Browserbase's cloud; and use cloud fetch/search, Functions, and templates. Use whenever a task needs to view, navigate, scrape, or act on a web page.
changelog
Maintain a project's CHANGELOG.md in Keep a Changelog 1.1.0 format - record only what moved the project's user-facing surface (commands, flags, API, config, output, screens) and never internal work, pick the right category, word it for the humans who use the project, and insert it under [Unreleased] without disturbing the rest of the file. Also cuts a release section (promotes [Unreleased] to a dated version and updates the compare links) and creates CHANGELOG.md for a project that has none. Use when the user asks to add or write a changelog entry, update the changelog, record a change in CHANGELOG.md, or prepare a release section. Reads git but never commits, tags, or bumps version files.
commit
Commit with a generated Conventional Commits message, then push. Commits the staged changes; when nothing is staged, commits the whole working tree, untracked files included. Never unstages anything. Use when the user asks to commit, save work, or commit and push. The user's confirmation in the questionnaire is the explicit, single-use git approval for the staging, the commit and the push.
context7
Fetch up-to-date library documentation and code examples via Context7 API. Use when you need current docs for any library/framework, to verify APIs exist, or to get version-specific code examples. No API key required.
exa
Web research using Exa search via scripts. Provides web search, advanced filtered search, code context lookup, and URL content extraction. Use when researching topics, finding documentation, looking up code examples, or extracting webpage content. No API key required.
handoff
Write or refresh a HANDOFF-<slug>.md briefing in the root of the working directory that transfers everything this session knows, so the next agent continues the work as this agent would - from that file alone, with no transcript and no re-explaining. Use when the user asks to hand off or save the session or to write down where things stand, when context is running low, at the end of a work stint, or before a long or risky operation that could end the session.
plan
Research-and-plan mode for substantive tasks before implementation. Use when the user asks to plan, design, investigate, figure out, or explore how to make a non-trivial code change. Restricts the agent to read-only operations until the user explicitly authorizes implementation. Grounds every claim in the codebase and current docs instead of memory, keeps a full rewrite and rejecting the task itself on the table, and opens with the before and after that the project's users will feel.
rewrite
Ground-up rewrite of everything within a scope, rebuilt clean and idiomatic in the language's modern style as if written for the first time, every inherited assumption discarded - while preserving the user-facing contract so the product behaves identically. First argument is the target path (defaults to "."); anything that isn't a path is treated as extra context. Plans first (read-only, first-principles) via the plan skill and implements only after you authorize. Use when asked to rewrite, rebuild, modernize, or overhaul a file, module, or project from scratch.