Agent skill · software engineering · jeremylongshore
procore-cost-tuning
Recover Procore API capacity by eliminating failed calls, redundant polling, repeated lookups, and unused payloads. Use when request volume, infrastructure spend, or backlog growth is high; this workflow does not invent provider pricing. Trigger with: "reduce Procore API calls", "cut Procore sync cost", "stop Procore polling".
Why this skill is useful
Provides specific API call patterns and error handling for Procore's cost 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 API Call Budget Recovery Overview Treat calls, worker time, transfer, and backlog as measured costs. Procore documents request limits and activity reporting, but not a universal per-call price, so financial claims must come from the operator's own infrastructure and agreement. Prerequisites Route, method, status, and daily count from the API Call Activity Report Poll interval, worker utilization, transfer, storage, and queue metrics Freshness objective and correctness oracle for every optimized resource Instructions Step 1: Build the denominator Rank normalized routes by total calls, failed calls, payload volume, and worker time. Separate unavoidable business traffic from retries, polling, and adapter defects. Step 2: Eliminate failed-call waste Fix recurring 400, 403, and 404 traffic first because unsuccessful requests consume rate budget. Remove private or deprecated routes rather than retrying them. Step 3: Replace polling carefully Use webhooks for prompt change notification and retain a lower-frequency reconciliation sync for completeness. Do not claim webhooks are a guaranteed event log. Step 4: Collapse repeat reads Cache stable company and project metadata, request collections instead of per-record reads, and use only documented filters, pagination, or sync actions. Step 5: Quantify savings Compare calls per useful changed record, failed-call share, compute time, transfer, backlog age, and infrastructure cost. Keep provider fees separate unless an authoritative contract supplies them. Step 6: Guard freshness Run a full reconciliation and compare state hashes. Roll back any optimization that misses records, delays required updates, or expands permissions. Authentication Optimized requests continue using the existing OAuth 2.0 Bearer token and company scope. Credential multiplication is not a cost or rate-control strategy and must never be used to bypass limits. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-cost-tuning