Platform Trust Archive Manage
forcedotcom/sf-skills
ALWAYS USE THIS SKILL for anything involving Salesforce Archive (also called Trusted Services Archive) — search, view, unarchive, analyze, mask, and erase (RTBF) archived records via the Archive…
Agent skill
Salesforce Incident Runbook
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention.
Install Salesforce Incident Runbook
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-incident-runbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-incident-runbook --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-incident-runbook .claude/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .claude/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbookType 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-incident-runbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-incident-runbook --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-incident-runbook .agents/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .agents/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-incident-runbook --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-incident-runbook .cursor/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .cursor/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbook--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-incident-runbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-incident-runbook --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-incident-runbook .gemini/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .gemini/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbookInstalls 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-incident-runbook -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-incident-runbook .github/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .github/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbook -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-incident-runbook --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-incident-runbook .opencode/skills/salesforce-incident-runbook && 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-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-incident-runbook into .opencode/skills/salesforce-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-incident-runbook", 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-incident-runbook- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 424 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention.
- Works in 7 steps: Declare severity, commander, time… → Freeze deployments and unsafe retries;… → Check Salesforce Status, org identity,… → …
- Handling service
- 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 Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention. Use when handling service or data incidents. Trigger with "respond to Salesforce incident".
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; credential, permission, workload, event, data, and production changes require incident commander and customer approval
It sits in Sales & Support, covering CRM management, Runbooks and postmortems and Incident response. 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
- Handling service
- With respond to Salesforce incident
Example prompts
- “respond to Salesforce incident”
- “/salesforce-incident-runbook”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; credential, permission, workload, event, data, and production changes require incident commander and customer 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.
- Declare severity, commander, time window, affected orgs and workloads, business invariant, data risk, and communication cadence.
- Freeze deployments and unsafe retries; preserve request, job, event, deployment, and reconciliation identifiers.
- Check Salesforce Status, org identity, authorization, API support, limits, metadata, automation, async jobs, event flow, and application…
- Classify platform, org, identity, permission, schema, capacity, code, dependency, data, or consumer failure and bound impact.
- Select the least-destructive approved containment such as pausing intake, deferring work, isolating a consumer, rollback, or credential…
- Recover in a bounded cohort, reconcile records and events by stable keys, and monitor technical and business stop signals.
- Close only after invariants, backlog, security, and data exposure are resolved; assign root-cause and prevention work.
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; credential, permission, workload, event, data, and production changes require incident commander and customer approval
From compatibility in the SKILL.md frontmatter.
Context cost
Salesforce Incident Runbook loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 424 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). 424 words, ~1,084 tokens.
Download SKILL.mdSave it as
.claude/skills/salesforce-incident-runbook/SKILL.md (or your agent's skills folder).- name
- salesforce-incident-runbook
- description
- Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention. Use when handling service or data incidents. Trigger with "respond to Salesforce incident".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; credential, permission, workload, event, data, and production changes require incident commander and customer approval
- argument-hint
- [incident-id] [environment]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, salesforce, incident-response, recovery, reconciliation
- model
- inherit
- effort
- high
Salesforce Integration Incident Response
Overview
Restore business invariants safely by separating Salesforce platform state, customer org state, application behavior, data correctness, and event delivery.
Prerequisites
- Incident commander, severity model, affected environments and workloads, communications, and evidence channel
- Current deployment, org identity, app and principal, API, limits, jobs, events, data, and reconciliation contracts
- Pre-approved containment, failover, deferral, rollback, credential revocation, and vendor escalation procedures
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 reports platform incidents, while org-specific authorization, limits, metadata, automation, jobs, events, and data can fail independently. A green platform status does not prove an integration or business invariant is healthy.
Authentication
Use read-only incident access first and separate break-glass access under the customer process. Never paste tokens, sessions, private keys, raw records, or unrestricted logs into tickets or chat.
Instructions
- Declare severity, commander, time window, affected orgs and workloads, business invariant, data risk, and communication cadence.
- Freeze deployments and unsafe retries; preserve request, job, event, deployment, and reconciliation identifiers.
- Check Salesforce Status, org identity, authorization, API support, limits, metadata, automation, async jobs, event flow, and application telemetry.
- Classify platform, org, identity, permission, schema, capacity, code, dependency, data, or consumer failure and bound impact.
- Select the least-destructive approved containment such as pausing intake, deferring work, isolating a consumer, rollback, or credential revocation.
- Recover in a bounded cohort, reconcile records and events by stable keys, and monitor technical and business stop signals.
- Close only after invariants, backlog, security, and data exposure are resolved; assign root-cause and prevention work.
Show full SKILL.md (140 more words)Show less
Approval Boundaries
Do not rotate credentials, broaden access, disable automation, replay events, retry writes, purge queues, roll back, or fail over without incident and system owners.
Output
Return severity, timeline, evidence, classification, containment, approved actions, recovery IDs, reconciliation, exposure assessment, communications, and prevention owners.
Error Handling
| Condition | Response |
|---|---|
| Salesforce Status is green | Continue org and application diagnosis; do not downgrade from platform status alone. |
| Prior write outcome is unknown | Block replay and reconcile by stable business key and request evidence. |
| Containment can lose business work | Use durable deferral or quarantine and document the recovery obligation. |
Example
A redacted completion receipt might look like this:
incident=SF-311; severity=2; class=event-consumer; intake=paused; recovery=bounded; backlog=0; 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-incident-runbook of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Salesforce Incident Runbook 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 Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Platform Trust Archive Manageforcedotcom/sf-skills | 1.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Service Itsm Incident Mgmt Configureforcedotcom/sf-skills | 1.1k | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Service Itsm Agentic Setup Configureforcedotcom/sf-skills | 1.1k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Service Itsm Agentic Setup Agentforce Coordinateforcedotcom/sf-skills | 1.1k | — | ~5.5k | Automated safety check: Notes | Apache-2.0 | |
| Service Itsm Incident Priority Configureforcedotcom/sf-skills | 1.1k | — | ~5.7k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Service Itsm Incident Mgmt Configure
forcedotcom/sf-skills
Reads and toggles the master Incident Management setting on a Salesforce ITSM org — the org-level switch that turns Incident Management on or off.
Service Itsm Agentic Setup Configure
forcedotcom/sf-skills
Top-level orchestrator for setting up IT Service Management (ITSM) in Salesforce Service Cloud.
Service Itsm Agentic Setup Agentforce Coordinate
forcedotcom/sf-skills
Orchestrator for setting up Agentforce in Salesforce Service Cloud ITSM — Agentforce Studio enablement, the IT Service Fulfiller agent, the IT Service Employee agent, specialized employee agents…
Service Itsm Incident Priority Configure
forcedotcom/sf-skills
Configures the Incident Priority Matrix for Salesforce ITSM through the sf CLI — enabling or disabling the matrix, shaping the Impact x Urgency grid that derives Priority on Incident records…
Sf Datacloud Act
Jaganpro/sf-skills
Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills.
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 Incident Runbook
What does Salesforce Incident Runbook do?
Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention. Salesforce Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention.
When should I use Salesforce Incident Runbook?
Salesforce Incident Runbook fits situations like: handling service; with respond to Salesforce incident.
How do I install Salesforce Incident Runbook in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/salesforce-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/salesforce-incident-runbook in your project. Claude Code loads it when a task matches its description.
How do I install Salesforce Incident Runbook in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/salesforce-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/salesforce-incident-runbook in your project. Codex loads it when a task matches its description.
Can I use Salesforce Incident Runbook 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-incident-runbook -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-incident-runbook, .gemini/skills/salesforce-incident-runbook, .github/skills/salesforce-incident-runbook and .opencode/skills/salesforce-incident-runbook in your project.
What does Salesforce Incident Runbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Salesforce Incident Runbook 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; credential, permission, workload, event, data, and production changes require incident commander and customer approval.
Does Salesforce Incident Runbook 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 Incident Runbook 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 Incident Runbook use?
Salesforce Incident Runbook 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 Incident Runbook 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.
What are the alternatives to Salesforce Incident Runbook?
Skills that share tags, products or a category with Salesforce Incident Runbook: Platform Trust Archive Manage (forcedotcom/sf-skills, 1.1k stars), Service Itsm Incident Mgmt Configure (forcedotcom/sf-skills, 1.1k stars), Service Itsm Agentic Setup Configure (forcedotcom/sf-skills, 1.1k stars) and Service Itsm Agentic Setup Agentforce Coordinate (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Salesforce Incident Runbook?
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.