Agent skill · software engineering · jeremylongshore
procore-local-dev-loop
Build a deterministic Procore integration loop with fixtures, a Developer Sandbox, and explicit mutation cleanup. Use when developing endpoint adapters, reproducing provider failures, or testing pagination and retry logic locally. Trigger with: "set up Procore local development", "test Procore with fixtures", "reproduce a Procore API bug".
Why this skill is useful
Provides specific implementation patterns and API call examples for Procore's REST API that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, npm, pip installed locally. 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 Deterministic Development Loop Overview Separate fast fixture tests from deliberate provider tests. A Developer Sandbox supplies isolated seed data and separate OAuth credentials, but it is not a production replica and cannot be casually refreshed, so tests must own their records and cleanup. Prerequisites Endpoint contract and failure case under test Sanitized request and response fixtures with stable identifiers Developer Sandbox app, sandbox credentials, and a dedicated test project Cleanup rule for every test-created Procore record Instructions Step 1: Define the contract Capture method, normalized route, required headers, request schema, expected status, pagination metadata, and error shape. Keep provider-generated IDs outside golden assertions. Step 2: Build fixture tests Exercise token expiry, permission denial, hidden-resource 404, validation failure, throttling, and server retry behavior without network access. Assert that secrets and construction payloads are redacted. Step 3: Isolate provider tests Point live tests only at login-sandbox.procore.com and sandbox.procore.com with sandbox credentials. Refuse production hosts in local and CI test profiles. Step 4: Create bounded data Prefix test artifacts with a run identifier, record every created ID, and clean up in reverse dependency order. Do not assume the Developer Sandbox can be reset. Step 5: Reconcile fixtures When the official endpoint behavior changes, review the API reference and changelog, update the adapter first, then deliberately re-record only sanitized fixtures. Authentication Live sandbox tests use a sandbox OAuth 2.0 Bearer token. Production credentials and tokens are forbidden in the development profile, and recorded fixtures must contain neither credentials nor tokens. Tool Discipline Use Read and Grep to inspect code, fixtures, and endpoint documentation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-local-dev-loop--6272b7