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

odoo-knowledge

Skill2 starsChanged 3 months agoMITView on GitHub

Functional expertise in Odoo's Knowledge application, covering article creation, hierarchical organization, and collaborative sharing.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    Mandate: When creating or updating articles, the agent must ensure the generated HTML is clean and semantically correct (using <h1>, <ul>, …

    line 17
  2. Very specific:

    Public Sharing: Use the is_published field to make an article accessible via a public URL (if the website_knowledge module is installed).

    line 25
  3. Very specific:

    Workflow: Use search_read on knowledge.article to find existing documentation before creating new SOPs to prevent duplication.

    line 28
  4. Very specific:

    Visuals: Use the icon (emoji) and cover_image_id fields to make articles easier for human users to identify.

    line 29

≈ “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 Knowledge Management

This skill provides the agent with functional expertise in Odoo's Knowledge application, covering article creation, hierarchical organization, and collaborative sharing.

Core Mandates

1. Hierarchical Architecture

  • Structure: Articles are recursive. Use parent_id to build a navigation tree (e.g., "Engineering" -> "Procedures" -> "Safety").
  • Root Articles: Articles without a parent_id act as the main categories in the sidebar.

2. Content & Formatting

  • Body: The body field of a knowledge.article stores the content in HTML.
  • Mandate: When creating or updating articles, the agent must ensure the generated HTML is clean and semantically correct (using <h1>, <ul>, <table>, etc.).

3. Sharing & Access Control

  • Categories:
    • workspace: Visible to everyone with access to the Knowledge app.
    • private: Visible only to the owner unless explicitly shared.
    • shared: Articles that have been moved out of Private but aren't yet in the global Workspace.
  • Permissions: Odoo uses internal_permission (write, read, none) for the general staff and article_member_ids (knowledge.article.member) for specific user overrides.
  • Public Sharing: Use the is_published field to make an article accessible via a public URL (if the website_knowledge module is installed).

4. Search & Organization

  • Workflow: Use search_read on knowledge.article to find existing documentation before creating new SOPs to prevent duplication.
  • Visuals: Use the icon (emoji) and cover_image_id fields to make articles easier for human users to identify.

Available Resources

  • knowledge-logic.md: Deep-dive into permission inheritance, embedded views, and public sharing workflows.
  • knowledge-fields.json: Dense technical map of fields for Article and Member models.

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.