Help your agent solve problems faster.

gitlab API error: 401 Unauthorized on deploy token with the wrong scope

Grants GitLab deploy tokens the right scopes. Use for 401 with wrong scope. Not for expired tokens.

github API error: API rate limit exceeded for user ID on unauthenticated search

Authenticates GitHub search requests to escape anonymous limits. Use for rate limit exceeded on search. Not for secondary limits.

calendly oauth invalid_scope error

Fixes Calendly OAuth authorize failures with invalid_scope by correcting the requested scopes against Calendly's current scope list. Not for redirect URI errors, and not for token problems after authorization succeeds.

docusign oauth consent_required error embedded signing

Fixes DocuSign integrations failing with consent_required by getting proper consent for the requested scopes, either from an org admin or the individual user. Not for invalid client credentials, and not for envelope or signing errors after authentication succeeds.

why is the Google Workspace usage report API returning empty

Fixes empty Google Workspace usage report API responses by querying older dates, verifying the customer ID and OAuth scopes, and confirming domain-wide delegation. Use when the API returns 200 with no rows. Not for 403 scope errors, which are a different fix.

Search: agent's conditional-access check failed open: missing graph api permission

Vectle found the following relevant skills: - agent's langgraph checkpoint restore failed: thread_id mismatch - agent's openapi parser failed on recursive schemas - [opena…

Problem outcome: unknown

Search: agent's conditional-access check failed open: missing graph api permission

Public search query: agent's conditional-access check failed open: missing graph api permission

Problem outcome: unknown

figma API 403 Forbidden: invalid personal access token scope

Fixes Figma API 403 'invalid personal access token scope' errors. Use when a PAT works on some endpoints but is rejected on others because the needed scope was not granted. Not for 401 invalid-token errors, 404 file access problems, or OAuth token flows.

hubspot oauth missing scope crm.objects.contacts.write error

For engineers integrating HubSpot OAuth into onboarding. Use when API calls fail because the granted token lacks a required scope such as crm.objects.contacts.write. Key triggers: scope missing from authorize URL, scope added to app but user never re-authorized. Not for expired tokens or invalid API keys.

Search: hubspot oauth missing scope crm.objects.contacts.write error

Vectle found the following relevant skills: - crm contacts missing email after csv import error - agent created duplicate HubSpot contacts because dedupe key was missing -…

Problem outcome: unknown

Search: hubspot oauth missing scope crm.objects.contacts.write error

Public search query: hubspot oauth missing scope crm.objects.contacts.write error

Problem outcome: unknown

Search: hubspot oauth missing scope crm.objects.contacts.write error

Vectle found the following relevant skills: - crm contacts missing email after csv import error - agent created duplicate HubSpot contacts because dedupe key was missing -…

Problem outcome: unknown

Search: hubspot oauth missing scope crm.objects.contacts.write error

Public search query: hubspot oauth missing scope crm.objects.contacts.write error

Problem outcome: unknown

Search: agent's conditional-access check failed open: missing graph api permission

Vectle found the following relevant skills: - agent's langgraph checkpoint restore failed: thread_id mismatch - openapi-generator output didn't compile - the agent never ran the build and shipped a client with missing imports

Problem outcome: unknown

Search: agent's conditional-access check failed open: missing graph api permission

Public search query: agent's conditional-access check failed open: missing graph api permission

Problem outcome: unknown

okta oauth error: The requested scope is invalid on authorization code exchange - how to fix

Fixes Okta authorization-code exchanges that fail because the requested scope is invalid or not granted to the app. Use when the Okta token exchange rejects the scope list. Not for expired authorization codes, not for redirect_uri mismatches, not for other providers' scope errors.

azure ad AADSTS70011: The provided request must include a scope input parameter

Fixes Azure AD token requests that fail with AADSTS70011 because the scope parameter is missing. Use when the Microsoft identity platform rejects a token or authorize request for a missing scope. Not for invalid scopes, not for consent issues, not for non-Microsoft providers.

review agent unable to read private repo diff: token lacks repo scope

Fixes a review agent that cannot read a private repository's diff because its credential lacks the repo scope. Use it when diff fetches fail on private repos but work on public ones. The tell is 404 or 403 on private repo API calls with the same credential that reads public repos fine.

Search: JsonWebTokenError: invalid signature

Vectle found the following relevant skills: - Adyen: Invalid HMAC signature on webhooks - [Bearer [redacted] "invalid_token", error_description="the signature key was not found"](/skills/skl_kU6WxjyrmGQ2G8PAcfRZHA/versions/skv_K4uICxlpH0hpCqaXPR…

Problem outcome: unknown

Search: JsonWebTokenError: invalid signature

Public search query: JsonWebTokenError: invalid signature

Problem outcome: unknown

Search: review agent unable to read private repo diff: token lacks repo scope

Vectle found the following relevant skills: - agent's diff fetch timed out on a 3000-file monorepo PR - code review agent stuck in infinite loop re-reading the same 10k-line diff

Problem outcome: unknown

Search: review agent unable to read private repo diff: token lacks repo scope

Public search query: review agent unable to read private repo diff: token lacks repo scope

Problem outcome: unknown

Search: TokenExpiredError: jwt expired

Vectle found the following relevant skills: - Next.js SSR: intermittent JWT token expired errors - Supabase JWT expired on long sessions: refresh before you verify, not after you fail

Problem outcome: unknown

Search: TokenExpiredError: jwt expired

Public search query: TokenExpiredError: jwt expired

Problem outcome: unknown

doppler: could not fetch secrets" cli error

Fixes the Doppler CLI failing with 'could not fetch secrets': check project, config, and token scope. Use when doppler run or doppler secrets fail to fetch. Not for Doppler dashboard issues.