Sf Datacloud Act
Jaganpro/sf-skills
Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills.
Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation.
Install Salesforce Observability
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-observability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-observability --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/salesforce-observability .claude/skills/salesforce-observability && 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 "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .claude/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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/salesforce-observabilityType 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 salesforce-observability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-observability --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/salesforce-observability .agents/skills/salesforce-observability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .agents/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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 salesforce-observability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-observability --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/salesforce-observability .cursor/skills/salesforce-observability && 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 "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .cursor/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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/salesforce-observability--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 salesforce-observability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-observability --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/salesforce-observability .gemini/skills/salesforce-observability && 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 "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .gemini/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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 salesforce-observabilityInstalls 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 salesforce-observability -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/salesforce-observability .github/skills/salesforce-observability && 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 "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .github/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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 salesforce-observability -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 salesforce-observability --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/salesforce-observability .opencode/skills/salesforce-observability && 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 "salesforce-observability" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-observability into .opencode/skills/salesforce-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-observability", 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
salesforce-observability- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 428 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation.
- Works in 7 steps: Define availability, latency,… → Instrument the adapter with redacted… → Collect Salesforce platform status,… → …
- Designing monitoring
- SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Salesforce Observability is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation. Use when designing monitoring. Trigger with "monitor Salesforce integration".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code; log, Event Monitoring, alert, and data access require entitlement and security approval
It sits in Sales & Support, covering CRM management, Observability and Accounting and bookkeeping. It works with Salesforce. 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
- Designing monitoring
- With monitor Salesforce integration
Example prompts
- “monitor Salesforce integration”
- “/salesforce-observability”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; log, Event Monitoring, alert, and data access require entitlement and security approval
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Define availability, latency, throughput, error, freshness, completeness, duplicate, limit, job, event-lag, and business-invariant…
- Instrument the adapter with redacted request IDs, operation class, API version, timing, outcome, retry, and reconciliation state.
- Collect Salesforce platform status, relevant limit and header values, async job summaries, event metrics, and entitled logs.
- Normalize timestamps, org and environment aliases, deployment IDs, and correlation IDs without exposing customer record data.
- Build dashboards by environment and workload with freshness labels and separate technical from business-correctness views.
- Alert on sustained objective breaches, capacity margin, auth failure, job failure, event gap, wrong-org binding, and reconciliation…
- Test alerts and runbooks in non-production, measure noise and blind spots, and assign review and retention owners.
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:
ReadGlobGrepWebFetchWriteEdit
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):
status.salesforce.comdeveloper.salesforce.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
Designed for Claude Code; log, Event Monitoring, alert, and data access require entitlement and security approval
From compatibility in the SKILL.md frontmatter.
Context cost
Salesforce Observability loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 428 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). 428 words, ~1,105 tokens.
Download SKILL.mdSave it as
.claude/skills/salesforce-observability/SKILL.md (or your agent's skills folder).- name
- salesforce-observability
- description
- Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation. Use when designing monitoring. Trigger with "monitor Salesforce integration".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; log, Event Monitoring, alert, and data access require entitlement and security approval
- argument-hint
- [integration] [service-objective]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, salesforce, observability, monitoring, event-monitoring
- model
- inherit
- effort
- high
Salesforce Integration Observability and Reconciliation
Overview
Connect technical telemetry to Salesforce platform state and business correctness without exporting sensitive records into monitoring systems.
Prerequisites
- System context, service and business objectives, APIs, jobs, event channels, orgs, and owners
- Current Salesforce Status, Limits, EventLogFile or entitled Event Monitoring, async-job, and event-usage surfaces
- Telemetry data classification, redaction, retention, alert routing, incident, and reconciliation policies
Tool Discipline
Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.
Current Contract
Salesforce Status, REST limits, response headers, async jobs, platform-event usage, debug logs, and Event Monitoring expose different signals with different entitlements and delays. Limits resource values can lag recent consumption.
Authentication
Use separate read-only monitoring access with minimum permissions. Never emit access tokens, session IDs, authorization headers, raw SOQL results, record payloads, or unrestricted user and org identifiers as telemetry.
Instructions
- Define availability, latency, throughput, error, freshness, completeness, duplicate, limit, job, event-lag, and business-invariant objectives.
- Instrument the adapter with redacted request IDs, operation class, API version, timing, outcome, retry, and reconciliation state.
- Collect Salesforce platform status, relevant limit and header values, async job summaries, event metrics, and entitled logs.
- Normalize timestamps, org and environment aliases, deployment IDs, and correlation IDs without exposing customer record data.
- Build dashboards by environment and workload with freshness labels and separate technical from business-correctness views.
- Alert on sustained objective breaches, capacity margin, auth failure, job failure, event gap, wrong-org binding, and reconciliation mismatch.
- Test alerts and runbooks in non-production, measure noise and blind spots, and assign review and retention owners.
Show full SKILL.md (149 more words)Show less
Approval Boundaries
Do not enable broad logging, retrieve sensitive event files, expand retention, export record data, or create production alerts without security, admin, and incident-owner approval.
Output
Return the signal catalog, instrumentation contract, dashboards, alerts, redaction and retention rules, runbook links, test receipt, blind spots, and owners.
Error Handling
| Condition | Response |
|---|---|
| Signal is unavailable without an add-on | Document the entitlement boundary and implement a lower-risk compensating signal. |
| Telemetry contains record or credential data | Block export, purge according to policy, rotate exposed credentials, and repair redaction. |
| Platform is healthy but business reconciliation fails | Escalate as an application or data incident rather than closing on status alone. |
Example
A redacted completion receipt might look like this:
service=customer-sync; slo=defined; traces=redacted; limits=dated; jobs=monitored; event-gap=alerted; reconcile=exactResources
Next Steps
Run the workflow first in the lowest-risk authorized org and preserve its redacted receipt. Schedule a review against the next Salesforce seasonal release and the customer change calendar.
© 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
Just SKILL.md in skills/.curated/salesforce-observability of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Salesforce 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Salesforce Observability this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sf Datacloud ActJaganpro/sf-skills | 424 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Sf Datacloud ConnectJaganpro/sf-skills | 424 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Sf Datacloud HarmonizeJaganpro/sf-skills | 424 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sf DebugJaganpro/sf-skills | 424 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Sf Datacloud RetrieveJaganpro/sf-skills | 424 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Sf Datacloud Connect
Jaganpro/sf-skills
Salesforce Data Cloud Connect phase. An agent skill from Jaganpro/sf-skills.
Sf Datacloud Harmonize
Jaganpro/sf-skills
Salesforce Data Cloud Harmonize phase. An agent skill from Jaganpro/sf-skills.
Sf Debug
Jaganpro/sf-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring.
Sf Datacloud Retrieve
Jaganpro/sf-skills
Salesforce Data Cloud Retrieve phase. An agent skill from Jaganpro/sf-skills.
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
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
Works with
Categories
Questions about Salesforce Observability
What does Salesforce Observability do?
Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation. Salesforce Observability is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation.
When should I use Salesforce Observability?
Salesforce Observability fits situations like: designing monitoring; with monitor Salesforce integration.
How do I install Salesforce Observability in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-observability -a claude-code`. Or copy the skill folder (skills/.curated/salesforce-observability in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/salesforce-observability in your project. Claude Code loads it when a task matches its description.
How do I install Salesforce Observability in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-observability -a codex`. Or copy the skill folder (skills/.curated/salesforce-observability in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/salesforce-observability in your project. Codex loads it when a task matches its description.
Can I use Salesforce 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 salesforce-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/salesforce-observability, .gemini/skills/salesforce-observability, .github/skills/salesforce-observability and .opencode/skills/salesforce-observability in your project.
What does Salesforce Observability need to run?
SKILL.md names no scripts, command-line tools or credentials: Salesforce Observability is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; log, Event Monitoring, alert, and data access require entitlement and security approval.
Does Salesforce Observability access the network?
SKILL.md names 2 domains. As links in the text: status.salesforce.com and developer.salesforce.com. This is read from the text; nothing was executed.
Is Salesforce 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 Salesforce Observability use?
Salesforce 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 Salesforce Observability 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.
What are the alternatives to Salesforce Observability?
Skills that share tags, products or a category with Salesforce Observability: Sf Datacloud Act (Jaganpro/sf-skills, 424 stars), Sf Datacloud Connect (Jaganpro/sf-skills, 424 stars), Sf Datacloud Harmonize (Jaganpro/sf-skills, 424 stars) and Sf Debug (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Salesforce 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.