Menu

Individual skill

faq

0upvotes

Explain how this assistant works and help users understand computer access, confirmation or login blocks, and Slack errors. Use for capability questions and confusing product limitations; verify the actual state and give a supported next step. Also use for questions about their avatar or profile picture (their icon or the picture at the top) or the color of messages they send (message color, chat bubble color, or text bubble color).

OpenAI/dots/skills/faq/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
71,199
Repository last updated
Nov 10, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top