Skip to content

forcedotcom/sf-skills / skills/platform-agenticsetup-categories-get

platform-agenticsetup-categories-get

Verified

Get agentic setup prompt categories from a connected Salesforce org using the Connect API via sf api request rest. Use this skill to call GET /services/data/vXX.0/agenticsetup/categories and return the list of prompt categories, optionally with their nested prompts using fetchPrompts=true. TRIGGER when: user asks to get, fetch, retrieve, list, or show agentic setup categories, prompt categories, setup copilot categories, prompt library categories, available setup prompts, Agentforce prompt library, copilot prompts, or calls the agenticsetup categories Connect REST API. DO NOT TRIGGER when: user wants to create new categories, work with non-categories endpoints, or generate OpenAPI specs.

platform-agenticsetup-categories-get

Get prompt categories from the Agentic Setup Categories Connect API on a connected Salesforce org.

Scope

In scope:

  • Calling GET /services/data/{apiVersion}/agenticsetup/categories via SF CLI
  • Passing the fetchPrompts query parameter to include nested prompts
  • Parsing and presenting the JSON response (categories, labels, prompts)
  • Handling errors (403 when feature is disabled, auth failures)

Out of scope — delegate elsewhere:

  • Creating or modifying prompt categories → not supported via this API (read-only)
  • Org authentication setup → use sf org login separately
  • Permission set assignment → assigning-permission-set

Required Inputs

The agent needs:

  • A connected org (already authenticated via sf org login)
  • Optionally: whether to include nested prompts (fetchPrompts=true)
  • Optionally: target API version (default: v67.0). Replace v67.0 in the URL with the user-specified version if provided.

Workflow

1. Verify org connectivity

sf org display --json

Confirm the org is authenticated and extract the instance URL. If no default org is set, ask the user which org to target with --target-org.

2. Call the Categories API

Basic call (categories only):

sf api request rest /services/data/v67.0/agenticsetup/categories --method GET

With nested prompts:

sf api request rest "/services/data/v67.0/agenticsetup/categories?fetchPrompts=true" --method GET

3. Parse and present the response

The API returns a JSON object with a categories array. Each category has name, label, and prompts fields. See references/api-response-schema.md for the full response structure and examples for both fetchPrompts=true and fetchPrompts=false.

Present the results clearly:

  • List categories with their name and label
  • If fetchPrompts=true was used, show nested prompts under each category
  • Note any categories with empty prompts arrays (means no prompts exist for that category)

4. Handle errors

ErrorMeaningAction
Success (exit 0)200 OKParse and display results
FUNCTIONALITY_NOT_ENABLEDFeature not enabled for this org/userTell user the Agentic Setup Categories feature needs to be enabled — check Setup > Einstein/Agentforce
INVALID_SESSION_IDSession expiredRe-authenticate with sf org login
NOT_FOUNDEndpoint not foundAPI version too old or feature not deployed to this org

Rules / Constraints

RuleRationale
Always use sf api request rest — never curl or raw HTTPcurl bypasses ~/.sfdx session tokens and requires manual Authorization headers, making it brittle
NEVER use SOQL queriesCategories are NOT in standard objects — only available via this Connect REST API
NEVER generate files (LWC, Apex, XML)This is a data-fetching task, not a code generation task
Default to v67.0 unless user specifiesThis is the min-version where the endpoint was introduced
Don't pass fetchPrompts unless askedReduces payload size; prompts can be large
Categories are sorted by labelThe API returns them alphabetically — don't re-sort
Prompts are sorted by textWithin each category, prompts come alphabetically

Output Expectations

When finishing, present:

  1. Number of categories returned
  2. Category list — name and label for each
  3. Prompts (if requested) — nested under their category
  4. Any errors encountered with suggested fixes

Reference File Index

FileWhen to read
references/api-response-schema.mdWhen you need to understand the full response structure and field descriptions
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall