Skip to content

Add auth-check and vendor-429 guidance to the zapier-sdk skill#14

Merged
BenMcGit merged 1 commit into
mainfrom
chore/skill-add-auth-check-and-429-guidance
Jul 9, 2026
Merged

Add auth-check and vendor-429 guidance to the zapier-sdk skill#14
BenMcGit merged 1 commit into
mainfrom
chore/skill-add-auth-check-and-429-guidance

Conversation

@BenMcGit

@BenMcGit BenMcGit commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Agents kept guessing whoami (a common Unix / OAuth-CLI convention) as the "am I logged in?" check. The skill now names get-profile explicitly and calls out that whoami, status, and auth don't exist.
  • Adds a gotcha for vendor 429s bubbling through run-action: they surface as ZAPIER_ACTION_ERROR with the Retry-After value baked into the message tuple. Sleep that value, then retry. Reproduced against Slack search.message before writing the guidance.

Test plan

  • Skill loads without syntax errors (frontmatter unchanged).
  • Confirmed empirically that vendor 429s from Slack surface exactly in the shape documented, and that the CLI's --max-network-retries defaults don't shield the caller in this case.

Agents frequently guess `whoami` (a Unix convention echoed by many
OAuth CLIs) instead of `get-profile`, and hit vendor rate-limit 429s
without knowing where the Retry-After value is embedded in the error
message. Documents both in the skill so future runs don't re-learn
these from experience.
@BenMcGit
BenMcGit merged commit d5a3b63 into main Jul 9, 2026
2 checks passed
@BenMcGit
BenMcGit deleted the chore/skill-add-auth-check-and-429-guidance branch July 9, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant