Dsc Triage

Diagnose a failing Salesforce API request against its public spec on developer.salesforce.com ("DSC"). Invoke whenever the user pastes a cURL command, raw HTTP request, or error body (`invalid_client`, `insufficient_scope`, `400 missing_parameter`, etc.) from a customer ticket and asks "why is this failing" / "what scope is missing" / "what's wrong with this request." Diffs required vs. provided scopes (decoded from the access token or from a registered client list the user supplies) and required vs. actual request shape (method, params, headers, body schema). Every claim cited to a public developer.salesforce.com URL. Works against any DSC reference `dsc-scrape` can deliver. Hands off honestly for errors the spec can't explain (5xx, 404 path-or-resource-missing, 409 conflicts). Not for scraping a reference wholesale (that's `dsc-scrape`), not for answering one-off "what does this endpoint require" questions (that's `dsc-endpoint-lookup`).

mkdir -p ~/.claude/skills/dsc-triage
curl -L https://claudskills.com/skills/dsc-triage/SKILL.md \
  -o ~/.claude/skills/dsc-triage/SKILL.md

@misc{dsc-triage-2026,
  author    = {j-256},
  title     = {Dsc Triage [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/dsc-triage/}
}