About EPM Agent Skills

EPM Agent Skills enable you to use natural language to ask questions, explore business data, and prepare supported administrative actions in Oracle Fusion Cloud Enterprise Performance Management and Oracle Fusion Cloud Enterprise Data Management. The skills combine domain instructions, reference material, and executable tools to guide an AI agent through a defined workflow for the selected environment.

The skills follow the Agent Skills open standard, a lightweight format for providing agents with specialized knowledge and repeatable procedures. Each skill packages instructions and descriptive metadata in a folder, with scripts and reference resources as required. The agent identifies the relevant skill, loads its instructions, and accesses additional resources as needed. This structure enables compatible agents to reuse the same skills.

The EPM_AI_SKILLs package includes a root router that directs requests to the appropriate skill as documented in EPM Skill Routing in in Features with AI .

How Requests Are Processed

When you submit a request, EPM Agent Skills process it in the following sequence:

  1. You describe the required outcome and identify the environment, application, cube, model, or other relevant scope.
  2. The router selects the appropriate domain and checks whether the requested capability is available.
  3. The shared Auth skill prepares or reuses a private session for the selected environment and identity.
  4. The domain validates the inputs and requests any missing information.
  5. The agent performs the authorized read operation or presents the exact proposed change or scenario for approval before execution.
  6. The agent reports the results, supporting evidence, and relevant context, including any failures or incomplete results. For asynchronous operations, it distinguishes job submission from successful completion.

Writing Prompts

In your prompt, describe the action, name the environment, and identify the relevant business scope. For data requests, include the metric, time period, scenario, version, entity, and comparison, when known. For changes, identify the target and specify the new value.

You can refer to details from earlier requests in follow-up prompts. When switching between test and production environments, explicitly name the environment to use.

Here are some prompt examples:

  • Use Basic Auth with my selected configuration file for EPM Test.
  • Get the maintenance start time and time zone.
  • List the cubes in the Vision application.
  • Get the dimensions for Plan3.
  • Read form <form name> for my selected scenario, entity, and period; show the source context.