Agent skill · software engineering · jeremylongshore
procore-performance-tuning
Reduce Procore synchronization latency through measured call sequencing, endpoint-specific pagination, caching, batching, and bounded concurrency. Use when a connector is slow, request-heavy, or accumulating lag. Trigger with: "speed up Procore sync", "optimize Procore pagination", "reduce Procore integration latency".
Why this skill is useful
Provides specific implementation patterns and API call examples for Procore's performance tuning that the AI wouldn't reliably 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 Measured Sync Performance Overview Optimize useful records per request and end-to-end freshness before increasing concurrency. Procore recommends collection reads, caching, webhooks, and deliberate sequencing; page limits and response shapes remain endpoint-specific. Prerequisites Baseline volume, latency percentiles, call count, error rate, and backlog age Resource dependency graph and current endpoint pagination contracts Correctness oracle for completeness, ordering, duplicates, and deletions Instructions Step 1: Measure the critical path Group calls by normalized route and outcome. Identify serial dependency edges, repeated lookups, first-page-only defects, payload-heavy reads, and failed calls consuming budget. Step 2: Sequence dependencies Fetch company and project context before project resources, and prerequisite catalogs before dependent records. Avoid nested request waterfalls when one collection or cache can serve many records. Step 3: Paginate correctly Use each endpoint's documented perpage range and follow Link relations until next is absent. Never treat a global page-size recommendation as an endpoint guarantee. Step 4: Reduce redundant work Cache stable lookups, use webhooks for fast change detection, retain a periodic reconciliation scan, and use documented sync actions where the resource supports them. Step 5: Tune concurrency Increase workers gradually while observing rate headers, error rate, and provider latency. Route every worker through the shared rate controller. Step 6: Verify correctness and gain Compare record sets and state hashes before and after optimization. Accept the change only when completeness is unchanged and measured latency or call volume improves. Authentication Performance tests use the normal OAuth 2.0 Bearer token and company boundary. Never spread traffic across extra credentials to hide inefficient behavior or bypass provider controls. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-performance-tuning--9db06d