amd/gaia

---

name: integrate-agent-email

description: Use when integrating the @amd-gaia/agent-email npm package — embedding the GAIA email agent (a local triage/draft/send sidecar) into a Node, TypeScript, or Electron app. Covers install, spawning the sidecar, calling the typed client, prerequisites, and the common gotchas.

---

name: action-item-extraction

description: Pull the concrete commitments out of a thread — who owes what, by when. Use when the user asks what they need to do, what they promised, what is outstanding, or for action items from a conversation.

---

name: escalation-routing

description: Decide which messages need attention now, which can wait, and which belong to someone else. Use when the user asks what is urgent, what needs escalating, what they should look at first, or who should handle something.

---

name: inbox-triage

description: Sort an inbox into what needs a reply, what needs a decision, and what is just noise. Use when the user asks to triage, catch up on, clean up, or make sense of their inbox.

---

name: meeting-scheduling

description: Turn meeting requests in email into calendar decisions — accept, decline, or propose another time. Use when a message asks to meet, when the user asks about invitations, or when checking whether a proposed time is free.

---

name: newsletter-digest

description: Condense newsletters, promotions, and other bulk mail into one short digest and clear them out. Use when the user asks what they missed in their subscriptions, wants a digest of bulk mail, or asks to clean up promotions.

---

name: travel-itinerary

description: Assemble scattered booking confirmations into one chronological itinerary. Use when the user asks about an upcoming trip, their flight or hotel details, or wants an itinerary built from their email.

---

name: integrate-gaia

description: Use when integrating the @amd-gaia/gaia npm package — running GAIA's flagship agent, or embedding its local sidecar into a Node, TypeScript, or Electron app. Covers the one-command path, the SHA-256 integrity gate, platform coverage, starting the sidecar, the /v1/gaia/query SSE contract, and the gotchas that will bite you.

---

name: document-extract

description: Enumerate every requested item in long text documents or transcripts, with fields and source evidence. Use for exhaustive inventories such as every exercise, action item, or finding; not ordinary summaries, general knowledge lists, or code symbols.

---

name: gaia-harness-engineering

description: Help a developer report a GAIA TUI, WebUI or agent problem, explicitly share a snapshot with Claude Code or Codex through MCP, and validate isolated worktree fixes.

---

name: gaia-voice

description: How GAIA talks and what it must never claim. Always on — the agent's voice and its honesty floor, not a task recipe.

---

name: check-in

description: Run a short personal check-in that picks up where the last one left off, following up on what the user said they would do and recording what changed. Use when the user says good morning, asks for a check-in, or asks what they were working on.

---

name: coding

description: Work on a codebase — read, search, edit and verify source files. Use when the user asks to fix a bug, add a feature, refactor, explain code, make a test pass, or change anything in a repository. Covers finding the right file, editing safely, and proving the change works before reporting it.

---

name: daily-brief

description: Compose a short briefing from several sources at once — headlines, tracked topics, and the user's own open items — as one digest instead of separate answers. Use when the user asks for a briefing, a digest, a rundown, or "what do I need to know today".

---

name: data-explore

description: Load messy tabular data into SQL scratchpad tables and answer questions with real queries instead of eyeballing. Use when the user has a CSV, spreadsheet, export, or pasted table and asks for totals, trends, outliers, or a breakdown.

---

name: document-brief

description: Index a document or folder and answer questions about it with quotes from the source. Use when the user points at a PDF, contract, spec, report, or folder of files and asks what it says, what changed, or what they should worry about.

---

name: file-ops

description: Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive. Use when the user wants a file read, created, modified, or searched for by name or content.

---

name: github-triage

description: Triage GitHub work with the gh CLI — your unread notification inbox, or one repository's issue backlog. Groups what arrived, judges what is urgent, and posts the reply once you approve it. Use when asked to triage issues or notifications, check the GitHub inbox, see what needs attention or what you are blocking, review a backlog, comment on or label an issue, or work out what to fix first.

---

name: image-gen

description: Turn a description into an image file with local Stable Diffusion, then iterate on it. Use when the user says draw, sketch, paint, render, "make a picture of", "generate an image", or asks for concept art, a thumbnail, a logo idea, a wallpaper, or a mockup — and when they want the last image changed rather than replaced.

---

name: inbox-triage

description: Triage a mailbox — group what arrived, judge what is urgent and what actually needs the user, and say what to do about it. Use when asked to triage or check mail, deal with email, go through the inbox, see what is unread, get a rundown of what came in, find what needs a reply, or work out which messages matter today.

---

name: price-watch

description: Check product pages for a price drop, comparing against the lowest price seen before and alerting only on a new low. Use when the user asks to watch a price, track a deal, or tell them when something gets cheaper.

---

name: recommendations

description: Recommend films, books, games, restaurants, or gear using what the user has already said they like and dislike, plus a web search for current options. Use when the user asks what to watch, read, play, buy, or try next.

---

name: research-report

description: Research a topic on the open web and write a cited Markdown report. Use when the user asks for a report, a literature scan, a competitive landscape, or a "what's the current state of X" answer that needs sources.

---

name: rss-digest

description: Read an RSS or Atom feed and summarize the newest entries. Use when the user gives a feed URL, asks what a blog or release feed has published lately, or wants a digest of a site that offers a feed.

---

name: source-watch

description: Check a web page or feed for something worth telling the user about, remembering what was already reported so nothing repeats. Use when the user asks to watch, monitor, or check a URL for changes, new items, or a condition being met.

---

name: summarize

description: Summarize a document, meeting transcript, or email — pick a style that matches what the content actually is, and fold long input forward in sections instead of losing the back half. Use when the user pastes or points at a transcript, email, PDF, or long document and asks for a summary, action items, or key decisions.

---

name: transcribe-meeting

description: Transcribe and summarize a meeting recording — speaker-attributed transcript, corrected mis-hearings, then a brief with decisions and action items. Use whenever the user points at an audio or video file (.mp4, .mkv, .mov, .m4a, .mp3, .wav) or a Teams/Zoom transcript export and asks to transcribe it, summarize it, take notes, write minutes, say what was discussed, who said what, what was decided, or what the action items and follow-ups are.