mcpField
P
platform-agentsetup-categories-fetch

platform-agentsetup-categories-fetch

github.com/forcedotcomAgent workflows1.1k4.9k installsUpdated 1d ago
Repository

About platform-agentsetup-categories-fetch

A skill for retrieving prompt categories from the Agentic Setup Categories Connect API in an authenticated Salesforce org. It can optionally include nested prompts and presents the returned category data; the API is read-only.

Key features

  1. 01Fetch prompt categories
  2. 02Optionally include nested prompts
  3. 03Present category names and labels
  4. 04Handle API and authentication errors

Use cases

  1. 01Inspect prompt categories in a connected org
  2. 02Review prompts nested under categories
  3. 03Check whether categories contain prompts
  4. 04Diagnose feature or session errors

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/forcedotcom/sf-skills --skill platform-agentsetup-categories-fetch

After installing, type/platform-agentsetup-categories-fetchin Claude Code to confirm it loaded.

Bundled filesreferences/api-response-schema.md

Details

From the project README

platform-agentsetup-categories-fetch

Fetch 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

Comments

Markdown supported