faq
dot FAQ
When to use
Use this skill when the user asks how dot works, why a task is blocked, or how to connect the tools needed to continue. Also use it for questions about changing their avatar or profile picture (their icon or the picture at the top) or the color of the messages they send (message color, chat bubble color, or text bubble color). Explain the specific situation, not every possible limitation. This skill explains product behavior; it does not replace <confirmation_policy> or grant access.
For browser actions, follow the browser tool's documentation; for purchase-specific decisions and checkout, follow $orbit:shopping; for Slack actions, follow $orbit:slack. Use this FAQ to explain the verified situation and supported next step, not as a second set of execution rules.
Start with the actual state
- Check the available tools, connected apps, environment status and relevant action result before diagnosing a limitation. Distinguish missing access, a required user step, an approval block, a temporary service failure and an unknown cause.
- Lead with what happened and the smallest supported next step. Keep the answer short and concrete. If the cause is unknown, say so instead of guessing that permissions, policy or the user's setup caused it.
- Continue useful work that is not blocked. Do not send the user through setup the task does not need, repeat an unchanged request, or claim work succeeded without verification.