OOTB Agent Scripts for New Agent Builder

About

This repository packages two Agent Script authoring bundles as reusable OOTB starting points for New Agent Builder work. The scripts are intended as internal templates for SEs to copy, adapt, and deploy in their own orgs, with explicit notes for the RAG setup and config ID handoff.

Bundles

• IT_Employee_Assistant_Baseline_NAB: employee-facing IT assistant baseline for knowledge, service requests, ticket follow-up, policy answers, and escalation guidance.
• IT_Service_Fulfiller_NAB: IT service fulfiller assistant for incident, problem, change request, knowledge, swarming, and record-update workflows.

Notes

• The _NAB suffix denotes New Agent Builder versions of the agents.
• Both scripts use subagent syntax and @subagent transitions.
• Replace org-specific knowledge, Flow, prompt template, Apex, Slack, and managed action dependencies before publishing in a new org.
• The knowledge.rag_feature_config_id field is intentionally blank in both scripts.
• The Answer Questions with Knowledge ragFeatureConfigId field is intentionally blank in source as well.
• After adding a Data Library in Canvas UI, switch to script mode, copy the generated RAG config ID, and paste it into the Answer Questions with Knowledge ragFeatureConfigId field.
• Do the same for the fulfiller script’s Knowledge Support subagent action.
• There are two RAG touchpoints to fill in per org: the overall knowledge block stays blank in source, and the action-level ragFeatureConfigId gets the org-specific value.

RAG Setup

Use this exact flow in each org:

1. Open the agent in Canvas.
2. Go to Data Library.
3. Select your org's ITSM Knowledge library, or the equivalent knowledge library you created for that org.
4. Save the Data Library if needed, then switch to Script mode.
5. Find the Data Library rag_feature_config_id and copy the ID in between "" (should be populated from previous step).
6. Find the Answer Questions with Knowledge action in the script (or search ragFeatureConfigId).
7. Paste the ID from step 6 into the action-level ragFeatureConfigId between the "".
8. Save the agent and test in Preview

For the fulfiller bundle, follow the same steps in the Knowledge Support subagent.

Support

No technical support is provided for this repository. Use it as a reference baseline and adapt it to your own org, policies, and deployment process.

License

This project is licensed under the MIT License. See LICENSE for details.

Useful Commands

sf project deploy start --manifest manifest/package.xml -o <target-org>

Use the Agent Script validate/publish commands that match your installed Salesforce CLI Agent Script version.