Agent skill · software engineering · jeremylongshore
procore-common-errors
Triage Procore OAuth, routing, permission, validation, pagination, throttling, and webhook failures without widening access or retrying blindly. Use when a Procore integration returns 4xx or 5xx responses, empty data, or missing deliveries. Trigger with: "debug Procore 403", "fix Procore API errors", "why is Procore returning 404".
Why this skill is useful
Provides specific implementation patterns and error handling for Procore API that the AI wouldn't reliably generate on its own.
What it needs
Requires procore account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Procore Error Classification and Recovery Overview Classify failures by identity, company routing, authorization, endpoint contract, business validation, throttling, or provider health. Preserve the original response and avoid treating every 404 as absence or every 5xx as safe to retry. Prerequisites Timestamp, environment, method, normalized route, status, and sanitized response Token alias, app version, company and project context, and operation type Current endpoint reference plus access to Integration Health or API activity evidence Instructions Step 1: Preserve the failure Capture response code, headers, body shape, correlation data, and elapsed time. Redact authorization, destination headers, query secrets, names, and construction payloads. Step 2: Classify the layer Map 401 to token or environment; 403 to connection, permission, tool, or project scope; 404 to route, identifier, or concealed access; 422 to business validation; 429 to rate budget; and 5xx to provider or transient infrastructure. Step 3: Check company routing Verify the intended company and whether Procore-Company-Id is required. Audit background jobs and webhook handlers that may have lost explicit routing context. Step 4: Check the public contract Confirm the route, API version, required fields, filters, enabled tool, and project membership against current documentation. Reject private or deprecated endpoints. Step 5: Recover narrowly Refresh or reauthorize only for an identity failure, fix permissions only when evidence proves the missing permission, honor rate headers, and retry server errors only when the operation is safe. Step 6: Verify the fix Replay the smallest sanitized case, confirm the expected status and resource boundary, and monitor the relevant Integration Health observation or API activity slice. Authentication Troubleshooting uses the existing OAuth 2.0 Bearer token alias and never requests a broader token as a generic fix. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-common-errors