Skip to content

forcedotcom/sf-skills / skills/dx-lifecycle-center

dx-lifecycle-center

Verified

Lifecycle 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.

FileKindSize
SKILL.mdskill md13.1 KB
examples/workflows.mdmarkdown12.0 KB
references/connect-api.mdmarkdown9.6 KB
references/connect-org.mdmarkdown19.8 KB
references/deploy.mdmarkdown12.1 KB
references/error-handling.mdmarkdown2.7 KB
references/hub-org.mdmarkdown6.5 KB
references/list-orgs.mdmarkdown11.8 KB
references/request-body.mdmarkdown3.7 KB
references/troubleshooting.mdmarkdown8.4 KB
scripts/hub-get.shexecutablescript2.8 KB
scripts/poll-deploy-status.shexecutablescript9.3 KB
scripts/resolve-environment.shexecutablescript16.3 KB

references/hub-org.md

View on GitHub
# Lifecycle Center org (Operation C)

The **Lifecycle Center org** is the Lifecycle Center hub that DX Inspector connects to. Its credential is named exactly `ALMDevOpsCenterHub` (case-sensitive). It is a separate connection from the deploy targets.

Three rules always hold:

1. It is **never a deploy target**.
2. It appears in a list **only when it is connected** (`hub.userAuth` is `configured`), as one clearly labelled row, **Lifecycle Center (Production Org)**, with no action button and never counted in Sync all. When it is not connected, the list does not mention it.
3. Its credential is **never used to deploy**.

## Hub names

Make two normalized forms of the request, both lowercase. The **word form** turns hyphens, underscores, and other punctuation into single spaces and splits camel case ("LifecycleCenter" becomes "lifecycle center"). The **compact form** also drops every space. Then "Lifecycle Center org", "lifecycle-center", "lifecycle_center", "LifecycleCenter org", and "lifecyclecenter" all read the same. Work through these in order:

1. **Never a hub name:** "Dev Hub" in any form (including "Dev Hub org"; it is the Salesforce Dev Hub), and plural or general phrases such as "DevOps Center orgs", "DevOps Center environments", or "orgs connected to DevOps Center". These are ordinary requests: route them by rules 2 to 5 in `SKILL.md`.
2. **Certain:** the compact form contains `lifecyclecenter`, `lifecyclecentre`, `almdevopscenterhub`, or `devopscenterhub`, and the name is used as an org: it stands alone or is followed by "org", "hub", "connection", "credential", or "status". This covers "connect to lifecycle center", "is lifecyclecenter org connected", "Lifecycle Center hub", "life cycle center", and `ALMDevOpsCenterHub`. Treat the request as Operation C with no clarifying question, even with extra words around it. If the name is followed by another word that makes it a longer name ("LifecycleCenterService", "lifecycle center controller"), it is a component name, not the org.
3. **Ambiguous:** the word form contains, as whole words, "hub org", "the hub", "doce hub", or "devops center org" (not followed by "s", "list", or letters that make a longer word, so "organizations" is not a match), or a standalone word "hub" that is not part of "dev hub", or any longer word that ends in "hub". Treat the request as Operation C only after the user confirms (see the first row below).

Run this check **before** the other routing rules.

## What to do

| The request | Do |
|---|---|
| Connect, reconnect, repair, log in to, or authorize the Lifecycle Center org | 1. If the name is in the ambiguous group, ask: "Do you mean the Lifecycle Center org (the Lifecycle Center hub)?" On no, ask which org they mean and treat it as a normal org (Operation B). 2. On yes, or for a certain name, check the credential (`connect-org.md`, Step 0, hub mode). 3. **Configured:** reply only "The Lifecycle Center org is already configured." and stop. No reconnect offer, org details, or login link. 4. **Not configured, or half-created:** run `connect-org.md` Steps 1 to 5 in hub mode, using its sign-in layout (Step 2) and connected layout (Step 5). |
| Ask whether the Lifecycle Center org is connected or configured | Check the credential the same way. Configured: reply only "The Lifecycle Center org is already configured." Not configured: reply "The Lifecycle Center org is not configured. Want me to connect it?" |
| Deploy, validate, or quick deploy to the Lifecycle Center org | Make no API call. Ask: "Do you mean the Lifecycle Center org, or a different org?" A different org: ask which and continue at `deploy.md`, Step 2. The Lifecycle Center org: say a deploy cannot go there because it is the Lifecycle Center hub, not a deploy target, and offer to connect that org, or another one, as a regular deploy target (Operation B). Never deploy with the hub credential. |
| List connected orgs or environments | Follow `list-orgs.md`. Add the labelled hub row only when it is connected; otherwise say nothing about it. |
| Show the Lifecycle Center org in the list, or asks why it is not listed | If it is connected it is listed, labelled Lifecycle Center (Production Org). If not, say it is not connected, so it is not shown. Either way it is the Lifecycle Center hub, never a deploy target. If they want its status, check the credential and answer as above. |
| Remove or disconnect it | Say to use **Remove DevOps Center Connection** in DX Inspector. |

## Reading from the Lifecycle Center org

Lifecycle Center tasks (and only those) can read from the hub, for example projects and work items. **Never deploy, validate or quick-deploy with it.**

Use the credential the connection already has. It needs no workspace alias and changes no record:

```bash
bash scripts/hub-get.sh "<dev-org-alias>" "/services/data/v<ver>/query?q=SELECT%20Id,Name%20FROM%20<Object>"
```

- The script is read-only (GET). It calls the hub through `ALMDevOpsCenterHub` as the signed-in user, from the source org, and prints the JSON body. Encode spaces as `%20` and quotes as `%27`. Keep results small (add `LIMIT`): a response that is cut off is reported as a failure.
- Run it only after the credential check says the hub is configured (`hub.userAuth` is `configured`). For `notConfigured`, offer to connect it (Operation C); for `unknown`, try once and report the error.
- A non-2xx answer is reported as is: 401/403 means this user has not signed in to the hub or lacks the **DevOps Center User** permission set; say so and offer to repair the connection.
- **Do not** PATCH or rename the hub row from this skill; DX Inspector owns that record, and a PATCH also rewrites its callout URL and org fields.
- The CLI alias is the row's own name, `hub.cliAlias` (for example `Doce Hub Environment`), always double-quoted: `sf ... --target-org "<hub.cliAlias>"`. Use it only when `hub.workspaceAlias` is `registered`. When it is `missing` or `conflict` (a same-named alias points at another org), use `hub-get.sh`; do not create the alias or invent a different one. Reads only: never deploy, validate or change data with it.

## Notes for the connect flow

- Hub mode has no `DevopsEnvironment` row: it uses `setupNamedCredential` with the fixed name `ALMDevOpsCenterHub`.
- The user must sign in as someone with the **DevOps Center User** permission set in the Lifecycle Center org.
- A failed finish step clears the user's saved DX Inspector selections. Say so before a repair, and again if the finish fails.
- Never rename `ALMDevOpsCenterHub`. DX Inspector finds the credential by that exact name.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall