From procore-pack
Lists Procore projects, creates RFIs with assignee, and lists submittals via Python requests to REST API. For construction management integrations after auth setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/procore-pack:procore-hello-worldThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
List companies and projects, then create your first RFI using the Procore REST API.
List companies and projects, then create your first RFI using the Procore REST API.
procore-install-auth with valid access tokencompany_id = 12345 # From install-auth step
projects = requests.get(
f"https://api.procore.com/rest/v1.0/projects?company_id={company_id}",
headers=headers,
)
for p in projects.json():
print(f"Project: {p['name']} (ID: {p['id']})")
project_id = 67890
rfi = requests.post(
f"https://api.procore.com/rest/v1.0/projects/{project_id}/rfis",
headers={**headers, "Content-Type": "application/json"},
json={
"rfi": {
"subject": "Structural beam specification clarification",
"question_body": "Please confirm the steel grade for beams on Level 3.",
"assignee_id": 11111, # User ID of the person to respond
}
},
)
rfi.raise_for_status()
print(f"RFI created: #{rfi.json()['number']} — {rfi.json()['subject']}")
submittals = requests.get(
f"https://api.procore.com/rest/v1.0/projects/{project_id}/submittals",
headers=headers,
)
for s in submittals.json():
print(f"Submittal #{s['number']}: {s['title']} — Status: {s['status']['name']}")
| Error | Cause | Solution |
|---|---|---|
404 Project not found | Wrong project_id | List projects first |
422 Missing subject | Required field | Include subject in RFI |
403 Forbidden | No project access | Check user permissions |
Full RFI workflow: procore-core-workflow-a
npx claudepluginhub kriptoburak/jeremylongshore-claude-code-plugins-plus-skills --plugin procore-pack5plugins reuse this skill
First indexed Jul 10, 2026
Lists companies and projects, creates RFIs, and lists submittals using the Procore REST API. Requires a valid access token from procore-install-auth.
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.