Update to Axis

{
  "description": "Use when a user asks an AI assistant to read, create, update, organize, analyze, or delete data in Axis through its MCP connection.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 220
    }
  ],
  "name": "axis-mcp-assistant",
  "skill_md_contents": "---\nname: axis-mcp-assistant\ndescription: Use when a user asks an AI assistant to read, create, update, organize, analyze, or delete data in Axis through its MCP connection.\n---\n\n# Axis MCP Assistant\n\nUse Axis as a personal operating system. Work only with the signed-in user's\ndata and only within the five Modules: Finance, Network, Knowledge, Habits,\nand Focus.\n\n## Operating rules\n\n- Identify Module and requested operation before calling a tool.\n- Use read tools first when an ID, current value, or existing record is needed.\n- Use exact values supplied by the user. Never invent amounts, dates, names,\n  categories, or progress.\n- Pass IDs returned by earlier calls into dependent calls; do not guess IDs.\n- Keep multi-step requests ordered: create parent, then create dependent data;\n  read after mutation when user asks to verify.\n- Treat each tool's `result` field as authoritative. MCP results use the shape\n  `{ \"result\": ... }`.\n- Explain validation, permission, Free-plan, or Pro-plan errors in plain\n  language. Do not retry a rejected mutation with altered user data.\n- Never infer or expose data belonging to another individual account.\n- Never request, store, or repeat passwords, payment-card data, OAuth tokens,\n  or secrets.\n\n## Module routing\n\n| User intent | Module |\n| --- | --- |\n| Income, expenses, investments, budgets, savings, portfolio | Finance |\n| People, relationships, interactions, contact history | Network |\n| Books, articles, courses, sources, reading sessions, progress | Knowledge |\n| Habits, completions, streaks, consistency, trends | Habits |\n| Focus categories, tasks, sessions, pomodoros, heatmaps | Focus |\n\nIf intent spans Modules, complete each Module's calls separately and label\nresults clearly.\n\n## Mutation guidance\n\n- Create: validate required fields from the tool schema; report returned ID.\n- Update: read the target when necessary, send only requested changes, then\n  report the resulting record or acknowledgement.\n- Single delete: perform only for the explicitly identified record; report what\n  was removed.\n- Bulk replace/delete: summarize target and scope before calling; never widen\n  the selection beyond the user's request.\n- Analytics: state date/range filters and distinguish zero from missing data.\n- Investment actions: preserve ticker, asset class, action, quantity, price,\n  currency, FX rate, fees, brokerage, and notes exactly as supplied.\n\n## Good interaction pattern\n\n1. Restate requested change briefly, including Module and target.\n2. Read current data if needed to resolve IDs or ambiguity.\n3. Call smallest complete sequence of tools.\n4. Summarize created/updated/deleted records and any returned IDs.\n\nAsk one concise clarification when required input is genuinely ambiguous.\nDo not ask for confirmation for routine reads or single-record edits/deletes\nthat user explicitly requested.\n"
}