commerce-b2b-open-code…
Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention \"integrate open code components\",…
Check when Salesforce orgs expire (or already expired) and what to do about it, for one org, the default org, or across all authenticated orgs, using the Salesforce CLI (sf). Use when the user asks about org or trial expiration, \"when does my trial expire\", \"is my trial org
$ npx -y skills add forcedotcom/sf-skills --skill dx-org-trial-expiration-check --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/dx-org-trial-expiration-checkContext preview
The summary Claude sees to decide when to auto-load this skill.
Check when Salesforce orgs expire (or already expired) and what to do about it, for one org, the default org, or across all authenticated orgs, using the Salesforce CLI (sf). Use when the user asks about org or trial expiration, \"when does my trial expire\", \"is my trial org
name: dx-org-trial-expiration-check
description: "Check when Salesforce orgs expire (or already expired) and what to do about it, for one org, the default org, or across all authenticated orgs, using the Salesforce CLI (sf). Use when the user asks about org or trial expiration, \"when does my trial expire\", \"is my trial org still active\", \"how many days are left\", \"which orgs are expiring soon\", wants to filter orgs expiring within N days, needs machine-readable (JSON/CSV) output for cron or alerting, wants to back up an at-risk org before it lapses, or asks how to extend or renew an expiring trial or Developer Edition org. Covers trial editions, Developer Edition orgs (anything with a TrialExpirationDate), and scratch orgs (via sf org list). DO NOT TRIGGER for sandbox refresh timing, for creating, deleting, or switching the active org, or for non-Salesforce trials such as AWS, Netflix, or other vendors — this skill reads expiration and prints guidance, it does not modify orgs."
allowed-tools: Read, Bash(bash), Bash(sf data query), Bash(sf org list), Bash(sf config get), Bash(jq), Bash(date)
metadata:
relatedSkills:
- "dx-org-switch"
version: "2.0"
domains: ["Developer Experience"]
cliTools:
- tool: ["jq"]
semver: ">=1.6.0"
- tool: ["sf"]
semver: ">=2.0.0"Determine when a Salesforce org expires, how many days remain, and whether it has already expired — for one org, the default org, or every authenticated org. Results are **prioritized** (already-expired and soonest-expiring first) with a one-line summary. The skill can also emit machine-readable output for alerting, print **backup** commands for an at-risk org, and explain how to **renew** an expiring trial or Developer Edition org.
Trigger on requests like:
This skill covers **trial editions, Developer Edition orgs** (anything with a `TrialExpirationDate`), and **scratch orgs** (via the `expirationDate` from `sf org list`).
Do **not** trigger this skill for:
expiration and *prints* guidance; it never creates, deletes, refreshes, or changes the active/default org. (To switch the default org, use `dx-org-switch`.)
vendor's trial. This skill is Salesforce-only.
`Organization.TrialExpirationDate` field, read via SOQL (`sf data query`). This field is `null` for paid/production orgs, which therefore report **no trial expiration** — that is expected, not an error.
query is issued for scratch orgs).
1. **CRITICAL:** Run the bundled helper script, which handles date math (days remaining, expired, expiring-soon warnings), prioritized sorting, and structured output, and works on macOS and Linux. Always invoke it by **absolute path** from the skill directory — never `./scripts/`, which resolves against the user's current directory and will either run the wrong script or fail.
**Before executing, verify:**
bash "<skill_dir>/scripts/check_expiration.sh" <alias-or-username> # one org bash "<skill_dir>/scripts/check_expiration.sh" # default org (target-org config) bash "<skill_dir>/scripts/check_expiration.sh" --all # every authenticated org bash "<skill_dir>/scripts/check_expiration.sh" --all --within 30 # only orgs expiring within 30 days
`<skill_dir>` is the absolute path to the directory containing this SKILL.md.
2. Relay the script output to the user. When an org could not be queried, surface the `sf org login web` command the script prints so the user can authenticate. Pick optional flags based on what the user asked for (see below): `--preserve` when they want to save their work, `--renew` when they ask how to extend, `--json`/`--csv` for automation, `--fail-if-expiring` for a cron/CI gate.
| Flag | Purpose | |------|---------| | `--all`, `-a` | Check every authenticated org. | | `--within <days>`, `-w` | Show only orgs expiring within N days (includes already-expired; omits paid/production). `--within=30` also works. | | `--json` | Emit a JSON array of org records (data only). | | `--csv` | Emit CSV rows (data only). | | `--preserve` | Print backup commands for expiring/expired orgs. | | `--renew` | Print trial/DE extension & reactivation guidance. | | `--fail-if-expiring[=N]` | Exit 3 if any org expires within N days (default 7). | | `--no-scratch` | Exclude scratch orgs (trial/DE only). | | `--help`, `-h` | Show usage. |
Flag order is flexible and flags combine (e.g. `--all --within 30 --json`).
Human output is grouped by urgency — **Expired** first, then **Expiring soon** (within 7 days, flagged `Warning`), then **Active**, then **No trial expiration**, then any orgs that could not be queried — and ends with a one-line summary:
Org expiration status for all authenticated orgs: Expired: old-trial trial/DE edition expired 2026-06-20 (EXPIRED 19 day(s) ago) Expi
This repository provides a curated collection of Salesforce agent skills for building applications.
Repo: forcedotcom/sf-skills
Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention \"integrate open code components\",…
Replace OOTB (out-of-the-box) B2B Commerce components with open source equivalents in site metadata content.json files, or look up the equivalent open code…
Use this skill to diagnose and resolve what blocks a DevOps Center promotion of a work item's feature branch: Git merge conflicts and deployment failures.…
Use this skill to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to…
Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix…
Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new…