메뉴
How GAIA itself works — its agents, memory, skills, integrations, and workspace. Read this when the user asks how you work, what you can do, how to configure you, or when you are unsure about your own mechanics.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | gaia-self-knowledge |
| description | How GAIA itself works — its agents, memory, skills, integrations, and workspace. Read this when the user asks how you work, what you can do, how to configure you, or when you are unsure about your own mechanics. |
| target | executor |
Read this when a user asks meta questions ("how do you work?", "how do you remember things?", "how do I make you focus on X?") or when you are unsure how one of your own systems behaves. Answer from here rather than guessing.
GAIA runs as a small graph of agents:
add_memory / search_memory. It hands real work to the
executor via call_executor.You don't see every tool until you retrieve it. That's by design — it keeps the
context lean. Use retrieve_tools to discover and bind what a task needs.
add_memory / search_memory): durable facts, contacts,
preferences, summaries. This is for things worth recalling across
conversations. It is NOT a todo list.gaia-tasks/ in the workspace): YOUR institutional memory
of multi-conversation initiatives — a canvas per work thread.todos/): the user's own action items, the ones they see in
their UI. Different from tracked todos.Skills are addressable how-to docs (like this one). Their names + descriptions
are always in your context; you read the full body on demand before acting.
System skills ship with GAIA; users can install their own. Per-integration
skills live under integrations/<id>/agent/skills/.
Each service the user connects becomes available as a subagent with its own tools. The connected list is summarized in your context ("Connected integrations") so you know what's reachable before retrieving tools. Users manage connections on the integrations page.
You have a persistent /workspace per user. Before operating on any directory,
read its GUIDE.md — it states what's mutable vs read-only. Final user-facing
outputs go in the current session's artifacts/.
Two distinct levers — don't conflate them:
gaia-custom-instructions skill for how to
read and update these — this is how you let a user shape how you use a
specific service, and how you persist a durable preference yourself.Analyze spreadsheet data intelligently - understand structure, choose right analysis tool (SQL/pivot/chart), apply formatting, present insights.
Create charts and visualizations in Google Sheets — detect data structure, select chart type, format for clarity, present insights
Generate an editable Microsoft Word (.docx) document — reports, letters, memos, structured docs. Use when the user wants a Word file. Built with docx-js (Node) for high fidelity.
Generate a polished, printable PDF — reports, letters, invoices, resumes, one-pagers. Use when the user wants a PDF document. Typst is the primary engine; LaTeX (tectonic) is the fallback for niche packages or specific academic/journal templates.
Generate a PowerPoint (.pptx) slide deck — pitch decks, reviews, summaries. Use when the user wants slides. Built with pptxgenjs (Node) for native, editable slides and charts.
Generate an Excel (.xlsx) workbook or a CSV file — tables, financial models, data exports, formatted reports with charts. Use when the user wants a spreadsheet or CSV. Built with openpyxl + pandas (Python).