Agent skill · software engineering · jeremylongshore
procore-core-workflow-a
Implement a governed Procore RFI lifecycle from read-only discovery through an approved create or update. Use when integrating RFI intake, assignment, response tracking, attachments, or closure without guessing workflow transitions. Trigger with: "automate Procore RFIs", "create a Procore RFI", "sync RFI status".
Why this skill is useful
Adds specific API commands and workflows for managing RFIs in Procore 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 RFI Lifecycle Overview Treat an RFI as a permissioned construction record with project configuration and business transitions, not generic CRUD. Derive fields and allowed actions from the current RFI reference and target project before submitting a mutation. Prerequisites Target company and project identifiers with the RFI tool enabled OAuth principal permitted for the exact read or write operation Current RFI endpoint reference, project field configuration, and approval owner Instructions Step 1: Discover the project contract List or show a representative RFI to confirm response shape, configurable fields, status values, and project access. Follow Link-header pagination for inventory reads. Step 2: Build the intent Capture subject, question, RFI manager, assignees, due-date policy, attachments, and notification choice. Resolve every referenced user or resource inside the same project. Step 3: Validate without side effects Check required fields against the live endpoint reference and project configuration. Present a sanitized mutation preview and require an identified approver. Step 4: Execute once Send the documented request only after approval. Record the response ID and status immediately; never infer success from a network timeout. Step 5: Reconcile lifecycle Read the RFI after each material transition. Drive responses, distribution, acceptance, or closure only through documented endpoints and fields rather than invented status strings. Step 6: Preserve audit evidence Store identifiers, before-and-after state hashes, actor, timestamp, and outcome without construction narrative or attachment contents. Authentication RFI calls use an OAuth 2.0 Bearer token and the required company routing context. Effective access comes from the user or DMSA permissions, project membership, and whether the RFI tool is enabled. Tool Discipline Use Read and Grep to inspect endpoint contracts, project configuration, and existing adapters. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-core-workflow-a--cf4f59