procore-core-workflow-a
Procore core workflow a — 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".
Best use case
procore-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Procore core workflow a — 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".
Teams using procore-core-workflow-a should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/procore-core-workflow-a/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How procore-core-workflow-a Compares
| Feature / Agent | procore-core-workflow-a | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Procore core workflow a — 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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# 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
```python
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
```python
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
```python
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
```python
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
- [RFIs API](https://developers.procore.com/reference/rest/rfis)
- [Procore Developers](https://developers.procore.com/)
## Next Steps
Submittal workflow: `procore-core-workflow-b`Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".