forcedotcom/sf-skills / skills/dx-lifecycle-center
dx-lifecycle-center
VerifiedLifecycle Center for DX Inspector and Builder Central. Four jobs: (A) list the orgs connected to DX Inspector; (B) connect a new org (sandbox or scratch, production, OrgFarm) as a deploy target; (C) connect or check the Lifecycle Center org, also written LifecycleCenter, lifecycle-center, ALMDevOpsCenterHub, or Hub org; (D) deploy, validate, or quick-deploy components that already exist in the user's org to a connected org, and poll a simple-deploy requestId. TRIGGER on: show, list, or pick connected orgs or environments; connect, add, log in to, or repair an org; connect the Lifecycle Center org; deploy, validate, push, or publish components (metadata) to another org, URL, org id, alias, or environment name. Short asks like "connect a new org" or "deploy to my sandbox" match. NOT for promoting work items (dx-devops-promote), local source deploys (platform-metadata-deploy), or publishing sites or packages. Deploys move components between orgs, not local files.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| examples/workflows.md | markdown | 12.0 KB |
| references/connect-api.md | markdown | 9.6 KB |
| references/connect-org.md | markdown | 19.8 KB |
| references/deploy.md | markdown | 12.1 KB |
| references/error-handling.md | markdown | 2.7 KB |
| references/hub-org.md | markdown | 6.5 KB |
| references/list-orgs.md | markdown | 11.8 KB |
| references/request-body.md | markdown | 3.7 KB |
| references/troubleshooting.md | markdown | 8.4 KB |
| scripts/hub-get.shexecutable | script | 2.8 KB |
| scripts/poll-deploy-status.shexecutable | script | 9.3 KB |
| scripts/resolve-environment.shexecutable | script | 16.3 KB |
scripts/hub-get.sh
View on GitHub#!/usr/bin/env bash
# Read-only GET against the Lifecycle Center org through the DX Inspector credential (ALMDevOpsCenterHub).
# No workspace alias and no record change: the call runs as the signed-in user, from the source org.
#
# Usage: hub-get.sh <source-org-alias> </services/data/vNN.N/...path?query>
# Prints the response body (JSON) on stdout. Exit codes: 0 HTTP 2xx, 1 usage / not 2xx / call failed.
set -uo pipefail
command -v jq >/dev/null || { echo "jq required" >&2; exit 1; }
SRC="${1:-}"; REQ="${2:-}"
[ -n "$SRC" ] && [ -n "$REQ" ] || { echo "usage: hub-get.sh <source-org-alias> </services/data/vNN.N/...>" >&2; exit 1; }
case "$REQ" in */../*|*/..|*%2e%2e*|*%2E%2E*) echo "path must not contain .." >&2; exit 1 ;; esac
printf '%s' "$REQ" | grep -Eq '^/services/data/v[0-9]+\.[0-9]+/' || { echo "path must start with /services/data/v<version>/" >&2; exit 1; }
# The path goes into an Apex string literal: allow only URL-safe characters (no quotes, backslashes, or whitespace).
printf '%s' "$REQ" | grep -Eq "^[A-Za-z0-9/._~%+=&?,:*()-]+$" || { echo "path has characters that are not allowed (encode spaces as %20 and quotes as %27)" >&2; exit 1; }
apex=$(mktemp "${TMPDIR:-/tmp}/hub-get.XXXXXX") || exit 1
trap 'rm -f "$apex"' EXIT
cat > "$apex" <<APEX
HttpRequest r = new HttpRequest();
r.setEndpoint('callout:ALMDevOpsCenterHub${REQ}');
r.setMethod('GET');
r.setHeader('Accept', 'application/json');
HttpResponse s = new Http().send(r);
System.debug('HUBGET ' + s.getStatusCode() + ' ' + EncodingUtil.base64Encode(Blob.valueOf(s.getBody())));
APEX
# One retry after a short pause covers a refreshing session or a transient hub error.
for attempt in 1 2; do
out=$(env FORCE_COLOR=0 SF_CLI_DISABLE_AUTOUPDATE=true sf apex run --file "$apex" --target-org "$SRC" --json 2>/dev/null) && \
line=$(printf '%s' "$out" | jq -r '.result.logs // ""' | grep -o 'HUBGET [0-9]* [A-Za-z0-9+/=]*' | head -1) || line=""
case "$line" in "HUBGET 5"*|"HUBGET 408"*|"") [ "$attempt" = 1 ] && { sleep 3; continue; } ;; esac
break
done
[ -n "$line" ] || { echo "no response captured; the callout failed (session expired, Apex not permitted, or the credential is not usable for this user): $(printf '%s' "$out" | jq -r '.result.exceptionMessage // .message // "unknown"' 2>/dev/null | head -c 200)" >&2; exit 1; }
code=$(printf '%s' "$line" | cut -d' ' -f2)
b64=$(printf '%s' "$line" | cut -d' ' -f3)
body=$(printf '%s' "$b64" | base64 -d 2>/dev/null || printf '%s' "$b64" | base64 -D 2>/dev/null)
# A truncated debug log decodes to partial JSON: never return it as a success.
printf '%s' "$body" | jq -e . >/dev/null 2>&1 || { echo "response was cut off or is not JSON; narrow the query (add LIMIT)" >&2; exit 1; }
printf '%s\n' "$body"
case "$code" in 2??) exit 0 ;; *) echo "hub returned HTTP $code" >&2; exit 1 ;; esac
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |