What problem does it solve? Connector-backed tools in APX fail with errors like "not connected", "read-only", or "not authorized", and the agent cannot fix these itself because connecting a plugin requires human action in the web panel. This Skill teaches the agent to recognize those errors, explain the exact next step to the user, and avoid confusing connectors with MCP servers or the Telegram channel. ## Core Features & Use Cases - Error interpretation: Maps connector tool errors (not connected, OAuth not completed, read-only calendar, missing Asana workspace) to precise user-facing remediation steps in the web panel's Integrations → Plugins section. - Connector catalog knowledge: Covers Asana (token), Google Calendar (user OAuth with write_access and Meet toggles), GitHub (token), Obsidian (local Vault path, the only connector with a CLI via apx obsidian), and WhatsApp (coming_soon, must not be attempted). - Scope resolution: Explains project-vs-default(global) precedence so a connector configured on the default project works everywhere unless overridden. - Use Case: A user asks "why can't you see my calendar?" — the agent recognizes the missing OAuth refresh_token, directs the user to finish the "Connect with Google" step in the panel, and stops instead of retrying the tool in a loop. ## Quick Start Ask the agent to check why the Google Calendar integration is not connected and tell you exactly what to do in the web panel.
