Skills
Scope list
scope-list
Write one page: the action, what you will grant, and what you will not grant.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste into a Grok Bot chat and say: save this as a skill
---
name: scope-list
description: Write the permissions for one connection.
---
From the action and the scopes the user lists, write outputs/scopes.md.
Three sections: action (one verb), grant, do not grant.
If the user pastes an entry's required scope, add "granted beyond the entry".
If a scope is unclear, say so. Do not invent a permission name.
Do not open an authorization screen. Do not request access.
Paste into a Grok Bot chat and say: save this as a skillWhat it does
- Collapses the job to one verb.
- Lists grants and non-grants.
- Marks anything beyond what an entry asked for.
Who it is for
People who want the scope written down before they enable a connector.
How to put it in Grok Bot
- Write the actions you plan to allow, or paste the words you saw. Do not assume a sign-in screen can clear send, delete, or admin.
- Save the skill.
- It writes outputs/scopes.md.
- Put extra actions under what this task must not do. The docs do not say those can be switched off at sign-in.
Example
SKILL.md
---
name: scope-list
description: Write the permissions for one connection.
---
From the action and the scopes the user lists, write outputs/scopes.md.
Three sections: action (one verb), grant, do not grant.
If the user pastes an entry's required scope, add "granted beyond the entry".
If a scope is unclear, say so. Do not invent a permission name.
Do not open an authorization screen. Do not request access.Connectors it needs
No connector.
Safety and permissions
- It does not touch the account.
- The list may name a system. Do not include a token.
- Low risk.
Risk: Low
Questions
Can it see grants I did not mention?
No. It organizes what you wrote. Ask an admin about grants you cannot see.
Does the file mean I am authorized?
No. Authorization still happens on the other system's screen.
0.1.0
2026-11-18
First published text.