j-256

@j-256 source repo

5 skills
0 followers
8 hours ago last updated

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

0
installs
▌
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.

0
installs
▌
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
▌
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.

0
installs
▌
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.

0
installs

5 published skills