Agent skill · software engineering · jeremylongshore
procore-hello-world
Prove a Procore connection with a read-only, company-routed smoke test before enabling mutations. Use when verifying a new token, app installation, DMSA project scope, environment, or deployment. Trigger with: "test my Procore connection", "run a Procore smoke test", "verify Procore access".
Why this skill is useful
Adds executable scripts for interacting with the Procore API, enabling project management tasks that the AI cannot generate on its own.
What it needs
Requires curl, requests 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 Read-Only Connection Proof Overview Establish identity, company routing, project visibility, and pagination without creating construction records. The proof must demonstrate the selected environment and permission boundary, not merely that an access token exists. Prerequisites Approved OAuth token obtained through the intended grant and environment Expected company identifier and at least one known permitted project Redacted evidence destination and named owner for permission failures Instructions Step 1: Freeze the target Record the expected environment, API base, company ID, token alias, and app version. Reject mixed production and sandbox inputs before sending a request. Step 2: Verify identity Call the documented current-user or company discovery surface using the Bearer token. Supply Procore-Company-Id when the contract requires company routing, especially for multi-region and DMSA traffic. Step 3: List visible projects Use the documented projects list endpoint and a small page. Follow the returned pagination contract instead of assuming one page is complete. Step 4: Assert the boundary Confirm the known permitted project appears and a known unpermitted project does not. Treat excess visibility as a security defect rather than a successful smoke test. Step 5: Capture a receipt Record status, normalized route, company and project identifiers, page metadata, response latency, and a hash of the sanitized assertion output. Do not retain names or payloads unless the test requires them. Authentication Authenticate with an OAuth 2.0 Bearer token produced for the selected Procore environment. The token carries either user permissions or DMSA permissions; the smoke test never broadens those permissions. Tool Discipline Use Read and Grep to inspect environment configuration and expected identifiers. Use Write or Edit only for the approved test, assertion fixture, or redacted receipt; this workflow must not create, update, or delete Procore records. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-hello-world