Agent skill · software engineering · jeremylongshore
procore-incident-runbook
Analyze, triage, and recover a Procore integration incident across provider health, OAuth, company routing, permissions, rate limits, webhooks, files, and synchronization gaps. Use when service objectives or data parity are breached. Trigger with: "run Procore incident response", "Procore sync is down", "recover missing Procore updates".
Why this skill is useful
Adds executable scripts for Procore API integration that provide capabilities not covered in public documentation.
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 Integration Incident Command Overview Protect construction data integrity while restoring service. Separate provider outage, identity failure, tenant-routing defect, permission drift, rate exhaustion, event-delivery gap, and internal deployment regression before choosing recovery actions. Prerequisites Incident commander, severity, affected tenant aliases, start time, and objectives Current release, last known good release, queue and reconciliation checkpoints Procore status, Integration Health, API activity, and approved communication channels Instructions Step 1: Stabilize Pause risky mutations, preserve durable queues, stop retry storms, and keep read-only evidence collection bounded. Do not delete events or rotate credentials without a matching hypothesis. Step 2: Classify Compare Procore status with route-level 401, 403, 404, 422, 429, 503, latency, webhook delivery, and backlog signals. Segment by release, environment, company, project, and operation. Step 3: Test the boundary Run one read-only connection proof using the intended principal and company context. Check app connection, DMSA permissions, permitted projects, enabled tools, and rate headers. Step 4: Mitigate narrowly Roll back a bad release, repair tenant routing, reauthorize or rotate only when credential evidence supports it, reduce concurrency, or disable the affected mutation path. Step 5: Recover data Determine the gap window, replay durable work idempotently, and run REST reconciliation. Validate record counts and state hashes before reopening downstream publication. Step 6: Settle and learn Monitor until objectives recover, record root cause and contributing controls, assign follow-ups, and retain only redacted evidence with a deletion schedule. Authentication Incident probes use the existing OAuth 2.0 principal unless identity failure is the proven cause. Tokens, client secrets, destination headers, and signed URLs never enter the incident timeline or chat. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-incident-runbook