{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1860,"path":"application-development/ba-configure-custom-skills-rules.md","title":"Configure custom skills and rules","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure custom skills and rules\n\nCreate and manage custom skills and rules, or instructions to control how Build Agent behaves during a session. Rules are preloaded into every session automatically. Skills are available on demand when you or the agent invokes them by name.\n\n## Before you begin\n\nYou must be on Australia Patch 5 or later to work with custom skills and rules.\n\nRole required: admin\n\n## About this task\n\nBoth skills and rules are stored as records in the Build Agent Instruction table. Each record has a type that determines how Build Agent loads the instruction during a session.\n\n- Use skills to provide task-specific guidance that Build Agent can use when needed. For example, internal guidelines for creating a specific type of record or handling a particular workflow pattern.\n- Use rules to enforce consistent behavior every time the agent runs. For example, naming conventions, required fields, or organizational standards.\n\nEach skill or rule instruction has an **Applies To** setting that controls which Build Agent sessions can use it. The coverage levels from broadest to narrowest are as follows:\n\n- **Instance**\n\n Applies to all Build Agent sessions on the instance. Instance-level instructions take the highest precedence.\n\n- **Application**\n\n Applies only when Build Agent is working within a record's application scope. Use application-level instructions to provide guidance specific to one scoped application.\n\n- **User**\n\n Applies only to sessions for the user who created the instruction. User-level instructions are stored separately from instance and application instructions.\n\n\n**Note:** Check your entitlements to determine whether you have access to custom skills and rules in Build Agent.\n\n## Procedure\n\n1. Navigate to **All** > **App Development** > **ServiceNow Studio**.\n\n2. Select the Settings icon \\[Omitted image \"ba-settings-icon.png\"\\] Alt text: in the Build Agent chat panel.\n\n \\[Omitted image \"ba-settings-panel-1.png\"\\] Alt text: Build Agent panel showing greeting message and the Settings button\n\n3. Select the tab for the type of instruction you're creating.\n\n - Select the **Skills** tab to create a custom skill.\n - Select the **Rules** tab to create a custom rule.\n4. Select the **Create skill** or **Create rule** button.\n\n5. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the instruction. Maximum 100 characters.\n\n
\n\nType\n\n\n\nDefines the type of instruction.- Select **Skill** for on-demand guidance\n- Select **Rule** to apply the instruction automatically to every session\n\n\n
\n\nApplies To\n\n\n\nControls which Build Agent sessions use the instruction.- Select **Instance** to apply to all sessions on the instance\n- Select **Application** to apply only when the session is in the record's application scope\n- Select **Me** to apply the instruction only to you\n\n\n
\n\nActive\n\n\n\nAvailability of the instruction for use. Selected by default.\n\n
\n\nDescription\n\n\n\nDescription of what the skill or rule does. Maximum 1,000 characters.\n\n
\n\nInstructions for Build Agent\n\n\n\nInstruction text that Build Agent follows. Plain text only, maximum 65,000 characters. Writing instructions in clear, structured prose helps Build Agent interpret the guidance accurately.\n\n
Some example instructions are:\n\n - Rules:\n - `reuse_before_create`\n\n `Check for existing artifacts before generating new ones. Before creating a table, field, business rule, script include, flow, or UI action, search the instance for something that already covers the requirement. Prefer extending an approved existing artifact over creating a near-duplicate. If a close match exists, tell me about it and wait before proceeding.`\n\n - `naming_convention`\n\n `Use our application prefix. All tables and fields you create use our approved prefix followed by the application short name. Match existing naming in the app you're working in rather than introducing a new pattern.`\n\n - Skill:\n\n `security_review`\n\n `Audit the app for access control and risky patterns. Review the current application and report on tables with missing or overly broad ACLs, client scripts using GlideRecord, scripts running with elevated privileges they don't need, and roles granted more broadly than the workflow requires. For each finding, give the artifact name, the risk in one sentence, and the change you recommend. don't make changes. Report only.`\n\n \\[Omitted image \"ba-new-custom-rule.png\"\\] Alt text: New rule editor form with Name, Type, Applies To, Active, Description, and Instructions for Build Agent fields, alongside the Rules settings panel listing existing custom rules with toggle switches.\n\n6. Select **Save**.\n\n The new skill or rule appears in the settings panel list. The panel updates automatically to reflect the change.\n\n7. Edit an existing instruction by selecting its Open rule record icon.\n\n Make changes to the instruction, then select **Save**.\n\n \\[Omitted image \"ba-instruction-edit.png\"\\] Alt text: Rules panel showing two rule cards with toggles and edit icons\n\n8. Enable or disable an instruction by selecting its toggle.\n\n \\[Omitted image \"ba-instruction-toggle.png\"\\] Alt text: Skills tab showing the toggle enabled for the add\\_comments skill, highlighted with a purple box.\n\n\n## What to do next\n\nActive rules get dynamically loaded per turn in a Build Agent session, so they're available immediately. Active skills are available immediately on demand during a session.\n\n**Parent Topic:**[Build Agent configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/configure-build-agent.md)\n\n"}}