Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
Agent skill
Salesforce Upgrade Migration
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls.
Install Salesforce Upgrade Migration
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-upgrade-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-upgrade-migration --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-upgrade-migration .claude/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .claude/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migrationType 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-upgrade-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-upgrade-migration --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-upgrade-migration .agents/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .agents/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-upgrade-migration --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-upgrade-migration .cursor/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .cursor/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migration--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-upgrade-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace salesforce-upgrade-migration --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-upgrade-migration .gemini/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .gemini/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migrationInstalls 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-upgrade-migration -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-upgrade-migration .github/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .github/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migration -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-upgrade-migration --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-upgrade-migration .opencode/skills/salesforce-upgrade-migration && 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-upgrade-migration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/salesforce-upgrade-migration into .opencode/skills/salesforce-upgrade-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salesforce-upgrade-migration", 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-upgrade-migration- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 438 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls.
- Works in 7 steps: Inventory every explicit and… → Re-fetch the API EOL table, release… → Classify each dependency as supported,… → …
- Planning platform upgrades
- 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 Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls. Use when planning platform upgrades. Trigger with "plan a Salesforce upgrade".
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; API version, dependency, metadata, and production changes require code and Salesforce platform owner approval
It sits in Sales & Support, covering CRM management. 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
- Planning platform upgrades
- With plan a Salesforce upgrade
Example prompts
- “plan a Salesforce upgrade”
- “/salesforce-upgrade-migration”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; API version, dependency, metadata, and production changes require code and Salesforce platform owner 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.
- Inventory every explicit and library-default API version, CLI and library version, endpoint, schema snapshot, event client, and metadata…
- Re-fetch the API EOL table, release notes, client-library releases, CLI contract, and org upgrade schedule.
- Classify each dependency as supported, deprecated, retired, preview, beta, or customer-specific and name an owner.
- Build fixtures for response, error, pagination, metadata, event schema, limits, and partial-failure compatibility.
- Upgrade one boundary at a time in a branch and validate static, unit, contract, sandbox, and deployment checks.
- Canary representative reads and approved non-production writes, then migrate consumers in reversible cohorts.
- Reconcile results, remove old versions only after all consumers and rollback windows close, and schedule the next review.
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):
developer.salesforce.comhelp.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; API version, dependency, metadata, and production changes require code and Salesforce platform owner approval
From compatibility in the SKILL.md frontmatter.
Context cost
Salesforce Upgrade Migration loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 438 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). 438 words, ~1,085 tokens.
Download SKILL.mdSave it as
.claude/skills/salesforce-upgrade-migration/SKILL.md (or your agent's skills folder).- name
- salesforce-upgrade-migration
- description
- Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls. Use when planning platform upgrades. Trigger with "plan a Salesforce upgrade".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; API version, dependency, metadata, and production changes require code and Salesforce platform owner approval
- argument-hint
- [repository] [target-release]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, salesforce, upgrade, api-lifecycle, compatibility
- model
- inherit
- effort
- high
Salesforce API and Toolchain Upgrade Control
Overview
Replace fixed-version guesswork with a complete inventory, compatibility matrix, staged validation, explicit ownership, and reversible consumer migration.
Prerequisites
- Repository and org inventory with API versions, libraries, CLI, metadata, events, packages, and consumers
- Current Salesforce API EOL policy, seasonal release notes, dependency releases, and customer support constraints
- Test environments, representative fixtures, compatibility owner, migration window, and rollback point
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 supports REST API versions for a documented lifecycle and retires older versions after notice. As of this review, versions 21.0 through 30.0 are unavailable, while the current support table must be re-fetched before every migration.
Authentication
Use existing approved app and principal contracts for compatibility tests. Do not add a password fallback, copy production tokens into test, or broaden access to compensate for an upgrade defect.
Instructions
- Inventory every explicit and library-default API version, CLI and library version, endpoint, schema snapshot, event client, and metadata consumer.
- Re-fetch the API EOL table, release notes, client-library releases, CLI contract, and org upgrade schedule.
- Classify each dependency as supported, deprecated, retired, preview, beta, or customer-specific and name an owner.
- Build fixtures for response, error, pagination, metadata, event schema, limits, and partial-failure compatibility.
- Upgrade one boundary at a time in a branch and validate static, unit, contract, sandbox, and deployment checks.
- Canary representative reads and approved non-production writes, then migrate consumers in reversible cohorts.
- Reconcile results, remove old versions only after all consumers and rollback windows close, and schedule the next review.
Show full SKILL.md (152 more words)Show less
Approval Boundaries
Do not change API versions, dependencies, org settings, metadata, event consumers, or production traffic without code, platform, security, and business-owner approval.
Output
Return the version inventory, authority evidence, compatibility matrix, changed contracts, test results, cohort plan, rollback point, and retirement date.
Error Handling
| Condition | Response |
|---|---|
| Requested API version is retired | Stop requests and migrate through a supported version after contract testing; do not retry the retired URI. |
| Library default differs from configured version | Pin and test the effective version at the raw request boundary. |
| Seasonal release changes org behavior | Hold rollout, reproduce in the preview or sandbox path, and update the compatibility decision. |
Example
A redacted completion receipt might look like this:
apis=14; retired=2; target=discovered-supported; fixtures=12; sandbox=pass; cohorts=3; rollback=taggedResources
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-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Salesforce Upgrade Migration 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 Upgrade Migration 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 Upgrade Migration
What does Salesforce Upgrade Migration do?
Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls. Salesforce Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate Salesforce API, seasonal release, CLI, client-library, metadata, and integration contracts under compatibility and rollback controls.
When should I use Salesforce Upgrade Migration?
Salesforce Upgrade Migration fits situations like: planning platform upgrades; with plan a Salesforce upgrade.
How do I install Salesforce Upgrade Migration in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/salesforce-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/salesforce-upgrade-migration in your project. Claude Code loads it when a task matches its description.
How do I install Salesforce Upgrade Migration in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill salesforce-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/salesforce-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/salesforce-upgrade-migration in your project. Codex loads it when a task matches its description.
Can I use Salesforce Upgrade Migration 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-upgrade-migration -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-upgrade-migration, .gemini/skills/salesforce-upgrade-migration, .github/skills/salesforce-upgrade-migration and .opencode/skills/salesforce-upgrade-migration in your project.
What does Salesforce Upgrade Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Salesforce Upgrade Migration 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; API version, dependency, metadata, and production changes require code and Salesforce platform owner approval.
Does Salesforce Upgrade Migration access the network?
SKILL.md names 2 domains. As links in the text: developer.salesforce.com and help.salesforce.com. This is read from the text; nothing was executed.
Is Salesforce Upgrade Migration 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 Upgrade Migration use?
Salesforce Upgrade Migration 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 Upgrade Migration 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 Upgrade Migration?
Skills that share tags, products or a category with Salesforce Upgrade Migration: 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 Upgrade Migration?
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.