Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence.
Install Salesforce Debug Bundle
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-debug-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-debug-bundle --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-debug-bundle .claude/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .claude/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundleType 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-debug-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-debug-bundle --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-debug-bundle .agents/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .agents/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-debug-bundle --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-debug-bundle .cursor/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .cursor/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundle--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-debug-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-debug-bundle --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-debug-bundle .gemini/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .gemini/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundleInstalls 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-debug-bundle -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-debug-bundle .github/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .github/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundle -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-debug-bundle --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-debug-bundle .opencode/skills/salesforce-debug-bundle && 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-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-debug-bundle into .opencode/skills/salesforce-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-debug-bundle", 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-debug-bundle- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 425 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence.
- Works in 7 steps: Create a manifest naming incident, time… → Collect application version, dependency… → Add only relevant limits, object… → …
- Escalating an integration defect
- 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 Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence. Use when escalating an integration defect. Trigger with "build a Salesforce debug bundle".
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; debug logs, event records, and org metadata require explicit support and data-owner authorization
It sits in Sales & Support, covering CRM management and Rate limiting. 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
- Escalating an integration defect
- With build a Salesforce debug bundle
Example prompts
- “build a Salesforce debug bundle”
- “/salesforce-debug-bundle”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; debug logs, event records, and org metadata require explicit support and data-owner authorization
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Create a manifest naming incident, time window, environment class, components, evidence owners, retention, and recipient.
- Collect application version, dependency lock, API version, redacted request ID, status, timing, retry history, and recent deployment IDs.
- Add only relevant limits, object metadata fingerprints, async job summaries, event channel metrics, and log excerpts.
- Replace record IDs, user IDs, org IDs, domains, field values, queries, and payloads with stable redaction tokens where required.
- Scan the bundle for credentials, authorization material, personal data, customer names, and unrelated records.
- Generate hashes and a manifest, then have the incident and data owners review the exact archive.
- Transfer through the approved support channel, record receipt, expiry, and deletion responsibility.
What it can do on your machine
Read from SKILL.md and the folder at commit 80f86df. 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):
developer.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; debug logs, event records, and org metadata require explicit support and data-owner authorization
From compatibility in the SKILL.md frontmatter.
Context cost
Salesforce Debug Bundle loads about 1.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 425 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 80f86df, republished under its MIT licence (© jeremylongshore). 425 words, ~1,066 tokens.
Download SKILL.mdSave it as
.claude/skills/salesforce-debug-bundle/SKILL.md (or your agent's skills folder).- name
- salesforce-debug-bundle
- description
- Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence. Use when escalating an integration defect. Trigger with "build a Salesforce debug bundle".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; debug logs, event records, and org metadata require explicit support and data-owner authorization
- argument-hint
- [incident-id] [output-path]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, salesforce, support, diagnostics, redaction
- model
- inherit
- effort
- high
Privacy-Safe Salesforce Support Evidence Bundle
Overview
Collect the smallest reproducible evidence set while excluding credentials, raw business records, personal data, and unrelated org configuration.
Prerequisites
- Incident identifier, time window, environment, affected operation, and support destination
- Approved evidence classes, redaction policy, retention period, and transfer channel
- Read-only access to the specific limits, metadata, job, event, or log evidence required
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 diagnostic surfaces vary by product, edition, permission, and entitlement. Limits can be read through the versioned REST resource, while debug logs, Event Monitoring, async jobs, and event metrics require separate access and interpretation.
Authentication
Use a dedicated read-only diagnostic principal where possible. Never include access or refresh tokens, session IDs, cookies, authorization headers, client secrets, private keys, usernames, org IDs unless approved, or raw record payloads.
Instructions
- Create a manifest naming incident, time window, environment class, components, evidence owners, retention, and recipient.
- Collect application version, dependency lock, API version, redacted request ID, status, timing, retry history, and recent deployment IDs.
- Add only relevant limits, object metadata fingerprints, async job summaries, event channel metrics, and log excerpts.
- Replace record IDs, user IDs, org IDs, domains, field values, queries, and payloads with stable redaction tokens where required.
- Scan the bundle for credentials, authorization material, personal data, customer names, and unrelated records.
- Generate hashes and a manifest, then have the incident and data owners review the exact archive.
- Transfer through the approved support channel, record receipt, expiry, and deletion responsibility.
Show full SKILL.md (146 more words)Show less
Approval Boundaries
Do not enable broad tracing, extend log retention, retrieve EventLogFile content, export records, or send an archive without support, security, and data-owner approval.
Output
Return the redacted manifest, evidence inventory, collection gaps, hashes, reviewer approvals, transfer receipt, retention deadline, and deletion owner.
Error Handling
| Condition | Response |
|---|---|
| Required evidence is not entitled or permitted | Record the gap and ask Salesforce Support for an approved alternative. |
| Secret or personal data is detected | Block transfer, remove the material, rotate exposed credentials if necessary, and rescan. |
| Bundle cannot reproduce the timeline | Do not add broad data; refine the time window and correlation identifiers. |
Example
A redacted completion receipt might look like this:
incident=SF-204; window=30m; files=7; records=0; secrets=0; pii=tokenized; hash=recorded; expiry=14dResources
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-debug-bundle of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 80f86df
Compare with similar skills
Salesforce Debug Bundle 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 Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib | 154 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Sf DatacloudJaganpro/sf-skills | 424 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Soql Lib Selectorbeyond-the-cloud-dev/soql-lib | 154 | — | ~2k | Automated safety check: Pass | MIT | |
| Dev SetupPortwood-Global-Solutions/Portwood | 126 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Sf FlowJaganpro/sf-skills | 424 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
Sf Flow
Jaganpro/sf-skills
Creates and validates Salesforce Flows with 110-point scoring.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
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 Debug Bundle
What does Salesforce Debug Bundle do?
Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence. Salesforce Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a privacy-safe Salesforce support bundle with request, limits, metadata, job, event, and change evidence.
When should I use Salesforce Debug Bundle?
Salesforce Debug Bundle fits situations like: escalating an integration defect; with build a Salesforce debug bundle.
How do I install Salesforce Debug Bundle in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/salesforce-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/salesforce-debug-bundle in your project. Claude Code loads it when a task matches its description.
How do I install Salesforce Debug Bundle in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/salesforce-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/salesforce-debug-bundle in your project. Codex loads it when a task matches its description.
Can I use Salesforce Debug Bundle 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-debug-bundle -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-debug-bundle, .gemini/skills/salesforce-debug-bundle, .github/skills/salesforce-debug-bundle and .opencode/skills/salesforce-debug-bundle in your project.
What does Salesforce Debug Bundle need to run?
SKILL.md names no scripts, command-line tools or credentials: Salesforce Debug Bundle 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; debug logs, event records, and org metadata require explicit support and data-owner authorization.
Does Salesforce Debug Bundle access the network?
SKILL.md names 1 domain. As links in the text: developer.salesforce.com. This is read from the text; nothing was executed.
Is Salesforce Debug Bundle 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 Debug Bundle use?
Salesforce Debug Bundle 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 Debug Bundle 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 Debug Bundle?
Skills that share tags, products or a category with Salesforce Debug Bundle: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Salesforce Debug Bundle?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 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.