all publishers

j-256

@j-256 source repo

10 published skills

  1. ▌
    Dsc Scrape 2 · j-256 bundle
    Use only for developer.salesforce.com `/docs/apis` catalogs and `/references/` API pages or operations. Scrapes, fetches, mirrors, discovers, lists, or extracts OAS, RAML/AMF, Swagger/OCAPI, and ReDoc references into JSON. Decline `/docs/atlas.*` URLs, guides, books, concepts, and release notes.
    4 installs
  2. ▌
    Dsc Scenario 2 · j-256 bundle
    Use for multi-call developer.salesforce.com API scenarios or repros covering prerequisites, call order, scopes, ID threading, or a flow around an operation, goal, cURL, or failure. Produces a plan and runnable cURL block. Not for one-endpoint lookup/debugging or narrated, paused demo scripts.
    2 installs
  3. ▌
    Dsc Endpoint Help 2 · j-256 bundle
    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.
    4 installs
  4. ▌
    Fork And Pr 2 · j-256 bundle
    Use for a single GitHub fork-and-PR contribution when the user lacks upstream write access, including how-to, existing forks or clones, and push 403. Do not use for owned or write-access repos, SAML authorization, merge conflicts, or stacked or multiple PRs.
    4 installs
  5. ▌
    Stepped Demo Script 2 · j-256 bundle
    Always use for paste-and-run Bash repros or reproductions, demos, case scripts, and CLI walkthroughs with narration, pauses, and visible checks, even if "script" is omitted. Owns authoring across domains. Not for CI/batch code, scenario planning, payloads, libraries, refactors, or debugging.
    4 installs
  6. ▌
    Dsc Scrape · j-256 bundle
    Use only for developer.salesforce.com `/docs/apis` catalogs and `/references/` API pages or operations. Scrapes, fetches, mirrors, discovers, lists, or extracts OAS, RAML/AMF, Swagger/OCAPI, and ReDoc references into JSON. Decline `/docs/atlas.*` URLs, guides, books, concepts, and release notes.
    5 installs
  7. ▌
    Fork And Pr · j-256 bundle
    Use for a single GitHub fork-and-PR contribution when the user lacks upstream write access, including how-to, existing forks or clones, and push 403. Do not use for owned or write-access repos, SAML authorization, merge conflicts, or stacked or multiple PRs.
    4 installs
  8. ▌
    Dsc Scenario · j-256 bundle
    Use for multi-call developer.salesforce.com API scenarios or repros covering prerequisites, call order, scopes, ID threading, or a flow around an operation, goal, cURL, or failure. Produces a plan and runnable cURL block. Not for one-endpoint lookup/debugging or narrated, paused demo scripts.
    0 installs
  9. ▌
    Dsc Endpoint Help · j-256 bundle
    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.
    5 installs
  10. ▌
    Stepped Demo Script · j-256 bundle
    Always use for paste-and-run Bash repros or reproductions, demos, case scripts, and CLI walkthroughs with narration, pauses, and visible checks, even if "script" is omitted. Owns authoring across domains. Not for CI/batch code, scenario planning, payloads, libraries, refactors, or debugging.
    2 installs