Procore core workflow a

Skill jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/procore-core-workflow-a

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill procore-core-workflow-a

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Procore core workflow a \u2014 construction management platform integration. \ Use when working with Procore API for project management, RFIs, or submittals. \ Trigger with phrases like "procore core workflow a", "procore-core-workflow-a"\ .

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 647 tokens by cl100k_base, as published. Nobody here has run it

Procore Core Workflow A

Overview

Build a complete RFI workflow: create, assign, respond, track, and close RFIs using the Procore API.

Prerequisites

Completed procore-hello-world with project access

Instructions

Step 1: Create RFI with Full Details

rfi_data = {
    "rfi": {
        "subject": "HVAC duct routing — Level 2 conflict",
        "question_body": "The HVAC ducts conflict with structural beams at grid B-4. Need routing alternatives.",
        "assignee_id": 11111,
        "rfi_manager_id": 22222,
        "due_date": "2026-04-15",
        "priority": "high",
        "cost_impact": "yes",
        "schedule_impact": "yes",
    }
}
rfi = requests.post(
    f"{BASE}/projects/{project_id}/rfis",
    headers={**headers, "Content-Type": "application/json"},
    json=rfi_data,
)
rfi_id = rfi.json()["id"]

Step 2: Add Response to RFI

response = requests.post(
    f"{BASE}/projects/{project_id}/rfis/{rfi_id}/responses",
    headers={**headers, "Content-Type": "application/json"},
    json={
        "response": {
            "body": "Route ducts below beam using 8-inch offset. See attached drawing.",
        }
    },
)

Step 3: Track RFI Status

rfi_detail = requests.get(f"{BASE}/projects/{project_id}/rfis/{rfi_id}", headers=headers)
data = rfi_detail.json()
print(f"RFI #{data['number']}: {data['status']['name']}")
print(f"  Days open: {data.get('days_open', 0)}")
print(f"  Responses: {len(data.get('responses', []))}")

Step 4: Close RFI

requests.patch(
    f"{BASE}/projects/{project_id}/rfis/{rfi_id}",
    headers={**headers, "Content-Type": "application/json"},
    json={"rfi": {"status": "closed"}},
)

Output

RFI created with full metadata (priority, impacts, due date)
Responses added to RFI thread
Status tracked through lifecycle
RFI closed upon resolution

Error Handling

Error	Cause	Solution
`422 Invalid assignee`	User not on project	Verify user is a project member
`403 Cannot close`	Not RFI manager	Only RFI manager can close
Missing responses	RFI in draft status	Distribute RFI first

Resources

Next Steps

Submittal workflow: procore-core-workflow-b