Agent skill · software engineering · jeremylongshore
procore-deploy-integration
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".
Why this skill is useful
Provides specific implementation patterns and error handling for Procore API integration that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, npm, pip installed locally. Requires procore account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-deploy-integration--89504c