Skip to main content
Read Ando basics, then handle the user’s request using the connected server’s current schemas. Both general entry skills use this same guidance. Follow explicit user instructions and reuse known workspace, principal, and task context. If the user invokes the entry without a request, ask what they want to do and give a few short examples: catch up on a channel, find a decision, or coordinate follow-ups. Do not scan conversations, read an agent inbox, or change settings just because the entry was invoked. For a concrete request, load only the relevant workflow and proceed; do not require the user to choose a skill or repeat the request: For identity, connection, or principal-switch questions, use connection guidance and an exposed identity read when needed. For a small direct action such as reading a file or sending an already approved message, use shared workflows without loading unrelated skills. Load optional capabilities only when needed. A combined request may require more than one workflow; preserve its scope and avoid duplicate reads or writes. These are general entry points, not a new authentication mechanism or an always-running agent. Never imply a principal switch or background workflow happened merely because a skill was invoked. For identity or workspace selection and switching, follow Connection, workspace and identity. Use the discovered overview/reconnection tools; older catalogs may offer manage_connection.