Agent skill · Backend & API

b2c-scapi-custom

Using the b2c CLI for Custom SCAPI endpoint management

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill b2c-scapi-custom-salesforcecommercecl-b2c-developer-toolin-8a909 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/api/b2c-scapi-custom-salesforcecommercecl-b2c-developer-toolin-8a909/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# B2C SCAPI Custom APIs Skill Use the `b2c` CLI plugin to manage SCAPI Custom API endpoints and check their registration status. ## Required: Tenant ID The `--tenant-id` flag is **required** for all commands. The tenant ID identifies your B2C Commerce instance. **Important:** The tenant ID is NOT the same as the organization ID: - **Tenant ID**: `zzxy_prd` (used with commands that require `--tenant-id`) - **Organization ID**: `f_ecom_zzxy_prd` (used in SCAPI URLs, has `f_ecom_` prefix) ### Deriving Tenant ID from Hostname For sandbox instances, you can derive the tenant ID from the hostname by replacing hyphens with underscores: | Hostname | Tenant ID | |----------|-----------| | `zzpq-013.dx.commercecloud.salesforce.com` | `zzpq_013` | | `zzxy-001.dx.commercecloud.salesforce.com` | `zzxy_001` | | `abcd-dev.dx.commercecloud.salesforce.com` | `abcd_dev` | For production instances, use your realm and instance identifier (e.g., `zzxy_prd`). ## Examples ### Get Custom API Endpoint Status ```bash # list all Custom API endpoints for an organization b2c scapi custom status --tenant-id zzxy_prd # list with JSON output b2c scapi custom status --tenant-id zzxy_prd --json ``` ### Filter by St

What's inside
Steps it walks through
  1. Required: Tenant ID
  2. Deriving Tenant ID from Hostname
  3. Examples
  4. Get Custom API Endpoint Status
  5. Filter by Status
  6. Group by Type or Site
  7. Customize Output Columns
  8. Debug Failed Registrations
  9. Configuration
  10. More Commands
  11. Related Skills
Ships with 1 file
  • metadata.json
Commands it runs
list all Custom API endpoints for an organization
b2c scapi custom status --tenant-id zzxy_prd
list with JSON output
b2c scapi custom status --tenant-id zzxy_prd --json
list only active endpoints
b2c scapi custom status --tenant-id zzxy_prd --status active
list only endpoints that failed to register
b2c scapi custom status --tenant-id zzxy_prd --status not_registered
group endpoints by API type (Admin vs Shopper)
b2c scapi custom status --tenant-id zzxy_prd --group-by type
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the b2c-scapi-custom skill do?

Using the b2c CLI for Custom SCAPI endpoint management

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill b2c-scapi-custom-salesforcecommercecl-b2c-developer-toolin-8a909 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.