AI Studio - Playbooks

Use this page to understand how Playbooks are invoked, created, imported, and managed in AI Studio.

Overview

Playbooks are standard operating procedures that the agent can look up and follow.

They define repeatable AI workflows and help administrators control how recurring analysis, reporting, and review tasks are handled.

Use Playbooks when a repeated business question needs a consistent method, data handling approach, output structure, or operating procedure.

User flow

Users do not usually choose a Playbook directly.

A Playbook is applied when the user's request matches a repeatable workflow, such as budget variance analysis, cloud spend review, vendor review, QBR creation, or financial root cause analysis.

When a user asks a question in Ask Yarken, the orchestrator evaluates:

• The user’s intent.

• Whether the task follows a repeatable workflow.

• Whether specialist domain expertise is needed.

• Whether a specific output format is required.

• Whether a system action is needed.

The orchestrator may use one or more AI Studio components.

Example scenarios

How Playbooks work

Where to find Playbooks

To open Playbooks:

1. Go to Admin.

2. Select AI Studio.

3. Under Orchestrate, select Playbooks.

The Playbooks page displays playbook cards in the main panel.

What the Playbooks page shows

Each playbook card shows:

The page also includes:

• Import: Upload playbook definitions.

• + Add Playbook: Create a new playbook manually.

Current playbooks shown

The current Playbooks screen shows examples such as:

• Generating Accurate Cost, Budget & Forecast Reports.

• Conducting Vendor Review for Optimization and Renegotiation.

• Perform Budget vs Forecast Variance Analysis.

• Perform Financial Root Cause Analysis.

• sop_compare_with_AWS_pricebook.

• App Portfolio Rationalization & Value Analysis.

• Cloud Spend Overview Dashboard Generation.

• Reserved Instance & Commitment Risk Check.

• Service Deep-Dive Analysis.

• Publish Monthly IT Cost Reports to Business.

• QBR report creation.

• TBM Office Digital Specialist.

• CLOUD OPTIMISATION.

This list may change as AI Studio evolves.

Admin configuration flow

Create a playbook manually

To create a Playbook manually:

1. Go to Admin > AI Studio > Playbooks.

2. Select + Add Playbook.

3. Enter the Title.

4. Enter the Description.

5. Add the Content.

6. Add conversation starters, if required.

7. Select Save.

Import playbooks

Use Import when you need to upload Playbooks instead of creating them manually.

The upload modal supports drag and drop or file browse.

Supported file types shown in the current interface:

• .xlsx

• .csv

After importing, review the Playbook before relying on it. Confirm the title, description, content, conversation starters, and active status.

Configure playbook identity

The top section defines the Playbook identity.

Write the description as a clear scope statement. It should help the orchestrator understand when the Playbook applies.

Example:

Streamline cost and forecast reporting using system-provided data while respecting calculation constraints.

Configure playbook content

Use Content to define the procedure the agent should follow.

Good Playbook content should define:

1. The objective.

2. Required parameters, such as time period, scope, audience, and report type.

3. Required data inputs.

4. Validation checks.

5. Analysis steps.

6. Calculation rules and constraints.

7. Chart or table instructions, where relevant.

8. Required caveats.

9. Recommended next steps.

10. What the agent must not infer or calculate.

Example from the current cost, budget, and forecast Playbook:

• Define the report objective.

• Validate data inputs.

• Confirm required columns are available.

• Use existing forecast values where available.

• Do not invent or derive forecast values when they are missing.

• Summarize insights using existing values only.

• Document limitations and recommend next steps.

Add conversation starters

Conversation starters are example questions shown to users to illustrate when a Playbook applies.

To add a conversation starter:

1. Open the Playbook.

2. Go to Conversation Starters.

3. Enter an example question.

4. Select Add.

5. Select Save.

Use examples that match the Playbook's real scope.

Deactivate a playbook

To deactivate a Playbook:

1. Open the Playbook.

2. Select Deactivate.

Use deactivation when the Playbook should remain configured but should not be available for orchestration.

Delete a playbook

To delete a Playbook:

1. Open the Playbook.

2. Scroll to Delete playbook.

3. Select Delete.

Deleting a Playbook permanently removes the Playbook and its configuration. Use deactivation when the Playbook may be needed later.

Configuration guidance

Before enabling a Playbook, confirm that:

1. The workflow is repeatable.

2. The trigger use case is clear.

3. The analysis steps are specific.

4. Required Data Sources are available.

5. Required Specialists or Skills are available.

6. Calculations, filters, and constraints are defined.

7. Output sections are specified.

8. The Playbook does not overlap with another active Playbook.

9. The Playbook has been tested with representative prompts.

Governance notes

Playbooks guide analysis. They do not override permissions, create missing data, or change source records.

Use Playbooks to standardize the method. Use Data Sources to control data access. Use Skills to control response format.

For financial and forecasting workflows, avoid instructions that ask the agent to invent missing values, override system data, or derive forecasts when the source data is unavailable.

Next step

AI Studio - Automations

Related articles

• AI Studio Complete Guide

• Specialists

• Data Sources

• Skills