DiscordSign up
SKILLS.SH

sf-ai-agentforce

>

INSTALLATION
npx skills add https://github.com/jaganpro/sf-skills --skill sf-ai-agentforce
Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$28

Do not use it for:

Required Context to Gather First

Ask for or infer:

  • whether this is a Builder / Setup UI project or a code-first Agent Script project
  • whether the user is editing Builder metadata or a .agent authoring bundle
  • agent type: Service Agent or Employee Agent
  • whether the work targets topics, actions, Prompt Builder templates, Models API, or custom Lightning types
  • what supporting Flow / Apex / metadata dependencies already exist
  • whether the user needs authoring help, publish help, or troubleshooting

Two Agentforce Paths

Path

Skill

Best fit

Builder metadata path

sf-ai-agentforce

Declarative maintenance, existing Builder agents, metadata-driven action registration

Agent Script authoring bundle path

sf-ai-agentscript

Code-first .agent authoring, deterministic routing, version-controlled agent logic

If the user is starting from scratch and wants strong control over flow/state, route to Agent Script.

Builder Workflow Summary

  • Confirm this is a Builder / Setup UI project
  • Pick Service Agent vs Employee Agent
  • For Service Agents, provision the running user (prefer sf org create agent-user)
  • For Employee Agents, plan visibility with a Permission Set containing <agentAccesses>
  • Define topics with strong descriptions, scope, and instructions
  • Prepare supporting actions (Flow, Apex, Prompt Builder template)
  • Configure inputs / outputs carefully
  • Validate dependencies and template status
  • Publish, then activate

Expanded workflow: references/builder-workflow.md

Key Platform Rules

Topic quality matters

Topic descriptions are routing instructions for the planner. They must be:

  • specific
  • scenario-based
  • non-overlapping with sibling topics

Actions are wrappers around real targets

Target type

Typical use

Registered via

Flow

safest default for Builder actions

GenAiFunction

Apex

complex business logic via @InvocableMethod

GenAiFunction

Prompt Builder template

generated summaries / drafts / recommendations

GenAiFunction

Prompt Template vs GenAiPromptTemplate

  • Prompt Template is the plain-English / UI term used in Prompt Builder.
  • **GenAiPromptTemplate** is the current Metadata API type for source-driven template work.
  • Prefer current source format: genAiPromptTemplates/*.genAiPromptTemplate-meta.xml.
  • For flexible Prompt Builder templates, plan around the 5-input maximum and consolidate inputs when needed.
  • Prompt content should reference inputs with the current merge-field shape, e.g. {!$Input:TargetRecord} or {!$Input:AdditionalContext}.

Supporting metadata deploys first

Before publishing the agent itself, deploy the supporting stack:

  • metadata / fields if needed
  • Apex if needed
  • Flows if needed
  • GenAiPromptTemplate / GenAiFunction / GenAiPlugin
  • then publish the agent

Service Agent running user

For Service Agents, prefer the native GA command:

sf org create agent-user --target-org <alias> --json

Use the returned username in the running-user configuration.

Employee Agent visibility

For Employee Agents, ensure end users receive a Permission Set containing <agentAccesses>. Without this, the agent can be active but still invisible in Lightning Experience.

See ../sf-permissions/references/agent-access-guide.md.

Publish does not activate

After publish, run sf agent activate separately.

For automation, prefer sf agent activate --api-name <AgentName> --version <n> --target-org <alias> --json so the rollout is deterministic and machine-readable.

Metadata Guidance

GenAiFunction

Use when registering a single callable action. Validate:

  • target exists
  • target is active / deployable
  • input names match the target contract
  • output names match the target contract
  • capability text clearly says when the action should be used

GenAiPlugin

Use when grouping related functions into one logical package.

GenAiPromptTemplate

Use for generated content, not deterministic business rules.

Prefer the current metadata shape:

  • metadata type: GenAiPromptTemplate
  • folder: genAiPromptTemplates/
  • file suffix: .genAiPromptTemplate-meta.xml
  • content lives under templateVersions
  • use published template versions before wiring actions that depend on them

Models API

Use when the solution belongs in Apex-driven AI orchestration rather than Builder-only actions.

Custom Lightning Types

Use when the action needs richer structured input or output presentation.

Expanded references:

Cross-Skill Integration

Recommended Orchestration Order

sf-metadata → sf-apex → sf-flow → sf-ai-agentforce → sf-deploy

Required delegations

Requirement

Delegate to

Why

Create / fix Flows

sf-flow

Action target creation and Flow validation

Create / fix Apex actions

sf-apex

@InvocableMethod and Apex correctness

Deploy / publish

sf-deploy

Deployment orchestration

Test the agent

sf-ai-agentforce-testing

Formal test execution and assertions

Employee Agent visibility / access

sf-permissions

Permission Set <agentAccesses> setup

High-Signal Failure Patterns

Symptom

Likely cause

Read next

Action not available in Builder

target metadata missing or not deployed

references/metadata-reference.md

Prompt action fails during publish or activation

template is Draft, missing inputs, or old metadata shape is being used

references/genaiprompttemplate.md

Need more than 5 template inputs

flex template input limit hit

references/genaiprompttemplate.md

Apex AI logic times out

Models API work placed in the wrong context

references/models-api.md

Rich input/output UI not rendering

Lightning type config or prerequisites are incomplete

references/custom-lightning-types.md

Agent publishes but is not usable

forgot explicit activation

references/cli-commands.md

Service Agent publish/runtime failure

missing or invalid running user

../sf-ai-agentscript/references/agent-user-setup.md

Employee Agent active but not visible to users

missing <agentAccesses> permission set

../sf-permissions/references/agent-access-guide.md

Reference Map

Start here

Terminology and template planning

Rubric

Cross-skill reads

Score Guide

Score

Meaning

90+

Ready to deploy

80–89

Strong, minor cleanup only

70–79

Review before deploy

60–69

Needs work

< 60

Block deployment

Full rubric: references/scoring-rubric.md

BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Related skills

azure-ai
3/3

Access Azure AI Search, Speech, OpenAI, and Document Intelligence services through unified MCP tools. AI Search supports full-text, vector, hybrid, and semantic search with built-in AI enrichment for entity extraction and OCR Speech service handles real-time and batch speech-to-text transcription, text-to-speech synthesis with neural voices, and speaker diarization MCP tools provide direct access: azure__search for index queries and azure__speech for transcription and synthesis SDK references available for Python, TypeScript, .NET, and Java across all services; enable via /azure:setup or /mcp if MCP is not active

Verified authormicrosoft
SKILLS.SH
325K1.1K
2026-05-22
microsoft-foundry
2/3

End-to-end deployment, evaluation, and management of AI agents on Microsoft Foundry. Covers the complete agent lifecycle: creation from starter samples, containerization and ACR push, hosted or prompt agent deployment, invocation, batch evaluation, and prompt optimization Includes specialized sub-skills for deploy, invoke, observe (evaluation and prompt optimization), trace analysis, troubleshooting, and dataset curation from production traces Supports project and resource provisioning, RBAC management, quota tracking, and model deployment with intelligent routing across regions and SKUs Requires .foundry/agent-metadata.yaml as the source of truth for environment-specific configuration, datasets, and evaluation test cases

Verified authormicrosoft
SKILLS.SH
323K1.1K
2026-05-22
azure-aigateway
2/3

Configure Azure API Management as an AI Gateway for models, MCP tools, and agents with built-in governance policies. Supports semantic caching (60-80% cost savings), token rate limiting, content safety filtering, and jailbreak detection across AI backends Add Azure OpenAI, AI Foundry models, or convert existing APIs to MCP tools as managed backends with load balancing Includes five core policy categories: authentication, semantic cache lookup, token limits, content safety, and token metrics for observability Requires Azure CLI for configuration and testing; integrates with managed identity for secure backend access

Verified authormicrosoft
SKILLS.SH
310K1.1K
2026-05-22
azure-hosted-copilot-sdk
2/3

Build and deploy GitHub Copilot SDK applications to Azure with flexible model configuration. Three scaffolding paths: create new greenfield projects, add SDK services to existing repos, or deploy existing SDK apps with Azure infrastructure Supports three model configurations: GitHub's default models, specific GitHub models via discovery, or bring-your-own-model (BYOM) on Azure with DefaultAzureCredential authentication Includes complete templates with Express/TypeScript API, React/Vite frontend, Bicep infrastructure, Docker support, and token management scripts Deploy workflow uses azure-prepare, azure-validate, and azure-deploy steps; requires Docker and respects existing AGENTS.md configuration in user repos

Verified authormicrosoft
SKILLS.SH
277K1.1K
2026-05-22

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card