Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
Implement a Procore submittal workflow with version-aware discovery, required-field validation, workflow-state reconciliation, and controlled notifications.
Install Procore Core Workflow B
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-b --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .claude/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .claude/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-bType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-b --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .agents/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .agents/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-b --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .cursor/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .cursor/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/procore-core-workflow-b--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-b --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .gemini/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .gemini/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-bInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .github/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .github/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-core-workflow-b --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/procore-core-workflow-b .opencode/skills/procore-core-workflow-b && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "procore-core-workflow-b" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/procore-core-workflow-b into .opencode/skills/procore-core-workflow-b/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procore-core-workflow-b", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
procore-core-workflow-b- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 442 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement a Procore submittal workflow with version-aware discovery, required-field validation, workflow-state reconciliation, and controlled notifications.
- Works in 6 steps: Select the endpoint version → Discover project data → Validate the proposal → …
- Reading submittals and their workflow data
- SKILL.md covers Overview, Prerequisites, Instructions and Authentication, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Procore Core Workflow B is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires a Procore project with Submittals enabled and an OAuth principal authorized for the chosen endpoint and workflow action.
It sits in Business, Finance & HR, covering Accounting and bookkeeping. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Reading submittals and their workflow data
- With: automate Procore submittals
- Create a Procore submittal
- Inspect submittal workflow
Example prompts
- “automate Procore submittals”
- “create a Procore submittal”
- “inspect submittal workflow”
- “/procore-core-workflow-b”
Requirements
- Compatibility (from SKILL.md): Requires a Procore project with Submittals enabled and an OAuth principal authorized for the chosen endpoint and workflow action.
- Pre-approved tools (allowed-tools): Read, Grep, Write, Edit
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.procore.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires a Procore project with Submittals enabled and an OAuth principal authorized for the chosen endpoint and workflow action.
From compatibility in the SKILL.md frontmatter.
Context cost
Procore Core Workflow B loads about 1.1k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 442 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 442 words, ~1,107 tokens.
Download SKILL.mdSave it as
.claude/skills/procore-core-workflow-b/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- procore-core-workflow-b
- description
- 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".
- allowed-tools
- Read, Grep, Write, Edit
- compatibility
- Requires a Procore project with Submittals enabled and an OAuth principal authorized for the chosen endpoint and workflow action.
- version
- 2.0.0
- argument-hint
- [submittal-operation-and-project]
- model
- inherit
- effort
- high
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, procore, submittals, approvals
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.
Show full SKILL.md (177 more words)Show less
Tool Discipline
Use Read and Grep to inspect endpoint versions, workflow fields, and project configuration. Use Write or Edit only for the approved adapter, test, proposal, or receipt; do not perform an unapproved submittal mutation.
Output
- Endpoint-version and permission decision
- Validated submittal proposal and approval record
- Read-after-write workflow-state receipt
Return the selected route version, project, submittal identifier, notification choice, observed workflow state, and rollback owner.
Examples
Before creating a submittal, an adapter reads the current reference, requests the project's next available number, resolves the manager and approvers, and previews whether emails will be sent. It then reconciles the returned workflow data after approval.
Error Handling
| Failure | Response |
|---|---|
| Only beta endpoint fits | Document the gap and obtain risk acceptance; do not label beta as stable. |
| Required actor or spec is missing | Stop and resolve the project dependency before mutation. |
| 403 or 422 response | Preserve the provider detail and verify permissions, fields, and workflow constraints. |
| Read-after-write disagrees | Treat Procore as authoritative and halt downstream publication until reconciled. |
Resources
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/procore-core-workflow-b of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Procore Core Workflow B next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Procore Core Workflow B this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| ERPClaw ERP Controlleravansaber/erpclaw | 116 | — | ~18k | Automated safety check: Pass | GPL-3.0 | |
| Odoo Agency Fleet Reviewerpipe-org/mcp-odoo | 421 | — | ~699 | Automated safety check: Pass | MIT | |
| Beancount Closebex-co/beancount-io | 297 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
ERPClaw ERP Controller
avansaber/erpclaw
Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
Forward Implementation First
Vuk97/forward-implementation-first
Keeps an agent building and validating real output instead of servicing its own bookkeeping.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Procore Core Workflow B
What does Procore Core Workflow B do?
Implement a Procore submittal workflow with version-aware discovery, required-field validation, workflow-state reconciliation, and controlled notifications. Procore Core Workflow B is an agent skill from jeremylongshore/tons-of-skills-marketplace. Implement a Procore submittal workflow with version-aware discovery, required-field validation, workflow-state reconciliation, and controlled notifications.
When should I use Procore Core Workflow B?
Procore Core Workflow B fits situations like: reading submittals and their workflow data; with: automate Procore submittals; create a Procore submittal; inspect submittal workflow.
How do I install Procore Core Workflow B in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a claude-code`. Or copy the skill folder (skills/.curated/procore-core-workflow-b in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/procore-core-workflow-b in your project. Claude Code loads it when a task matches its description.
How do I install Procore Core Workflow B in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a codex`. Or copy the skill folder (skills/.curated/procore-core-workflow-b in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/procore-core-workflow-b in your project. Codex loads it when a task matches its description.
Can I use Procore Core Workflow B in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-core-workflow-b -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/procore-core-workflow-b, .gemini/skills/procore-core-workflow-b, .github/skills/procore-core-workflow-b and .opencode/skills/procore-core-workflow-b in your project.
What does Procore Core Workflow B need to run?
SKILL.md names no scripts, command-line tools or credentials: Procore Core Workflow B is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires a Procore project with Submittals enabled and an OAuth principal authorized for the chosen endpoint and workflow action..
Does Procore Core Workflow B access the network?
SKILL.md names 1 domain. As links in the text: developers.procore.com. This is read from the text; nothing was executed.
Is Procore Core Workflow B safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Procore Core Workflow B use?
Procore Core Workflow B is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Procore Core Workflow B use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 259 tokens, read only when the agent opens those files.
What are the alternatives to Procore Core Workflow B?
Skills that share tags, products or a category with Procore Core Workflow B: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Procore Core Workflow B?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.