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 Security Basics

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

Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation.

MITAuto-check passedBackend & APIs

Install Procore Security Basics

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace procore-security-basics --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-security-basics .claude/skills/procore-security-basics && 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-security-basics
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
438 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation.

  • Works in 6 steps: Inventory secrets and principals → Prove least privilege → Bind company routing → …
  • Reviewing a new app
  • 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 Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation. Use when reviewing a new app, hardening production, or responding to credential exposure. Trigger with: "secure a Procore integration", "review Procore API security", "rotate Procore credentials".

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 application architecture, data classification, permission inventory, and access to the Procore app configuration.

It sits in Backend & APIs, covering Webhooks, Threat modeling and OAuth and OpenID Connect. 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

  • Reviewing a new app
  • Hardening production
  • Responding to credential exposure
  • With: secure a Procore integration

Example prompts

  • “secure a Procore integration”
  • “review Procore API security”
  • “rotate Procore credentials”
  • “/procore-security-basics”

Requirements

  • Compatibility (from SKILL.md): Requires application architecture, data classification, permission inventory, and access to the Procore app configuration.
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit

Workflow steps

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

  1. Inventory secrets and principals
  2. Prove least privilege
  3. Bind company routing
  4. Protect data paths
  5. Harden mutations
  6. Exercise response

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 application architecture, data classification, permission inventory, and access to the Procore app configuration.

    From compatibility in the SKILL.md frontmatter.

Context cost

Procore Security Basics 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 89 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
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). 438 words, ~1,121 tokens.

Download SKILL.mdSave it as .claude/skills/procore-security-basics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
procore-security-basics
description
Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation. Use when reviewing a new app, hardening production, or responding to credential exposure. Trigger with: "secure a Procore integration", "review Procore API security", "rotate Procore credentials".
allowed-tools
Read, Grep, Write, Edit
compatibility
Requires application architecture, data classification, permission inventory, and access to the Procore app configuration.
version
2.0.0
argument-hint
[application-and-data-classification]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, procore, security, threat-modeling

Procore Integration Security Boundary

Overview

Protect construction data by constraining identity, company and project scope, transport, stored artifacts, and operator actions. Procore authorization is permission-based; neither a valid token nor a successful request proves least privilege.

Prerequisites

  • Data-flow diagram, asset classification, trust boundaries, and named security owner
  • OAuth grant, credential locations, DMSA manifest, and permitted-project inventory
  • Webhook destinations, file flows, log sinks, support path, and revocation procedure

Instructions

Step 1: Inventory secrets and principals

Locate client secrets, access and refresh tokens, webhook destination secrets, cookies, and signed URLs. Ensure each secret has an owner, approved store, rotation path, and narrow audience.

Step 2: Prove least privilege

Map every endpoint to its required Procore tool permission and project scope. For DMSAs, compare the manifest with installed permitted projects and remove unexplained access.

Step 3: Bind company routing

Carry company context explicitly and validate Procore-Company-Id where required. Prevent a multi-company worker or event handler from reusing stale tenant context.

Step 4: Protect data paths

Use supported TLS, authenticate secure-file downloads as documented, sanitize logs and traces, and keep payload retention proportional to the business requirement.

Step 5: Harden mutations

Separate preview from execution, require approval for consequential changes, validate project ownership, and reconcile provider state after writes.

Step 6: Exercise response

Test revocation, credential rotation, app disconnection, webhook-secret rotation, and audit retrieval. Record recovery time without exposing the secrets under test.

Authentication

Procore API access uses OAuth 2.0 Bearer tokens from Authorization Code or DMSA Client Credentials. Store client secrets server-side, rotate credentials regularly, and revoke authorization when access is no longer valid.

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

Tool Discipline

Use Read and Grep to inspect architecture, manifests, configuration, and evidence. Use Write or Edit only for the approved threat model, security change, test, or redacted receipt; provider permission changes require administrator approval.

Output

  • Threat model and endpoint-to-permission map
  • Secret, routing, file, webhook, and mutation controls
  • Rotation, revocation, and negative-access test evidence

Return risks by severity, bounded remediation, owner, due condition, and verification status.

Examples

A multi-company connector passes company context with every job and tests that a permitted DMSA cannot read an unselected project. Logs retain normalized routes and status codes while excluding tokens, project names, payloads, and signed file URLs.

Error Handling

FailureResponse
Credential exposedRevoke or rotate immediately, invalidate caches, and scrub derived artifacts.
Excess project accessStop affected processing and reduce DMSA or user scope before resuming.
Company context is ambiguousFail closed rather than dispatching against a default tenant.
Secure file URL is loggedRemove and expire the artifact, then repair logging and retrieval boundaries.

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-security-basics of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Procore Security Basics 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 Security Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Procore Security Basics this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Security Threat Modelingdevcodex-labs/devcodex439—~771Automated safety check: PassAGPL-3.0
Stripe Best Practiceskanchengw/cnllm1732 repos~925Automated safety check: PassApache-2.0
Discord Php Bot Securitydiscord-php/DiscordPHP1.1k—~1.2kAutomated safety check: NotesMIT
GitHub OAuth Nango IntegrationAgentWorkforce/relay8691 repos~3.4kAutomated safety check: PassApache-2.0
Add OAuth Integrationrome-os/rome743—~3.6kAutomated safety check: PassMIT

Similar skills

  • Security Threat Modeling

    devcodex-labs/devcodex

    安全威胁建模专家 Owner — 当任务涉及权限、认证、授权、输入输出信任边界、密钥策略、审计、攻击面、Webhook/OAuth、敏感操作或用户要求安全专家视角时使用；要求识别滥用路径并绑定缓解验证。

    439 GitHub stars~771 tokensUpdated 23 days ago
    Backend & APIsAuto-check passed

  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    173 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed

  • Discord Php Bot Security

    discord-php/DiscordPHP

    Audit checklist for DiscordPHP bots and API libraries — stop the bot token leaking to third-party APIs or logs, keep secrets out of customids and exception messages, use constant-time comparison and…

    1.1k GitHub stars~1.2k tokensUpdated 4 days ago
    Backend & APIsAuto-check: notes

  • GitHub OAuth Nango Integration

    AgentWorkforce/relay

    A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling

    869 GitHub starsUsed in 1 repo~3.4k tokens
    Backend & APIsAuto-check passed

  • Add OAuth Integration

    rome-os/rome

    Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    743 GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Triggers Guide

    OtoDock/oto-dock

    Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…

    190 GitHub stars~3k tokensUpdated 2 days ago
    Backend & APIsAuto-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 Security Basics

What does Procore Security Basics do?

Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation. Procore Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Threat-model a Procore integration across OAuth credentials, company routing, DMSA permissions, webhooks, files, logs, and revocation.

When should I use Procore Security Basics?

Procore Security Basics fits situations like: reviewing a new app; hardening production; responding to credential exposure; with: secure a Procore integration.

How do I install Procore Security Basics in Claude Code?

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

How do I install Procore Security Basics in Codex?

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

Can I use Procore Security Basics 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-security-basics -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-security-basics, .gemini/skills/procore-security-basics, .github/skills/procore-security-basics and .opencode/skills/procore-security-basics in your project.

What does Procore Security Basics need to run?

SKILL.md names no scripts, command-line tools or credentials: Procore Security Basics is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires application architecture, data classification, permission inventory, and access to the Procore app configuration..

Does Procore Security Basics 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 Security Basics 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 Security Basics use?

Procore Security Basics 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 Security Basics use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 284 tokens, read only when the agent opens those files.

What are the alternatives to Procore Security Basics?

Skills that share tags, products or a category with Procore Security Basics: Security Threat Modeling (devcodex-labs/devcodex, 439 stars), Stripe Best Practices (kanchengw/cnllm, 173 stars), Discord Php Bot Security (discord-php/DiscordPHP, 1.1k stars) and GitHub OAuth Nango Integration (AgentWorkforce/relay, 869 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Procore Security Basics?

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.