New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Procore Deploy Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof.

MITAuto-check passedDevelopment

Install Procore Deploy Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-deploy-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-deploy-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-deploy-integration .claude/skills/procore-deploy-integration && rm -rf skills-src

Use ~/.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/

Facts

Skill name
procore-deploy-integration
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
431 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof.

  • Works in 6 steps: Freeze the release → Review contract changes → Verify in sandbox → …
  • Shipping a connector
  • 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 Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof. Use when shipping a connector or embedded app change. Trigger with: "deploy a Procore integration", "promote a Procore app version", "release Procore manifest".

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 Procore Developer Portal app ownership, an installable app version, and authorized sandbox and production administrators.

It sits in Development, covering Changelog and release notes and Deployment. 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

  • Shipping a connector
  • Embedded app change
  • With: deploy a Procore integration
  • Promote a Procore app version

Example prompts

  • “deploy a Procore integration”
  • “promote a Procore app version”
  • “release Procore manifest”
  • “/procore-deploy-integration”

Requirements

  • Compatibility (from SKILL.md): Requires Procore Developer Portal app ownership, an installable app version, and authorized sandbox and production administrators.
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Freeze the release
  2. Review contract changes
  3. Verify in sandbox
  4. Approve promotion
  5. Deploy and canary
  6. Observe and settle

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:

    • Read
    • Grep
    • Write
    • Edit

    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 Procore Developer Portal app ownership, an installable app version, and authorized sandbox and production administrators.

    From compatibility in the SKILL.md frontmatter.

Context cost

Procore Deploy Integration 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 88 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

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). 431 words, ~1,102 tokens.

Download SKILL.mdSave it as .claude/skills/procore-deploy-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
procore-deploy-integration
description
Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof. Use when shipping a connector or embedded app change. Trigger with: "deploy a Procore integration", "promote a Procore app version", "release Procore manifest".
allowed-tools
Read, Grep, Write, Edit
compatibility
Requires Procore Developer Portal app ownership, an installable app version, and authorized sandbox and production administrators.
version
2.0.0
argument-hint
[app-version-and-release-scope]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, procore, deployment, release

Procore App Version Promotion

Overview

Promote the Procore app contract and the integration deployment as one reviewed release. Permission changes, installation steps, OAuth credentials, endpoint compatibility, and customer communication must align with the same semantic version.

Prerequisites

  • Immutable integration release and matching Procore app version
  • Permission and component diff, release notes, migration plan, and rollback owner
  • Sandbox installation, test company, production approver, and observation window

Instructions

Step 1: Freeze the release

Record source release identifier, app manifest version, endpoint inventory, configuration schema, and generated artifacts. Refuse moving tags or unreviewed builds.

Step 2: Review contract changes

Classify semantic version impact and inspect added permissions, components, callback URLs, post-install steps, and customer-facing behavior.

Step 3: Verify in sandbox

Install the version using the correct environment key, exercise authentication, required reads, expected denials, mutations in disposable data, webhooks, and cleanup.

Step 4: Approve promotion

Present evidence, permission diff, release notes, known limitations, support plan, and rollback. Require the authorized operator to promote the reviewed version.

Step 5: Deploy and canary

Deploy the matching integration release to a bounded tenant set, verify token acquisition and read-only access, then enable controlled business processing.

Step 6: Observe and settle

Monitor API activity, Integration Health, errors, rate budget, webhook deliveries, and backlog. Roll back the application release or integration according to the predeclared boundary.

Authentication

Deployment verification uses OAuth 2.0 credentials for each environment and never copies sandbox tokens into production. Production credential issuance and rotation stay within the Developer Portal and approved secret store.

Show full SKILL.md (182 more words)Show less

Tool Discipline

Use Read and Grep to inspect release artifacts, manifests, diffs, and evidence. Use Write or Edit only for the approved release record, configuration, test, or receipt; the actual Procore promotion requires an authorized portal operator.

Output

  • Immutable release and app-version evidence
  • Permission diff, sandbox proof, promotion approval, and canary results
  • Observation, rollback, and customer-impact receipt

Return exact versions, approvers, test results, rollout scope, health signals, and final disposition.

Examples

A manifest adds a new project-tool permission, so the release is classified accordingly and tested against both allowed and denied projects. The production canary does not begin until the portal version and deployed integration share the reviewed release.

Error Handling

FailureResponse
Manifest and deployment differStop rollout and rebuild from the immutable reviewed release.
Permission diff is unexplainedReject promotion until each new capability has an owner and test.
Sandbox proof failsRepair and create a new reviewed version rather than editing evidence.
Canary health degradesHalt expansion and execute the declared rollback boundary.

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-deploy-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Procore Deploy Integration 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.

Procore Deploy Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Procore Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Cline Desktop App Releasecline/cline70k—~4.5kAutomated safety check: PassApache-2.0
EverOS Release WorkflowEverMind-AI/EverOS13k—~1.3kAutomated safety check: PassApache-2.0
Releasengrok/ngrok-operator272—~2.7kAutomated safety check: PassMIT
Remotion Bits Releaseav/remotion-bits490—~1.2kAutomated safety check: PassNone
Cline CLI Release Publishercline/cline70k—~3.4kAutomated safety check: WarnApache-2.0

Similar skills

  • Cline Desktop App Release

    cline/cline

    Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.

    70k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

  • EverOS Release Workflow

    EverMind-AI/EverOS

    Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.

    13k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    ngrok/ngrok-operator

    Automates the ngrok-operator release process: gathers PR data, classifies changes by component (container, Helm chart, CRDs chart), generates changelogs, updates version files, and prepares the…

    272 GitHub stars~2.7k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Remotion Bits Release

    av/remotion-bits

    Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.

    490 GitHub stars~1.2k tokensUpdated 24 days ago
    DevelopmentAuto-check passed

  • Cline CLI Release Publisher

    cline/cline

    Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.

    70k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check: warnings

  • ClawRouter Release Checklist

    BlockRunAI/ClawRouter

    Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.

    6.6k GitHub stars~1.4k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing 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.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • 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.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • 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.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Procore Deploy Integration

What does Procore Deploy Integration do?

Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof. Procore Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Promote a Procore app version through sandbox verification, permission-diff review, semantic versioning, release notes, production promotion, and post-deploy proof.

When should I use Procore Deploy Integration?

Procore Deploy Integration fits situations like: shipping a connector; embedded app change; with: deploy a Procore integration; promote a Procore app version.

How do I install Procore Deploy Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-deploy-integration -a claude-code`. Or copy the skill folder (skills/.curated/procore-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/procore-deploy-integration in your project. Claude Code loads it when a task matches its description.

How do I install Procore Deploy Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill procore-deploy-integration -a codex`. Or copy the skill folder (skills/.curated/procore-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/procore-deploy-integration in your project. Codex loads it when a task matches its description.

Can I use Procore Deploy Integration 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-deploy-integration -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-deploy-integration, .gemini/skills/procore-deploy-integration, .github/skills/procore-deploy-integration and .opencode/skills/procore-deploy-integration in your project.

What does Procore Deploy Integration need to run?

SKILL.md names no scripts, command-line tools or credentials: Procore Deploy Integration is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires Procore Developer Portal app ownership, an installable app version, and authorized sandbox and production administrators..

Does Procore Deploy Integration 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 Deploy Integration 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 Deploy Integration use?

Procore Deploy Integration 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 Deploy Integration 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 261 tokens, read only when the agent opens those files.

What are the alternatives to Procore Deploy Integration?

Skills that share tags, products or a category with Procore Deploy Integration: Cline Desktop App Release (cline/cline, 70k stars), EverOS Release Workflow (EverMind-AI/EverOS, 13k stars), Release (ngrok/ngrok-operator, 272 stars) and Remotion Bits Release (av/remotion-bits, 490 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Procore Deploy Integration?

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.