skills.rest
le-goff-benoit
le-goff-benoitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

odoo_inspect_studio

Audit Odoo Studio customizations and identify migration risks.

2|Updated May 11, 2026
Search Tags:#odoo#audit#migration#customization#studio
One-click install
npx skills add https://github.com/le-goff-benoit/better_odoo_consultant --skill odoo-inspect-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: odoo_inspect_studio
Source: https://github.com/le-goff-benoit/better_odoo_consultant/tree/main/skills/odoo-inspect-studio
Command: npx skills add https://github.com/le-goff-benoit/better_odoo_consultant --skill odoo-inspect-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive audit of Odoo Studio customizations, helping to identify potential migration risks and assess the complexity of Studio customizations in a project.

Core Features & Use Cases

  • Audit Studio Customizations: Inspect x_* models, x_studio_* fields, studio views, menus, base.automation rules, server actions, and automations.
  • Assess Studio Complexity: Evaluate the complexity of Studio customizations for a project or migration preparation.
  • Identify Migration Risks: Highlight potential risks and issues that may arise during migration to a new version of Odoo.

Quick Start

Use the odoo_inspect_studio skill to audit all Studio customizations on this instance.

Frequently Asked Questions about odoo_inspect_studio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Odoo Studio customizations before a migration?▼

Auditing Odoo Studio customizations involves inspecting x_* models, x_studio_* fields, studio views, menus, and base.automation rules to assess complexity and identify potential migration risks.

What are common migration risks with Odoo Studio customizations?▼

Migration risks in Odoo Studio customizations typically stem from complex x_studio_* fields, server actions, and base.automation rules that may conflict with new base versions or break existing business logic.

How do I evaluate the complexity of Odoo Studio custom fields and automations?▼

Evaluating Studio customization complexity requires scanning x_* models, studio views, and server actions to map dependencies and gauge the effort needed for migration or project maintenance.

Do I need an active Odoo connection to inspect Studio customizations?▼

Yes, inspecting Studio customizations requires an active Odoo connection because the audit process reads both the filesystem and live Odoo data to accurately map x_studio_* fields and automations.

What specific Odoo Studio components should I check when preparing for an upgrade?▼

When preparing for an upgrade, check Odoo Studio components including x_* models, studio views, menus, base.automation rules, and server actions to uncover hidden dependencies and migration conflicts.

Related Skills

Explore More Software Engineering Skills→
le-goff-benoitle-goff-benoit
2

inspect_automations

Audit server-side automations in Odoo instances by module, model, and XML-ID.

Community
Intermediate
sumeetonline90sumeetonline90

security-scan

Scan Claude Code configuration directories for security vulnerabilities and misconfigurations.

Community
Intermediate
edulazaroedulazaro
12

lc:slow-queries

Analyze Laravel Eloquent and Query Builder usage to detect database performance bottlenecks.

Community
Intermediate
Nikolay-ShirokovNikolay-Shirokov
511

form-info

Parse Form.xml files to summarize 1C managed form elements, attributes, events, and commands.

Community
Basic