Agent skill · software engineering · jeremylongshore
procore-core-workflow-b
Implement a Procore submittal workflow with version-aware discovery, required-field validation, workflow-state reconciliation, and controlled notifications. Use when listing, creating, routing, or reading submittals and their workflow data. Trigger with: "automate Procore submittals", "create a Procore submittal", "inspect submittal workflow".
Why this skill is useful
Adds specific API commands and integration patterns for managing submittals 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 Version-Aware Submittal Workflow Overview Submittal endpoints coexist across versions and may expose beta surfaces. Select the documented version per operation, preserve company routing and notification controls, and reconcile workflow state instead of assuming a generic approve-or-reject contract. Prerequisites Target company and project with Submittals enabled Current endpoint version and changelog reviewed for every intended operation Required managers, approvers, specification context, and notification policy resolved Instructions Step 1: Select the endpoint version Open the current Submittals API reference and choose the supported route for the required operation. Record whether a surface is beta and obtain explicit risk acceptance before using it. Step 2: Discover project data List a bounded page of submittals and retrieve workflow data for a representative record. Capture required headers, fields, allowed filters, and pagination metadata. Step 3: Validate the proposal Resolve project users and specification references, obtain any next-number value through the documented endpoint, and make email behavior explicit. Never invent a workflow status. Step 4: Approve the mutation Render a sanitized request preview with target project, selected API version, recipients, and expected outcome. Require approval before creating or changing a submittal. Step 5: Execute and reconcile Send the mutation once, then fetch the submittal and its workflow data. Confirm the observed workflow state rather than trusting a local projection. Step 6: Record compatibility Keep endpoint-version selection in an adapter and test both current response fields and failure shapes so future migrations remain bounded. Authentication Submittal calls authenticate with an OAuth 2.0 Bearer token. Provide Procore-Company-Id wherever the endpoint reference requires it, and rely on the principal's project and Submittals permissions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-core-workflow-b