dsc-endpoint-helplisted

Use for Salesforce endpoint facts or diagnosing API/OAuth errors, even with only an error body and no request. Covers scopes, auth, inputs, and outputs. Decline custom-hook questions about CSC/downstream field requirements, even when product_search is named. Not for flows, concepts, or scraping.
j-256/agent-skills · ★ 2 · API & Backend · score 76

Install: claude install-skill j-256/agent-skills

# DSC Endpoint Help Answer one question about one endpoint in a Salesforce API reference on DSC – either by quoting the relevant spec field, or (when a failing request is attached) by diffing the request against the spec and naming the root cause. Every claim is backed by a public `developer.salesforce.com` URL the user can forward to a customer. ## When to use **Lookup branch** (no failing request attached): - A direct spec-field question about a named endpoint: "what scopes does shopper-products getProducts need", "which query params does searchOrders take", "what auth scheme guards createOrder". - A code-generation ask that references a named endpoint: "write me a node script that calls getProduct" – quote the spec the user can write the code against; don't write the code. - A how-to ask that's really a spec-field question in disguise: "how do I paginate search results", "what limit does X accept" – quote the relevant param. **Diff branch** (a failing request is attached): - A cURL command + an error body: "why is this 403ing", "what's wrong with this request". - A request + an `insufficient_scope` / `invalid_client` / `unauthorized_client` envelope, optionally with a JWT to decode for the scope diff. - A content-type / body-shape failure: "diff this against the spec", "is this 415 because content-type is wrong". ## Inputs from the user The user's prompt usually contains some of: - **A reference name** ("shopper-products", "orders", "scapi shopper baskets") – mayb