You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Files should start with a comment of the file name. Ex: `// functions_personal_agents.js`
8
+
9
+
- Imports should be grouped at the top of the document after the module docstring, unless otherwise indicated by the user or for performance reasons in which case the import should be as close as possible to the usage with a documented note as to why the import is not at the top of the file.
10
+
11
+
- Use 4 spaces per indentation level. No tabs.
12
+
13
+
- Code and definitions should occur after the imports block.
14
+
15
+
- Use camelCase for variable and function names. Ex: `myVariable`, `getUserData()`
16
+
17
+
- Use PascalCase for class names. Ex: `MyClass`
18
+
19
+
- Do not use display:none. Instead add and remove the d-none class when hiding or showing elements.
20
+
21
+
- Prefer inline html notifications or toast messages using Bootstrap alert classes over browser alert() calls.
Copy file name to clipboardExpand all lines: application/community_customizations/actions/azure_billing_retriever/readme.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
# Azure Billing Action Instructions
4
4
5
5
## Overview
6
-
The Azure Billing action is an experimental Semantic Kernel plugin that helps agents explore Azure Cost Management data, generate CSV outputs, and render server-side charts for conversational reporting. It stitches together Azure REST APIs, matplotlib rendering, and Cosmos DB persistence so prototype agents can investigate subscriptions, budgets, alerts, and forecasts without touching the production portal. It leverages message injection (direct cosmos_messages_container access) to store chart images as conversation artifacts in lieu of embedding binary data in chat responses.
6
+
The Azure Billing action is an experimental Semantic Kernel plugin that helps agents explore Azure Cost Management data, generate CSV outputs, and render server-side charts for conversational reporting. It stitches together Azure REST APIs, matplotlib rendering, and Cosmos DB persistence so prototype agents can investigate subscriptions, budgets, alerts, and forecasts without touching the production portal. It leverages message injection (direct cosmos_messages_container access) to store chart images as conversation artifacts in lieu of embedding binary data in chat responses. You will need to move the ```azure_billing_plugin.py``` to the [semantic-kernel-plugins](../../../single_app/semantic_kernel_plugins/) folder, and move the ```schema.json``` and ```definition.json``` to the [schemas](../../../single_app/static/json/schemas) folder.
7
7
8
8
## Core capabilities
9
9
- Enumerate subscriptions and resource groups via `list_subscriptions*` helpers for quick scope discovery.
@@ -48,6 +48,5 @@ The Azure Billing action is an experimental Semantic Kernel plugin that helps ag
48
48
49
49
## Additional resources
50
50
- Review `instructions.md` in the same directory for the autonomous agent persona tailored to this action.
51
-
- Inspect `abd_proto.py` for prompt experimentation tied to Azure Billing dialogues.
52
51
- Leverage the sample CSV files to validate plotting offline before wiring the plugin into a notebook or agent loop.
0 commit comments