Skip to content

armgit / qm

Public Imported from GitHub
0

Multiplayer agent harness for work.

Fold auth-header guidance into existing Dropbox skill text

Josh France9a89c695a3b5
diff --git a/skills-seed/dropbox/SKILL.md b/skills-seed/dropbox/SKILL.md
index 2ddff129b..c4ed4d46e 100644
--- a/skills-seed/dropbox/SKILL.md
+++ b/skills-seed/dropbox/SKILL.md
@@ -20,7 +20,8 @@ cached credential would):
Both carry the **same** Dropbox token (one OAuth grant spans every host), so if a
host-specific var is empty, `$VAULT_TOKEN_API_DROPBOXAPI_COM` works as the bearer for any
-Dropbox host. Pass it as `-H "Authorization: Bearer $VAULT_TOKEN_..."`. Never ask the user
+Dropbox host. Pass it as `-H "Authorization: Bearer $VAULT_TOKEN_..."` on every call;
+nothing on the network path adds it for you. Never ask the user
for a token, log it, or use another principal's credential or a service fallback.
If `$VAULT_TOKEN_API_DROPBOXAPI_COM` is **empty**: per-user connector tokens are injected
@@ -29,24 +30,13 @@ they're absent by design, even for a fully-connected user. So don't tell a chann
reconnect; ask them to DM you to run this. Only if it's empty inside a DM does it mean they
haven't connected Dropbox — then point them to the Connectors page.
-**Always send the token yourself.** Every Dropbox call needs
-`-H "Authorization: Bearer $VAULT_TOKEN_..."`. Nothing between your computer and Dropbox
-adds it for you, so a call without that header always fails.
+On **400 `Invalid authorization value`**: the header was missing or empty, so Dropbox
+never checked the token. Fix your command (`echo ${#VAULT_TOKEN_API_DROPBOXAPI_COM}` shows
+the variable is set) and retry; this says nothing about the user's connection. Before
+telling a user Dropbox is broken, confirm with `users/get_current_account` below.
-**Telling a missing header from a bad token:**
-
-- **400 `Invalid authorization value in HTTP header/URL parameter`:** the header was
- missing, empty or malformed. Dropbox never checked the token, so this says nothing about
- the user's connection. Check that your command has the header and that the variable is
- set (`echo ${#VAULT_TOKEN_API_DROPBOXAPI_COM}` prints its length, not the token), then retry.
- Don't tell the user their connection is broken and don't ask them to reconnect.
-- **401 `invalid_access_token` / `expired_access_token`:** the token was sent and rejected.
- Only then is a reconnect the answer.
-
-Before telling the user Dropbox is broken, run `users/get_current_account` (below) with the
-header. If it returns their account, the connection works and the fault is in your call.
-
-On **401**: the token is expired/invalid → have them reconnect — _unless_ the error body's
+On **401** (`invalid_access_token`, `expired_access_token`): the token was sent and
+rejected → have them reconnect — _unless_ the error body's
`.tag` is `missing_scope`, in which case the app lacks a permission; name the `required_scope`
it returns (the connected app grants account_info.read, files.metadata.read,
files.content.read/write, sharing.read/write).