agentleFS
actinon-comactinon-com/brass-monkey/skills/odoo-workspace/SKILL.md

odoo-workspace

Skill2 starsChanged 3 months agoMITView on GitHub

Manage multiple Odoo environments, handle authentication, and switch between instances.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Initial Setup: If no instances are configured, use setup_instance to add the first one.

    line 15
  2. Very specific:

    Discovery: Use list_instances to see which environments are currently configured.

    line 17
  3. Very specific:

    Workflow: Use switch_instance to change the primary environment for a session.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Odoo Workspace Management

This skill provides the agent with the expertise required to manage multiple Odoo environments, handle authentication, and switch between instances.

Core Mandates

1. Multi-Instance Architecture

Brass-Monkey can manage multiple Odoo environments simultaneously. Each environment is identified by a unique instance_alias (e.g., "prod", "staging", "dev").

2. Configuration & Setup

  • Initial Setup: If no instances are configured, use setup_instance to add the first one. You will need the Odoo URL, database name, username, and password/API key.
  • Verification: setup_instance automatically validates credentials by attempting to authenticate.
  • Discovery: Use list_instances to see which environments are currently configured.

3. Session Defaults & Switching

  • Default Instance: By default, tool calls use the first configured instance or the one set via switch_instance.
  • Contextual Execution: You can override the default for any tool call by providing the instance_alias parameter.
  • Workflow: Use switch_instance to change the primary environment for a session. After switching, always call get_environment to confirm the new context (User, DB, Version).

4. Cross-Instance Operations

You can move data between environments by reading from one instance and creating on another:

  1. data = search_read(model: '...', instance_alias: 'prod')
  2. create_record(model: '...', values: data, instance_alias: 'staging')

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.