Enhance your automations with the power of generative AI by creating reusable AI Skills in AI Agent Studio. AI Skills enable Pro Developers configure prompts, parameters, file inputs, and model connections to produce contextual and consistent AI outputs that can be reused across multiple solutions.

AI Skills are created by selecting a Model connections, configuring prompt logic, and making the skill available to Citizen Developers and Pro Developers for automation building.

Vendors Types
Amazon Bedrock

Standard

Fine tuned

Grounded by knowledge base
Automation Anywhere Grounded by Enterprise knowledge
Azure OpenAI

Standard

Fine tuned

Grounded by AI Search
Google Vertex AI

Standard

Fine tuned

Grounded by data source
OpenAI

Standard

Fine tuned
Note: Some models support multimodal inputs, enabling the AI Skill to process images and documents in addition to text. These capabilities are available only for supported generative AI models, and vary based on the model vendor.

This topic walks you through the steps of creating AI Skills.

Prerequisites

A Pro Developer requires these roles and permissions to create and test an AI Skill.
  • Role: AAE_Basic, Pro Developer Custom role
  • Permission: Bot Creator
  • Setting: Administration > Settings > AI Data Management > Data logging settings must be enabled. The Automation Admin can enable this setting for the Pro Developer

See Roles and permissions

Other requirements:

As part of testing the Model connection, you would have to run the bot on your desktop. Hence ensure the Bot Agent is configured to your user. If you have to switch connection to a different Control Room, see: Switch device registration between Control Room instances.

Procedure

  1. Create a new AI Skill.
    1. Log in to the Control Room.
    2. Navigate to Automation > Create or click the ‘+’ icon and select AI Skill.
    3. Enter a name and description and then click Create & edit. Let us create an example with the name Patient Discharge Agent.
  2. Model connection: Choose a Model connection. At the top of the AI Skill editor, click Choose... under Model connection to open the list of Model connections assigned to you.
    Once selected:

    • The Model connection name, vendor, and Description appear in the header.

    • Parameter fields such as Frequency Penalty, Presence Penalty, N, Max Tokens, Temperature, and Top P become editable.

    These defaults are tailored to the selected model but can be adjusted as needed.

  3. System prompt (Optional): Use this to define high-level context or behavioral guidelines. If the selected Model connection supports the System prompt, you will see a System prompt section. For more information on System prompt, see System prompt. For example:You are a Family Physician creating a comprehensive patient discharge plan.
  4. User prompt: Enter instructions the model. You reference string inputs using $variableName$ syntax. The user prompt supports multi-line text entry and the expanding text area as shown in the screenshot. For example: Create a verbose patient discharge plan... Use the following $patientdetails$ to create the heading…
  5. Prompt Input: (right side)
    String inputs:
    • Click Add String or + to add an input string. Enter a Key and Value.
    • Shows variables created for text-based inputs.
    • Each input includes a name, value, and actions (copy, delete).
    • Example: patientdetails.
    File inputs:
    • Click Add File or + to add a file string. Enter a Key and Value.

    • Choose a file from the Control Room repository or upload a new one. Supported file types include:

      • Images: .jpeg, .jpg, .png, .gif, .webp

      • Documents: .txt, .pdf, .docx, .csv

    AI Skill parameters
    Note: Model-specific restrictions on file size, supported types, and maximum file count are automatically enforced.
  6. File prompt (optional): Displayed only when multimodal input is supported. If you have added files, you will be able to select the files from the drop-down. It controls which file inputs (from the right-side file panel) are included in the final request sent to the model.
    Note: Files attached to an AI Skill are not processed by AI Guardrails for data masking.

    Guardrails evaluate and mask text prompts only.

    File contents are passed directly to the model exactly as provided.

    Note: The maximum number of files and allowable file sizes depend on the selected model connection. Automation 360 enforces the vendor’s limitations automatically.
  7. Get reponse: Use Get reponse to preview the result using the selected Model connection. You can test your AI Skill with the AI Guardrails. Use the Test with AI Guardrail option to simulate the impact of selected guardrails on your prompts and model responses. If a guardrail is chosen, the prompt will be scanned for toxicity and sensitive data. If no guardrails are selected, no guardrail evaluations will be performed on the prompts.
    Note: To use Test with AI Guardrail, the AI Guardrails must be enabled in the global admin settings and you will need View AI Guardrails and View Settings permissions. You can review the audit trail within AI Governance for a detailed record of each test.

    When you are testing with a guardrail you will see the Toxicity for both User prompt and Response. To view the results of data masking, click view data masking execution. It will display the tokenized masked values of any sensitive data identified in the prompt.

    When an AI Skill sends a prompt that violates a blocking rule defined in an active guardrail, the automation using that skill will stop execution with an error message and no response from LLM. The error message will typically indicate that the prompt has been blocked by a guardrail. For more information on setting up Toxicity rule, see Create and manage AI Guardrails.

  8. Data Logging: A toggle appears at the top-right of the screen: Data logging disabled. .

    When enabled: The toggle switches toData logging enabled. The system logs the prompt, response, and the model parameters and file metadata to AI > Governance > AI prompt log

    When disabled: Only minimal metadata is captured.

    Developers can decide how much information is logged based on the sensitivity of the content.

    Note: AI Governance does not store or surface the actual contents of uploaded files. Only file metadata—such as filename, size, and associated parameters—is logged when data logging is enabled. File contents themselves are never logged or displayed in AI Governance.

Example:

Click on the ellipsis next to an AI Skill to view and access actions available to the Pro Developer.

AI Skill actions

Actions Function
Move AI Skill Click on this action to select the location where you want to move the AI Skill to, as per your folder permissions.
Check in the AI Skill Lets you check in an AI Skill to a different folder. The Status of the AI Skill is updated and it displays the folder you checked in the AI Skill. Example: if you checked in the AI Skill to the Public folder, then the Status label displays Public.
View AI Skill Opens the AI Skill displaying details.
Edit AI Skill Lets you edit the AI Skill.
Note: The Pro Developer has this permission.
Copy AI Skill Lets you copy an existing AI Skill to create a new one with the same details. You have to provide a different name though, as there cannot be duplicates of an AI Skills.
Note: The Pro Developer has this permission.
View references Lets you view references to other bots that are directly dependent on the current one where this AI Skill has been used.
Delete AI Skill Lets you delete an AI Skill.
Note: The Pro Developer has this permission.

Next steps

Your next step would be to check-in the AI Skills to make it available to Citizen Developers from the AI Skills package.

Why would you check-in an AI Skill?

After creating an AI Skill, check it into the Public folder. This will let the Pro Developer, and Citizen Developer use it from the AI Skills package in the production environment.

For reference, see:

A Task Bot, with one or multiple embedded AI Skills can be added to a larger automation that would run a complete workflow scenario.

Note: When you create or test an AI Skill in the AI Skills screen, the success or failure details along with the model responses can be viewed in Administration > Audit log and Administration > AI governance navigation. See AI Governance

As the next step in your sequence of tasks, go to Use AI Skills in a Task Bot.