Skip to content
Back to search

unclecat-agent-skills

SkillGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/unclecatvn--agent-skills/badge.svg)](/listings/unclecatvn--agent-skills)

HTML

<a href="/listings/unclecatvn--agent-skills"><img src="/api/listings/unclecatvn--agent-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pick **one** installation route.

Claude Code plugin (recommended for Claude Code): skills and agents together

claude plugin marketplace add unclecatvn/agent-skills
claude plugin install agent-skills@unclecat-agent-skills

Add `--scope project` to record the installation in the current project instead of your user settings. Everything appears namespaced by the plugin: skills such as `agent-skills:odoo-workflow` and `agent-skills:odoo-18-0`, agents such as `agent-skills:odoo-code-tracer` and `agent-skills:odoo-code-review`.

To update later, refresh the marketplace, then install the plugin again:

claude plugin marketplace update unclecat-agent-skills
claude plugin install agent-skills@unclecat-agent-skills

See the [marketplace manifest](.claude-plugin/marketplace.json) and the [plugin reference](https://code.claude.com/docs/en/plugins-reference).

Skills installer: any supported assistant

npx skills add unclecatvn/agent-skills

Choose the skills and your assistant in the installer. Install `odoo-workflow` plus the pack for your Odoo version (`odoo-18`, ...). This route installs skills only, not the standalone agents or rules. Targets and options are maintained by the [upstream skills CLI](https://github.com/vercel-labs/skills#readme).

Bundled CLI: copy one pack to a known location

# List installable packs
npx @unclecat/agent-skills-cli versions skills

# Odoo 18 pack for Cursor
npx @unclecat/agent-skills-cli init --ai cursor --skill skills --version odoo-18.0

# Workflow pack for Claude Code
npx @unclecat/agent-skills-cli init --ai claude --skill skills --version odoo-workflow

`--skill skills` names the repository directory and `--version` selects a pack inside it. Pass both: the CLI's legacy defaults do not match this layout. See [installation notes](#installation-notes).

**Requirements:** Node.js 18+ for the CLI routes; Python 3.8+ for the workflow's helper (standard library only; the Python in your Odoo virtualenv works); a local checkout of the Odoo source your project runs (community, plus enterprise if you use it).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 27 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://json.schemastore.org/claude-marketplace.json",
  3. "name": "unclecat-agent-skills",
  4. "owner": {
  5. "name": "UncleCat",
  6. "url": "https://github.com/unclecatvn"
  7. },
  8. "metadata": {
  9. "description": "Skills and agents for Odoo 16-19 development",
  10. "version": "1.0.20"
  11. },
  12. "plugins": [
  13. {
  14. "name": "agent-skills",
  15. "source": "./",
  16. "description": "Odoo 16-19 skill packs, the odoo-workflow pre-code gate, Odoo commit style, and the Odoo review/tracer agents",
  17. "version": "1.0.20",
  18. "category": "development",
  19. "keywords": [
  20. "odoo",
  21. "python",
  22. "code-review",
  23. "development"
  24. ]
  25. }
  26. ]
  27. }
README.md · README · 429 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. https://github.com/user-attachments/assets/a6f73c3a-7253-4621-b72e-511e2e57cb3a
  3. # Agent Skills
  4. **Version-aware expertise for Odoo development.**
  5. Reference packs, a trace-first development workflow, and specialized reviewers that make AI coding
  6. assistants work from your real Odoo source instead of from memory. Odoo 16–19.
  7. [![npm version](https://img.shields.io/npm/v/@unclecat/agent-skills-cli?style=flat-square&color=714B67)](https://www.npmjs.com/package/@unclecat/agent-skills-cli)
  8. [![MIT license](https://img.shields.io/badge/license-MIT-714B67?style=flat-square)](LICENSE)
  9. [![CI](https://github.com/unclecatvn/agent-skills/actions/workflows/ci.yml/badge.svg)](https://github.com/unclecatvn/agent-skills/actions/workflows/ci.yml)
  10. **English** · [Tiếng Việt](README.vi.md)
  11. [Why](#why-it-exists) · [With vs without](#with-and-without-the-skill-one-real-task) · [Quick start](#quick-start) · [First run](#first-run-in-an-odoo-project) · [How it works](#how-the-odoo-workflow-works) · [Prompts](#everyday-prompts) · [Toolkit](#whats-in-the-toolkit) · [Versions](#odoo-versions-and-runtime) · [Contributing](#contributing)
  12. </div>
  13. ## Why it exists
  14. AI assistants write plausible Odoo code. The failures that cost time are always the same kind:
  15. - a field, method or xmlid that does not exist in the base addon (`sale.order.delivery_date`,
  16. `sales_team.group_sale_admin`);
  17. - an xpath anchor that only another module's view adds, so the module fails to install;
  18. - an override hooked on the public method instead of the hook that does the work;
  19. - a stored field renamed without a migration, which silently drops the column and its data;
  20. - a `sudo()` nobody can audit;
  21. - "tests pass" when the test run ran zero tests.
  22. This repository gives the assistant three things against that:
  23. | Part | What it does |
  24. | --- | --- |
  25. | **Odoo reference packs** (16.0, 17.0, 18.0, 19.0) | Version-specific guides for models, fields, views, OWL, security, controllers, reports, tests, migrations, translations and performance, plus an `api-highlights.md` list of what not to use in that version. |
  26. | **Odoo Workflow skill** | A procedure the assistant follows for every Odoo change: find the runtime, trace the real source with a bundled helper, write a Context Brief where every claim has a `file:line`, implement the smallest change, then prove it on a throwaway database. |
  27. | **Agents** | A code tracer and a scored code reviewer that share the same version and runtime rules. |
  28. These are instructions and a read-only helper script, not an Odoo module or an enforcement system.
  29. Results depend on the assistant, the model, and the checks you let it run.
  30. ## With and without the skill: one real task
  31. A user in an Odoo 18 project asks the following. As in most real setups, the Odoo source and
  32. `odoo.conf` live outside the project directory, and nothing in the prompt says where:
  33. > In module x_eval, add a stored computed integer field `x_age_days` on `sale.order.line`: days since
  34. > the line's `create_date`.
  35. We ran this task with the same model (Claude Opus 5.5), once with no skill and once with the
  36. `odoo-workflow` skill, and had a separate grader check both answers against the Odoo 18 source
  37. without knowing which was which. Both noticed that a stored compute on `create_date` never
  38. refreshes and added a daily cron. The difference is in what each one knew and what it would have
  39. shipped:
  40. | | Without the skill | With `odoo-workflow` |
  41. | --- | --- | --- |
  42. | Odoo version | Guessed: *"I assumed Odoo 18 (or 19)"* | Found 18.0 in the core's `odoo/release.py`, through the `odoo.conf` in a sibling directory |
  43. | Source read | 3 tool calls, no `file:line` anywhere | 26 tool calls, a Context Brief of 13 cited rows |
  44. | Why `create_date` exists on the line | Not explained | Cited: automatic log field from `odoo/models.py:288` |
  45. | Upgrading a database that already has order lines | Noted that `-u` recomputes every line in Python | Bumps the version to 1.1 and adds `migrations/1.1/pre-migrate.py` that fills the column in SQL, so `-u` does not recompute millions of rows |
  46. | Tests | `-u x_eval --test-tags /x_eval` on an unnamed database, which runs **0 tests and still exits 0** if x_eval is not installed there | Installs on a throwaway `scratch_x_eval` database and requires the log line `0 failed, 0 error(s) of N tests` with N > 0 |
  47. | Grader verdict | 2 of 3 expectations | 3 of 3, preferred |
  48. An excerpt of the Context Brief the skill produced:
  49. | Layer | Symbol | Source (file:line) | Change |
  50. | --- | --- | --- | --- |
  51. | field | `create_date` | `odoo/models.py:288` (automatic field), set once at `models.py:5137` | `@api.depends('create_date')` |
  52. | field | `x_age_days` | NOT FOUND on all three roots (helper exit 1): the name is free | new field |
  53. | method | daily recompute | `addons/membership/models/partner.py:87-91`, `membership/data/membership_data.xml:4-10` | same core pattern |
  54. | migration | new stored compute on a populated table | `odoo/models.py:3474-3487` (new column → recompute every row), `odoo/fields.py:1117` (existing column skips it) | version 1.1 + pre-migration |
  55. ### The numbers
  56. The same comparison over the repository's anti-hallucination evals (details and every per-eval row in
  57. [benchmark.md](tests/evals/odoo-workflow/benchmark.md)):
  58. | | Without skill | With `odoo-workflow` |
  59. | --- | --- | --- |
  60. | Realistic setup, 8 evals: expectations passed | 21/23 | **23/23** |
  61. | Realistic setup: evals fully passed | 6/8 | **8/8** |
  62. | Environment given, 24 evals: expectations passed | 70/71 | **71/71** |
  63. | Invented Odoo behaviour (32 runs) | 4 | **2** |
  64. | Code or commands that would ship broken | 0 | 0 |
  65. | Grader prefers (32 pairs) | 6 | **16** (10 ties) |
  66. | Cost: output tokens / tool calls | 1× | ~2× / ~1.7× |
  67. What this says honestly:
  68. - A strong model that can read the source is already careful: neither side shipped broken code on
  69. these evals. The skill's gain is **grounding and completeness**: cited sources, the migration a
  70. stored field needs, and tests that provably ran.
  71. - It costs about **twice the tokens**. For a label change that is wasted, which is why the skill has
  72. a fast path for trivial edits.
  73. - The bundled trace helper answered **34/34** trace questions correctly on real Odoo 18 and 19
  74. source, where the grep recipe of the previous release answered 12/34 under zsh (every lookup came
  75. back empty) and 20/34 under bash. See [benchmark.md](tests/evals/odoo-workflow/benchmark.md).
  76. ## Quick start
  77. Pick **one** installation route.
  78. ### Claude Code plugin (recommended for Claude Code): skills and agents together
  79. ```bash
  80. claude plugin marketplace add unclecatvn/agent-skills
  81. claude plugin install agent-skills@unclecat-agent-skills
  82. ```
  83. Add `--scope project` to record the installation in the current project instead of your user
  84. settings. Everything appears namespaced by the plugin: skills such as `agent-skills:odoo-workflow`
  85. and `agent-skills:odoo-18-0`, agents such as `agent-skills:odoo-code-tracer` and
  86. `agent-skills:odoo-code-review`.
  87. To update later, refresh the marketplace, then install the plugin again:
  88. ```bash
  89. claude plugin marketplace update unclecat-agent-skills
  90. claude plugin install agent-skills@unclecat-agent-skills
  91. ```
  92. See the [marketplace manifest](.claude-plugin/marketplace.json) and the
  93. [plugin reference](https://code.claude.com/docs/en/plugins-reference).
  94. ### Skills installer: any supported assistant
  95. ```bash
  96. npx skills add unclecatvn/agent-skills
  97. ```
  98. Choose the skills and your assistant in the installer. Install `odoo-workflow` plus the pack for your
  99. Odoo version (`odoo-18`, ...). This route installs skills only, not the standalone agents or rules.
  100. Targets and options are maintained by the [upstream skills CLI](https://github.com/vercel-labs/skills#readme).
  101. ### Bundled CLI: copy one pack to a known location
  102. ```bash
  103. # List installable packs
  104. npx @unclecat/agent-skills-cli versions skills
  105. # Odoo 18 pack for Cursor
  106. npx @unclecat/agent-skills-cli init --ai cursor --skill skills --version odoo-18.0
  107. # Workflow pack for Claude Code
  108. npx @unclecat/agent-skills-cli init --ai claude --skill skills --version odoo-workflow
  109. ```
  110. `--skill skills` names the repository directory and `--version` selects a pack inside it. Pass both:
  111. the CLI's legacy defaults do not match this layout. See [installation notes](#installation-notes).
  112. **Requirements:** Node.js 18+ for the CLI routes; Python 3.8+ for the workflow's helper (standard
  113. library only; the Python in your Odoo virtualenv works); a local checkout of the Odoo source your
  114. project runs (community, plus enterprise if you use it).
  115. ## First run in an Odoo project
  116. 1. **Open the assistant in your project** (the directory with your custom addons, or its parent).
  117. 2. **Let the workflow find the runtime.** On the first Odoo task it runs
  118. `python3 <skill_dir>/scripts/odoo_trace.py env`, which reads, in order:
  119. `.claude/odoo.json`, an `odoo-bin` configuration in `.claude/launch.json`, then the one `*.conf`
  120. whose `addons_path` covers your project (searched in parent directories, so `../18.0/odoo.conf`
  121. is found). It prints the Odoo version, core path, conf, Python, dev database and the addons roots
  122. in the order Odoo loads them:
  123. ```text
  124. version 18.0 [/path/odoo/18.0/odoo/release.py]
  125. odoo_root /path/odoo/18.0 [/path/project/.claude/launch.json config "odoo-dev"]
  126. conf /path/odoo/18.0/odoo.conf [same]
  127. python /path/odoo/18.0/.venv/bin/python3 [same]
  128. dev_db v18_dev [same]
  129. addons conf addons_path
  130. r1 /path/odoo/18.0/odoo/addons [odoo/addons (always first)]
  131. r2 /path/odoo/18.0/addons [addons_path]
  132. r3 /path/project/erp [addons_path]
  133. VERDICT: Odoo 18.0, 3 roots, 652 modules, base at /path/odoo/18.0/odoo/addons/base
  134. ```
  135. 3. **If it cannot find the runtime**, it asks once and offers to write a gitignored
  136. `.claude/odoo.json` (paths are machine-local, so do not commit it):
  137. ```json
  138. {"odoo_version": "18.0", "odoo_root": "/path/odoo/18.0", "conf": "/path/odoo/18.0/odoo.conf",
  139. "python": "/path/odoo/18.0/.venv/bin/python3", "dev_db": "v18_dev"}
  140. ```
  141. 4. **Optionally add project rules.** Merge the relevant parts of the
  142. [project template](skills/odoo-workflow/templates/CLAUDE.md) into your `CLAUDE.md` or `AGENTS.md`
  143. (do not overwrite it): Odoo version, addons layout, "throwaway databases only", migrations for
  144. stored-field changes, `_sudo` naming, commit style. The template forbids `Co-Authored-By` and
  145. `Generated with` lines; to stop Claude Code from adding them, set
  146. `"attribution": {"commit": "", "pr": ""}` in the project or user `settings.json`.
  147. You can run the helper yourself from a clone of this repository to see what the assistant sees:
  148. ```bash
  149. cd /path/to/your/project
  150. python3 /path/to/agent-skills/skills/odoo-workflow/scripts/odoo_trace.py env
  151. python3 /path/to/agent-skills/skills/odoo-workflow/scripts/odoo_trace.py field sale.order access_url
  152. ```
  153. ## How the Odoo workflow works
  154. ```mermaid
  155. flowchart LR
  156. R[Request or traceback] --> S0[0 Runtime, version, pack]
  157. S0 --> S1[1 Trace the real source]
  158. S1 --> S2[2 Context Brief with file:line]
  159. S2 --> S3[3 Minimal plan]
  160. S3 --> S4[4 Implement]
  161. S4 --> S5[5 Definition of done]
  162. S5 --> S6[6 Review agent]
  163. ```
  164. | Step | What happens |
  165. | --- | --- |
  166. | **0. Runtime, version, pack** | The helper resolves core, conf and roots; the version comes from the core's `release.py` (a `.claude/odoo.json` or legacy `.odoo-version` pin must agree, or it stops and asks). The assistant loads the matching pack and its `api-highlights.md`. |
  167. | **1. Trace** | Python symbols through the helper (below); views, OWL templates, JS patches, routes, ACLs and rename impact through zsh- and bash-safe greps over the same roots. |
  168. | **2. Context Brief** | One row per symbol the change touches, each with exactly one of `file:line`, `NOT FOUND`, `UNCERTAIN: <what is missing>` or `AMBIGUOUS: <modules>`. No `file:line`, no code. Rules cover redefined fields, related paths, `depends`, override order, generated xmlids, magic fields, xpath anchors, multi-company, schema changes and `sudo()`. |
  169. | **3. Plan** | At most ten bullets; one commit and PR per git repository touched. |
  170. | **4. Implement** | The narrowest hook, `super()` plus the smallest delta, `_inherit = 'model'`, new files listed in the manifest, `_sudo` naming, translatable strings. |
  171. | **5. Definition of done** | [Commands checked on Odoo 18 and 19](skills/odoo-workflow/references/definition-of-done.md): install and test on `scratch_<module>`, the test summary must count more than 0 tests, upgrade on a database copy when there is a migration, no unloaded files, ACL and company rules, `.pot`/`.po` refresh that keeps file names, the project's linter, hygiene checks per repository, then drop the scratch database. |
  172. | **6. Hand off** | The `odoo-code-review` agent, or its checklist if the agent is not installed. |
  173. Two shortcuts keep it proportionate:
  174. - **Brief only:** "where is X defined?", "does `sale.order` have F?" run Steps 0–2 and answer with
  175. the Brief.
  176. - **Fast path:** a label, help text or typo in your own module, a manifest bump, or a test-only
  177. change gets a one-row Brief and skips tracing; the definition of done still applies.
  178. ### The trace helper
  179. `skills/odoo-workflow/scripts/odoo_trace.py` parses the source with Python's `ast`, applies the
  180. version's model-naming rules, follows `_inherit` mixins, `_inherits` delegation, `base` extensions and
  181. the core `BaseModel`, skips files the module never imports, and prints absolute `file:line`. It only
  182. reads files.
  183. | Question | Command |
  184. | --- | --- |
  185. | Where does the runtime come from? | `odoo_trace env` / `odoo_trace roots` |
  186. | Which classes define or extend a model, its mixins, `_auto`, `_log_access`? | `odoo_trace model sale.order` |
  187. | Does a field exist (own, mixin, `_inherits`, magic), and where? A dotted path is checked hop by hop. | `odoo_trace field sale.order partner_id.country_id.code` |
  188. | Every definition of a method in `super()` order, with the hooks it calls | `odoo_trace method sale.order _action_confirm --module x_eval` |
  189. | What a module transitively depends on, in load order | `odoo_trace depends x_eval` |
  190. | Does an xmlid exist: loaded XML, CSV row, or generated at install? | `odoo_trace xmlid base.lang_vi_VN` |
  191. | Which files of a module never load? | `odoo_trace unlisted x_eval` |
  192. Exit code 0 means found, 1 NOT FOUND (the verdict lists the closest real names), 2 a setup error. For
  193. example:
  194. ```text
  195. $ odoo_trace field sale.order delivery_date
  196. VERDICT: NOT FOUND: sale.order.delivery_date; closest fields: commitment_date (label 'Delivery Date'), ...
  197. $ odoo_trace field sale.order access_url
  198. .../addons/portal/models/portal_mixin.py:13 portal PortalMixin via=parent portal.mixin Char compute='_compute_access_url'
  199. VERDICT: FOUND via parent portal.mixin
  200. ```
  201. ## Everyday prompts
  202. You do not need to name the skill; it triggers on Odoo work. Being explicit helps on the first run.
  203. - **Add a field or view change:** "In module `sale_extra`, add a boolean `x_rush` to sale orders and
  204. show it after the warehouse on the form."
  205. - **Fix an install error:** paste the traceback, for example
  206. `Element '<xpath expr="//field[@name='warehouse_id']">' cannot be located in parent view`. The
  207. innermost frame in your module is the first citation.
  208. - **Override behaviour:** "After a sale order is confirmed and its pickings exist, post the picking
  209. names in the chatter." Expect it to trace `action_confirm` → `_action_confirm` and hook the right one.
  210. - **Rename or remove a stored field:** expect a version bump and a `migrations/<version>/` script.
  211. - **Ask about the source:** "Which model gets this field on Odoo 19 when `_inherit` is a list?"
  212. - **Review:** "Review the diff of `sale_extra` for Odoo 18" (uses `odoo-code-review` when installed).
  213. Ask for the evidence: the Brief, the test summary line, and which checks were skipped and why.
  214. ## What's in the toolkit
  215. ![Three parts of the toolkit: Skills for versioned references and workflows, Agents for tracing and review, and Rules for coding and security guidance](lib/image/overview.png)
  216. ### Skills
  217. | Pack | Purpose |
  218. | --- | --- |
  219. | [Odoo 16.0](skills/odoo-16.0/) | Version-specific development references and API highlights. |
  220. | [Odoo 17.0](skills/odoo-17.0/) | Version-specific development references and API highlights. |
  221. | [Odoo 18.0](skills/odoo-18.0/) | Version-specific development references and API highlights. |
  222. | [Odoo 19.0](skills/odoo-19.0/) | Version-specific development references and API highlights. |
  223. | [Odoo Workflow](skills/odoo-workflow/) | Trace-first procedure for every Odoo change: runtime detection, the trace helper, a cited Context Brief, and a definition of done run on a throwaway database. |
  224. | [Odoo Commit](skills/odoo-commit/) | Odoo-style commit messages, explicit staging, and commit preparation. |
  225. | [DTG Base](skills/dtg-base/) | References for DTGBase utilities: dates, timezones, batches, barcodes, text, and files. |
  226. Each Odoo pack starts from its `SKILL.md` index and `references/api-highlights.md`, then one guide
  227. per topic: models, fields, decorators, views, OWL, security, controllers, actions, data, reports,
  228. testing, performance, transactions, migrations, translations, mixins, manifests, development.
  229. ### Agents
  230. | Agent | Purpose |
  231. | --- | --- |
  232. | [Odoo Code Tracer](agents/odoo-code-tracer.md) | Follows entry points, overrides, inheritance and side effects through the project source. |
  233. | [Odoo Code Review](agents/odoo-code-review.md) | Reviews Odoo changes for correctness, security, multi-company, performance and version-specific standards, with a scored report. |
  234. ### Rules
  235. - [Coding style](rules/coding-style.md): naming, imports, and code organization.
  236. - [Security](rules/security.md): practices to fold into project instructions and review.
  237. ## Odoo versions and runtime
  238. Install the pack that matches your project: **16.0, 17.0, 18.0 or 19.0**. The workflow, its helper
  239. and this release's corrections to the 18.0 and 19.0 packs were checked against the Odoo 18 and 19
  240. source; the rest of the packs, and 16.0/17.0 in particular, are maintained without a full
  241. re-verification against a checkout.
  242. The helper takes the first of:
  243. 1. The `--odoo-root`, `--conf` and `--addons` flags.
  244. 2. `.claude/odoo.json` in the project or a parent directory, with the keys `odoo_version`,
  245. `odoo_root`, `conf`, `python`, `dev_db` and, optionally, `addons` (a list that replaces
  246. `addons_path`).
  247. 3. An `odoo-bin` configuration in `.claude/launch.json` whose addons path covers the working
  248. directory. Relative `addons_path` entries resolve against its `cwd`, as `odoo-bin` does.
  249. 4. The one `*.conf` whose uncommented `addons_path` covers the working directory, searched from the
  250. parent directory upwards (each level and its subdirectories). Two matching confs are a setup
  251. error: pin one in `.claude/odoo.json`.
  252. The version is `version_info` in the core's `odoo/release.py`. An `odoo_version` in
  253. `.claude/odoo.json` or a `.odoo-version` file must agree with it, or the helper stops instead of
  254. guessing. The workflow and both agents resolve the version in this order:
  255. 1. An explicit statement or invocation argument, such as `odoo_version: "18.0"`.
  256. 2. The version stated in the project `CLAUDE.md` or `AGENTS.md`.
  257. 3. The helper's `env` output.
  258. 4. Agents only, when the helper is not available: the same files read by hand, then serie-prefixed
  259. manifest versions such as `18.0.1.0` or `18.0.1.0.0` (short addon versions like `'1.2'` are
  260. ignored).
  261. 5. Nothing found, or sources that disagree: they ask. There is no default version.
  262. The agents use the pack directory, roots and helper path the workflow passes, or look for an
  263. installed pack; if none is found they say `pack not found` instead of guessing.
  264. ## Installation notes
  265. ### Bundled CLI targets
  266. Paths are relative to the destination project. `PACK` is the selected directory, such as `odoo-18.0`.
  267. | Target | Files written by the CLI |
  268. | --- | --- |
  269. | `cursor` | `.shared/skills/PACK/` and `.cursor/commands/skills.md` |
  270. | `claude` | `.claude/skills/skills/PACK/` |
  271. | `antigravity` | `.shared/skills/PACK/` and `.agent/workflows/skills.md` |
  272. | `kiro` | `.shared/skills/PACK/` and `.kiro/steering/skills.md` |
  273. | `docs` | `docs/skills/PACK/` |
  274. | `all` | All five destinations above. |
  275. The CLI copies whole pack directories, including the workflow's `scripts/` and `references/`. This
  276. describes file copies, not native skill discovery in every host: for Claude Code use the plugin, for
  277. other assistants the skills installer, or give the copied files to the assistant as context.
  278. - Run from the destination project, or pass `--dest /path/to/project`.
  279. - Existing files are kept unless you pass `--force`.
  280. - Cursor, Antigravity and Kiro share one entry file, `skills.md`; installing another pack keeps the
  281. existing entry unless forced, and forcing repoints it to the new pack.
  282. - `--offline` skips the CLI's update check; it does not make `npx` itself offline.
  283. - Preview with `--dry-run --offline`:
  284. ```bash
  285. npx @unclecat/agent-skills-cli init --ai cursor --skill skills --version odoo-18.0 --dry-run --offline
  286. ```
  287. ### Limits to know
  288. - The workflow can only cite what is on disk: keep the Odoo source (and enterprise, if you use it) in
  289. a checkout the conf points to.
  290. - The definition of done needs a PostgreSQL server and permission to create `scratch_*` databases.
  291. The assistant is told never to install or upgrade on a named database unless you ask.
  292. - The trace helper models the static load order of all roots, not what is installed in a given
  293. database.
  294. - More tokens per task, as measured above. Use the fast path for trivial edits.
  295. ## Contributing
  296. Improve version-specific references, add reproducible evals, refine review instructions, or report
  297. gaps through [issues](https://github.com/unclecatvn/agent-skills/issues).
  298. Before opening a pull request:
  299. ```bash
  300. npm test
  301. ```
  302. This validates skill and agent structure, plugin paths, version consistency, changelog coverage,
  303. selected reference checks, the workflow's Step 1 greps on fixtures under bash and zsh, and the trace
  304. helper on its fixture checkout (`tests/test_odoo_trace.sh`). It does not run Odoo itself. CI also runs
  305. a baseline-aware SkillSpector scan; see the [CI workflow](.github/workflows/ci.yml).
  306. If you change the helper, the greps or the workflow, also run the real-source checks against the
  307. checkouts you have:
  308. ```bash
  309. ODOO_ROOT_18=/path/to/odoo/18.0 ODOO_ROOT_19=/path/to/odoo/19.0 bash tests/test_odoo_trace.sh
  310. ODOO_ROOT=/path/to/odoo/18.0 bash tests/odoo-workflow-greps.sh
  311. python3 tests/bench_odoo_workflow.py --odoo 18.0=/path/to/odoo/18.0 --odoo 19.0=/path/to/odoo/19.0
  312. ```
  313. - `tests/test_odoo_trace.sh`: hand-verified helper checks on each real checkout; run it under zsh too.
  314. - `tests/odoo-workflow-greps.sh`: the Step 1 greps on real source, once per checkout, under bash and zsh.
  315. - `tests/bench_odoo_workflow.py`: the mechanical benchmark; `--workspace /path/to/project` also checks
  316. that the resolved roots include the Odoo core.
  317. - `tests/evals/odoo-workflow/`: 24 anti-hallucination evals with fixture modules;
  318. [benchmark.md](tests/evals/odoo-workflow/benchmark.md) records the last agent runs.
  319. Keep new skills under `skills/` with a `SKILL.md` entry point, keep version-specific changes in their
  320. pack, and include evidence (a source `file:line` or a command you ran) for behavioral claims.
  321. ## Releases and license
  322. See the [changelog](CHANGELOG.md) and the [npm package](https://www.npmjs.com/package/@unclecat/agent-skills-cli).
  323. Merging a version bump to `main` tags the release, publishes the GitHub release notes from the
  324. changelog, and publishes the CLI to npm.
  325. Released under the [MIT license](LICENSE). This is an independent community project, not an official
  326. Odoo product.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.