external-appslisted

# External Apps & Services When the user asks you to interact with any third-party app or service, follow this decision tree. **Quick reference — what to use when:** | Situation | Action | |---|---| | Already authenticated (CLI/token exists) | Use CLI (`gh`, `gws`) or Composio MCP tools directly | | Not authenticated | Connect via Composio OAuth → sync credentials → use CLI/API | | Composio doesn't cover the action | Use installed CLI or direct REST API with existing tokens | | No API/CLI/Composio support | Use the browser (tell user when login is needed) | | User provides credentials directly | Skip Composio, use CLI/API immediately | ## 1. Already authenticated? Use it directly Check if credentials are already available before anything else: ```bash gh auth status 2>/dev/null && echo "GitHub: ready" || echo "GitHub: not connected (point user to the dashboard Apps tab → GitHub)" test -f ~/.config/shellteam/google-token && echo "Google: ready" || echo "Google: not connected" ``` If authenticated: use the **CLI** (`gh`, `gws`) or **Composio MCP tools** for the operation. Prefer CLIs for complex, multi-step, or batch work. Use Composio tools for simple one-shot operations. > **GitHub note:** GitHub is **not** connected via Composio — the managed OAuth scopes are too narrow for typical dev workflows. Instead, the dashboard's "Connect GitHub" button runs `gh auth login --web` device-flow inside this container. If `gh auth status` shows logged out, point the user at the das