Agent skill · software engineering · jeremylongshore
procore-data-handling
Transfer Procore documents, images, and attachments through the documented upload and secure-download contracts with checksums, bounded retention, and resource association. Use when importing, exporting, or migrating construction files. Trigger with: "upload a file to Procore", "download Procore documents securely", "migrate Procore attachments".
Why this skill is useful
Provides specific API call patterns and error handling for Procore's REST API 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 Governed File Transfer Overview Treat file bytes, upload sessions, returned storage instructions, resource association, and secure downloads as separate contracts. Never infer a permanent public URL or place customer documents in logs or diagnostic bundles. Prerequisites Approved company, project, target resource, file classification, and retention period Current upload or document endpoint selected for the resource and file size OAuth principal with required tool access and encrypted staging storage Instructions Step 1: Inventory the transfer Record source checksum, media type, size, logical owner, target resource, and duplicate policy. Reject unsupported or unclassified content before upload. Step 2: Choose the documented flow Use the current direct, segmented, unified, or resource-specific upload sequence documented for the target. Do not reuse a legacy upload contract merely because it returns an identifier. Step 3: Upload to provider storage Follow the returned storage request exactly, including method, fields, segment ordering, and completion step. Never send the Procore Bearer token to an unrelated storage host unless documentation explicitly requires it. Step 4: Associate the upload Use the documented upload identifier or attachment-by-reference shape for the target resource. Reconcile the resource after association. Step 5: Download securely Treat returned file URLs as opaque and potentially changing. Supply the Bearer token where secure-file guidance requires it and avoid persisting signed or redirect URLs. Step 6: Verify and expire Compare checksums or an approved content assertion, record association IDs, then remove temporary bytes and URLs according to retention policy. Authentication Procore resource and secure-file requests use an OAuth 2.0 Bearer token and required company context. Storage-upload authorization follows the provider-returned upload contract; do not leak the Procore token across hosts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-data-handling