From procore-pack
Creates and manages Procore submittals via API: assign reviewers, update approvals, filter lists using Python requests. For construction project management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/procore-pack:procore-core-workflow-bThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a submittal workflow: create submittals, assign reviewers, track approvals, and manage the review cycle.
Build a submittal workflow: create submittals, assign reviewers, track approvals, and manage the review cycle.
procore-core-workflow-a (RFIs)submittal = requests.post(
f"{BASE}/projects/{project_id}/submittals",
headers={**headers, "Content-Type": "application/json"},
json={
"submittal": {
"title": "Concrete mix design — Foundation",
"specification_section": "03 30 00",
"description": "Concrete mix design for foundation pour, 4000 PSI.",
"received_from_id": 33333, # Subcontractor
"approver_id": 44444, # Project engineer
"due_date": "2026-04-20",
}
},
)
submittal_id = submittal.json()["id"]
print(f"Submittal #{submittal.json()['number']} created")
# Approve the submittal
requests.patch(
f"{BASE}/projects/{project_id}/submittals/{submittal_id}",
headers={**headers, "Content-Type": "application/json"},
json={"submittal": {"status_id": 2}}, # 2 = Approved
)
# Get all pending submittals
pending = requests.get(
f"{BASE}/projects/{project_id}/submittals",
headers=headers,
params={"filters[status_id]": 1}, # 1 = Open/Pending
)
for s in pending.json():
print(f" #{s['number']}: {s['title']} — Due: {s['due_date']}")
| Error | Cause | Solution |
|---|---|---|
422 Missing approver | Required field | Set approver_id |
403 Cannot approve | Not the approver | Only assigned approver can approve |
Handle events: procore-webhooks-events
npx claudepluginhub ia23a-lachnita/claude-code-plugins-plus-fix-skills --plugin procore-pack5plugins reuse this skill
First indexed Jul 10, 2026
Creates submittals, assigns reviewers, tracks approvals, and manages the review cycle via the Procore API.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.