Agent skill · software engineering · jeremylongshore
procore-debug-bundle
Produce a minimal redacted Procore diagnostic manifest for escalation without collecting credentials, customer payloads, or attachment contents. Use when an API failure needs handoff to engineering or Procore support. Trigger with: "build a Procore debug bundle", "prepare Procore support evidence", "redact Procore diagnostics".
Why this skill is useful
Provides specific API integration patterns and error handling for Procore that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, npm, pip 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
Redacted Procore Diagnostic Manifest Overview Build a manifest of request metadata and assertions, not a raw archive. Procore support can investigate with method, URL, status, sanitized headers and body, and occurrence time; secrets and construction data increase risk without improving diagnosis. Prerequisites Incident identifier, owner, audience, retention deadline, and approved destination Exact failing request window and normalized route Organization redaction rules for identities, projects, documents, and credentials Instructions Step 1: Declare collection scope List the exact evidence fields required for the failure class. Reject recursive log directories, database dumps, environment files, OAuth responses, and attachment collections. Step 2: Collect metadata Capture UTC occurrence time, environment, method, normalized URL, status, elapsed time, API version, company and project aliases, rate headers, retry header, and application release identifier. Step 3: Sanitize content Remove Authorization and destination headers, client credentials, tokens, cookies, user details, project names, query secrets, request bodies, response payloads, and signed file URLs unless a reviewed minimal fragment is essential. Step 4: Validate redaction Grep the staged manifest for secret patterns and prohibited field names. Inspect every remaining value manually and replace provider identifiers with stable aliases where possible. Step 5: Seal and transfer Write a checksum, collector identity, scope statement, redaction result, expiry, and access list. Transfer only through the approved encrypted channel. Step 6: Delete on schedule Record the deletion owner and deadline, and preserve only the non-sensitive incident receipt after the diagnostic artifact expires. Authentication This workflow never acquires or refreshes OAuth credentials. Existing Bearer tokens, client secrets, refresh tokens, webhook destination headers, cookies, and signed URLs are prohibited from the manifest. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-debug-bundle