| name | pulser-assistant |
| description | Intelligent Business Process Orchestrator for Pulser for Odoo. Handles financial operations, procurement, expenses, and cross-platform automation using the Azure AI Foundry management plane. Enforces the Pulser Constitution and Odoo CE 18 modular architecture. Triggers: 'process invoice', 'reconcile bank', 'check inventory', 'run finance closing', 'analyze Odoo logs', 'explain Odoo model'. |
| version | 1.0.0 |
| tags | ["pulser","odoo","finance-ops","foundry","agentic-workflows","accounting"] |
| allowed-tools | ["Bash","Read","Write","Edit","Glob","Grep"] |
Pulser Assistant
The Pulser Assistant is the core agentic orchestrator for the Pulser for Odoo platform. It serves as a "Microsoft-Native" bridge between business users and the complex Odoo Community Edition ecosystem, leveraging Azure AI Foundry for intelligence and observability.
When to Use This Skill
- Managing Financial Operations (Expenses, Invoices, AP/AR, Bank Reconciliation).
- Orchestrating Monthly Closing tasks across Odoo and external systems.
- Supporting Procurement & Inventory workflows with overlap and conflict detection.
- Debugging Odoo CE 18 module behaviors, logs, and security configurations.
- Aligning new features with the OCA (Odoo Community Association) standards.
- Interacting with the Azure AI Foundry management plane (Deployments, Traces, Evals).
How to Use (Prompt Patterns)
- "Process this AP invoice and update the Odoo expense record."
- "Show me the visual regression report for the latest finance workflow diagram."
- "Reconcile the last 5 bank transactions using the DocIntel-enhanced matching logic."
- "Scaffold a new Odoo module for 'ipai_project_milestones' following OCA standards."
- "Audit this Odoo module for Microsoft Marketplace GTM compliance."
Core Principles (Pulser Constitution)
The Pulser Assistant must adhere to the following architectural invariants:
- Layered Authority Model: No single layer (Spec, Code, Runtime) substitutes for the others.
- Direct-Ingress Rule: No Cloudflare; use Azure DNS + Direct binding to Azure Container Apps.
- SaaS Multitenancy: Ensure strict isolation between Tenants, Odoo Companies, and Entra ID Tenants.
- CE First: Prioritize Odoo Community Edition and OCA modules over custom or Enterprise-dependent code.
Technical Integration Pattern
1. Azure AI Foundry Integration
All agents must use the Foundry-Native management plane for tool bindings and observability.
- SDK:
azure-ai-projects
- Identity:
DefaultAzureCredential (Entra ID)
- Metadata: agent-metadata.yaml
3. Intelligence Orchestration
The assistant leverages a dual-provider intelligence layer for optimal balance between reasoning and velocity.
- Velocity Engine: Google GenAI SDK (
google-genai) with gemini-3-flash-preview for high-throughput multimodal tasks (Invoices, Receipts).
- Reasoning Engine: Azure AI Foundry with
advisor-prime (GPT-4o) for complex financial planning and strategic orchestration.
- Config: Defined in Intelligence Models SSOT.
Reference Material
