- Home
- Skills
- Agents & Orchestration
- checkbox
checkbox
Forces an Odoo fit-gap ladder before writing code: standard, then configuration, then no-code, then an existing module, then code. Evidence-grounded per version/edition/hosting, decision cards, blast-radius risk tiers.
$19
Works with the AI Agents you already use
checkbox
Example session with this skill installed
Walk the ladder for adding a new field to track customer social media handles on the partner form. Project is Odoo 17 Enterprise on Odoo.sh.
- Read your context and instructions
- Compiled the checkbox
I have analyzed the requirement for social media handles on the partner form against the Odoo 17 Enterprise profile.
Fit-Gap Decision: Social Media Handles
The ladder search indicates this can be handled via standard configuration rather than custom code.
| Rung | Status | Evidence |
|---|---|---|
| 1. Standard | Found | res.partner already has social_twitter, social_facebook, etc., in the base module. |
| 2. Configuration | Pass | Fields are available; need to be added to the view via Studio or XML. |
| 3. No-Code | Pass | Odoo Studio can expose these hidden fields. |
| 4. Existing Module | N/A | Not required as standard covers it. |
| 5. Code | N/A | Avoided. |
Verdict: Rung 1 (Standard) / Rung 3 (No-Code)
I have drafted the decision card: .checkbox/decisions/0004-social-media-handles.md.
---
id: 0004
need: Track customer social media handles on partner records.
profile: 17.0 / enterprise / odoo-sh
verdict: standard
evidence: source (res.partner fields social_twitter, social_facebook, social_linkedin)
tier: green
status: proposed
---
The requirement is covered by existing fields in the base module. No new Python code is required.
Use Odoo Studio or a simple view inheritance to add these fields to the Partner form view.
Next steps
- Run
checkbox approve 0004in your terminal to authorize the view change. - Open Odoo Studio to drag the existing social media fields onto the form.
- If you prefer a module-based view override, I can draft the XML now that the card is proposed.
Connects securely to your tools. The creator never sees your data.
About this skill
Maintaining Odoo environments requires strict adherence to standard features before resorting to custom code. This skill package enforces a fit-gap ladder for Odoo developers, forcing an analysis of standard, configuration, no-code, and existing modules before any custom code is written. It eliminates technical debt by requiring evidence-grounded decision cards for every change.
What it does
- Fit-Gap Enforcement walks a ladder from standard Odoo features to custom code to minimize unnecessary development.
- Evidence-Based Search queries Odoo source, settings, and the OCA module catalog to find existing solutions.
- Decision Tracking generates version-specific Markdown decision cards at
.checkbox/decisions/to document the "why" behind changes. - Risk Classification categorizes changes into green, amber, or red tiers based on blast-radius risk.
- Automated Guarding prevents or warns against editing custom addons without an approved decision card.
How it works
- Initialize the project with
/checkbox:initto detect Odoo version, edition, and hosting environment. - Climb the ladder for any requested feature, searching for existing standard or OCA solutions first.
- Draft a card using
checkbox card next-idandvalidateto record the verdict and evidence. - Review and Classify changes using
checkbox classifyto identify high-risk "red-tier" modifications.
Frameworks & tools
Specifically built for Odoo (Community and Enterprise) across Online, Odoo.sh, and On-premise hosting. Integrates with the OCA (Odoo Community Association) module catalog and local Odoo source code.
Why this beats prompting it yourself
Generic AI prompts often jump straight to writing Python code or XML views, ignoring standard Odoo configuration. This skill forces a systematic search of the Odoo framework and OCA catalog, ensuring you don't build what already exists.
Use cases
- Evaluating if a requested custom field can be replaced by a standard Odoo setting.
- Finding an existing OCA module to solve a business requirement before starting a new addon.
- Documenting the technical justification and risk level for high-impact model overrides.
- Blocking junior developers or agents from modifying core logic without a recorded fit-gap analysis.
Known limitations
The Odoo official documentation index is not currently implemented. Red-tier changes require an external ledger-reviewer report for human approval.
Requires local Odoo source for indexing. The Odoo documentation index is not implemented. Strict mode requires manual CLI commands for approvals and mode changes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
Allowed Hosts