Agent skill

Procore Observability

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

Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership.

MITAuto-check passedDevOps & Cloud

Install Procore Observability

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

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

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

At a glance

Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership.

  • Works in 6 steps: Export provider evidence → Join route ownership → Monitor provider limits → …
  • Defining dashboards
  • 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 Observability is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership. Use when defining dashboards, alerts, service objectives, or a regular health-review cadence. Trigger with: "monitor Procore integration", "review Procore API activity", "alert on Procore health".

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 access to Procore Developer Portal health data plus application metrics, logs, queue state, and deployment identifiers.

It sits in DevOps & Cloud, covering Observability and Webhooks. 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

  • Defining dashboards
  • Service objectives
  • A regular health-review cadence
  • With: monitor Procore integration

Example prompts

  • “monitor Procore integration”
  • “review Procore API activity”
  • “alert on Procore health”
  • “/procore-observability”

Requirements

  • Compatibility (from SKILL.md): Requires access to Procore Developer Portal health data plus application metrics, logs, queue state, and deployment identifiers.
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit

Workflow steps

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

  1. Export provider evidence
  2. Join route ownership
  3. Monitor provider limits
  4. Monitor data freshness
  5. Define actionable alerts
  6. Close the loop

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 access to Procore Developer Portal health data plus application metrics, logs, queue state, and deployment identifiers.

    From compatibility in the SKILL.md frontmatter.

Context cost

Procore Observability loads about 1.1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 437 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
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.3k

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). 437 words, ~1,085 tokens.

Download SKILL.mdSave it as .claude/skills/procore-observability/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
procore-observability
description
Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership. Use when defining dashboards, alerts, service objectives, or a regular health-review cadence. Trigger with: "monitor Procore integration", "review Procore API activity", "alert on Procore health".
allowed-tools
Read, Grep, Write, Edit
compatibility
Requires access to Procore Developer Portal health data plus application metrics, logs, queue state, and deployment identifiers.
version
2.0.0
argument-hint
[app-and-service-objectives]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, procore, observability, integration-health

Procore Integration Health Observability

Overview

Combine provider-side observations with application-side service signals. Procore's Integration Health and API Call Activity Report identify unhealthy response patterns and routes, while the integration must supply latency, backlog, freshness, reconciliation, and release context.

Prerequisites

  • App owner with Developer Portal access and a recurring review cadence
  • Normalized route, status, latency, retry, queue, webhook, and freshness telemetry
  • Release identifiers, endpoint owners, alert destinations, and incident runbook

Instructions

Step 1: Export provider evidence

Review Integration Health and download the production API activity report. Preserve report time range, app identity, and a checksum in the audit receipt.

Step 2: Join route ownership

Map normalized route, method, status, and count to the responsible service and adapter. Flag unknown traffic as a legacy deployment or credential-compromise hypothesis.

Step 3: Monitor provider limits

Track rate limit, remaining budget, reset time, Retry-After, 401, 403, 404, 422, 429, and 5xx outcomes by route and release.

Step 4: Monitor data freshness

Track webhook acknowledgment and delivery outcomes, queue age, deduplication, reconciliation cursor age, changed records, and parity failures.

Step 5: Define actionable alerts

Every alert names the affected tenant boundary, route owner, runbook, severity, and recovery condition. Exclude tokens, payloads, names, and signed URLs.

Step 6: Close the loop

After remediation, verify application metrics and the provider observation history. Record when provider-side status may lag the underlying fix.

Authentication

Provider evidence is accessed through authorized Developer Portal sessions, while API probes use the intended OAuth 2.0 principal. Observability stores aliases and normalized metadata, never tokens or raw construction payloads.

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

Tool Discipline

Use Read and Grep to inspect reports, telemetry, releases, and runbooks. Use Write or Edit only for the approved dashboard, alert, mapping, or redacted receipt; do not broaden log collection to raw customer data.

Output

  • Provider and application signal inventory
  • Route ownership, objectives, alerts, and runbook links
  • Health-review and remediation verification receipt

Return current health, dominant routes and failures, freshness risk, owner, action, and expected recovery signal.

Examples

An alert ties rising 403 counts on one normalized route to a specific adapter release and company alias. The operator fixes routing, verifies the error rate locally, and then watches the provider's daily health history catch up.

Error Handling

FailureResponse
API traffic has no ownerTreat it as potentially stale or compromised and investigate credential usage.
Provider and app metrics disagreePreserve both time windows and reconcile sampling, release, and tenant scope.
Alert contains payload dataRemove the field and replace it with an alias or hash.
Health status remains staleCheck documented refresh cadence before declaring the fix ineffective.

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

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Procore Observability 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 Observability compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Procore Observability this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Cx Observability Setupcoralogix/cx-cli121—~2.3kAutomated safety check: PassApache-2.0
Debug Cloudflare Workers ObservabilityConsensys/c0105—~1.2kAutomated safety check: NotesLGPL-3.0
Coralogix Docscoralogix/cx-cli121—~1.2kAutomated safety check: PassApache-2.0
Cost Exportruvnet/ruflo74k—~687Automated safety check: NotesMIT
Distributed Tracingwshobson/agents40k12 repos~527Automated safety check: PassMIT

Similar skills

  • Cx Observability Setup

    coralogix/cx-cli

    A skill your agent uses when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack…

    121 GitHub stars~2.3k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction.

    105 GitHub stars~1.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Coralogix Docs

    coralogix/cx-cli

    Search and read official Coralogix platform documentation using cx docs search and cx docs fetch.

    121 GitHub stars~1.2k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Cost Export

    ruvnet/ruflo

    Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)

    74k GitHub stars~687 tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 12 repos~527 tokens
    DevOps & CloudAuto-check passed
  • Reviews and authors Cloudflare Workers code against production best practices.

    127 GitHub starsUsed in 6 repos~1.8k tokens
    DevOps & CloudAuto-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

Questions about Procore Observability

What does Procore Observability do?

Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership. Procore Observability is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor Procore Integration Health, API activity, rate budget, webhook deliveries, and synchronization freshness with route-level ownership.

When should I use Procore Observability?

Procore Observability fits situations like: defining dashboards; service objectives; A regular health-review cadence; with: monitor Procore integration.

How do I install Procore Observability in Claude Code?

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

How do I install Procore Observability in Codex?

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

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

What does Procore Observability need to run?

SKILL.md names no scripts, command-line tools or credentials: Procore Observability is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires access to Procore Developer Portal health data plus application metrics, logs, queue state, and deployment identifiers..

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

Procore Observability 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 Observability use?

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

What are the alternatives to Procore Observability?

Skills that share tags, products or a category with Procore Observability: Cx Observability Setup (coralogix/cx-cli, 121 stars), Debug Cloudflare Workers Observability (Consensys/c0, 105 stars), Coralogix Docs (coralogix/cx-cli, 121 stars) and Cost Export (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Procore Observability?

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.