Agent skill · software engineering · jeremylongshore
procore-prod-checklist
Gate a Procore integration for production with evidence for security, permissions, lifecycle, support, sandbox testing, health, rate handling, webhooks, and rollback. Use when preparing for customer launch or Marketplace submission. Trigger with: "review Procore production readiness", "check Procore launch", "prepare Procore Marketplace approval".
Why this skill is useful
Provides specific API call patterns and error handling for Procore integration that the AI wouldn't 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 Production Readiness Gate Overview Convert launch claims into verifiable evidence. This gate covers the integration and its Procore app contract; it does not declare Marketplace approval or provider certification merely because local checks pass. Prerequisites Immutable release candidate and matching app version Data classification, permission map, environment matrix, and endpoint inventory Support, security, operations, rollback, and customer communication owners Instructions Step 1: Verify application contract Confirm semantic version, release notes, components, callbacks, permissions, permitted-project behavior, installation instructions, and production credentials. Step 2: Verify functional paths Exercise token lifecycle, required reads, expected denials, approved mutations, pagination, files, webhooks, deduplication, reconciliation, and cleanup in the intended sandbox. Step 3: Verify reliability Prove handling for 401, 403, hidden 404, 422, 429, 503, timeout, ambiguous write, duplicate event, discarded event window, and provider outage. Step 4: Verify security and privacy Review secret storage and rotation, tenant routing, least privilege, log redaction, secure-file handling, data retention, deletion, and incident escalation. Step 5: Verify operations Establish Integration Health and API activity review, rate and backlog alerts, support intake, status-page dependency, runbooks, and on-call ownership. Step 6: Decide explicitly Record PASS, CONDITIONAL, or FAIL per gate with evidence. Require launch approval and preserve rollback triggers; do not convert missing evidence into a pass. Authentication Readiness tests use the selected OAuth 2.0 grant, environment-specific credentials, and intended user or DMSA permission boundary. Evidence excludes all tokens, client secrets, and webhook destination credentials. Tool Discipline Use Read and Grep to inspect release artifacts, tests, manifests, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-prod-checklist