Agent skill · software engineering · jeremylongshore
procore-multi-env-setup
Configure Procore Developer, On-Demand, Monthly, and production environments without mixing app keys, OAuth credentials, hosts, company IDs, or reset assumptions. Use when building an environment matrix or onboarding customer testing. Trigger with: "configure Procore environments", "set up Procore sandbox", "fix Procore sandbox credentials".
Why this skill is useful
Provides specific implementation patterns and error handling for Procore API integration that the AI wouldn't reliably generate on its own.
What it needs
Requires curl 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 Environment Isolation Matrix Overview Choose the environment from the test purpose and configure its actual installation and runtime contract. Developer, On-Demand, and Monthly sandboxes differ in credentials, hosts, app version keys, refresh behavior, and customer eligibility. Prerequisites Test objective, data sensitivity, customer involvement, and refresh requirement App version, sandbox or production keys, OAuth credential aliases, and company IDs Named administrator and post-refresh or post-install verification owner Instructions Step 1: Select the environment Use a Developer Sandbox for isolated app building, On-Demand Sandbox for customer-controlled testing on copied data, and Monthly Sandbox for a periodically refreshed customer snapshot. Use production only for approved live operation. Step 2: Build an explicit matrix Record authentication host, API host, browser host, app version key type, OAuth credential type, company ID, refresh behavior, and installation owner for each environment. Step 3: Enforce isolation Store configurations separately and add guards that reject mismatched host, credential alias, and environment. Never infer environment from a company name. Step 4: Install correctly Use the Sandbox App Version Key only for the Developer Sandbox. Customer On-Demand and Monthly sandboxes use the production app version key and must be installed or surfaced according to their documented lifecycle. Step 5: Plan data reset Do not assume Developer Sandboxes refresh. Treat On-Demand lifecycle as customer-controlled and Monthly Sandbox changes as disposable at refresh. Step 6: Verify after change After install, recreation, or refresh, obtain a token and run the read-only connection proof against the expected company and project boundary. Authentication Developer Sandbox uses sandbox OAuth credentials and sandbox hosts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-multi-env-setup--5d8301