Odoo Migration Copilot
erpipe-org/mcp-odoo
Plan and de-risk an Odoo version upgrade (16→17→18→19/20) using odoo-mcp's migration workbench — audit custom addons, classify upgrade-log failures into a worklist, resolve model renames, and…
Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.
Install Odoo Upgrade Advisor
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/odoo-upgrade-advisor .claude/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .claude/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/odoo-upgrade-advisor .agents/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .agents/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/odoo-upgrade-advisor .cursor/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .cursor/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/odoo-upgrade-advisor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/odoo-upgrade-advisor .gemini/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .gemini/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/odoo-upgrade-advisor .github/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .github/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills odoo-upgrade-advisor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/odoo-upgrade-advisor .opencode/skills/odoo-upgrade-advisor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "odoo-upgrade-advisor" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-upgrade-advisor into .opencode/skills/odoo-upgrade-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-upgrade-advisor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
odoo-upgrade-advisor- GitHub stars
- 47k
- Used in
- 2 other repos
- Token cost
- ~1.3k tokens
- SKILL.md length
- 334 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.
- Works in 3 steps: Activate: Mention @odoo-upgrade-advisor,… → Plan: Receive the full upgrade roadmap… → Execute: Get a step-by-step upgrade…
- Tasks that involve Code migrations
- SKILL.md covers Overview, When to Use This Skill, How It Works and Upgrade Paths, plus 3 more sections
- Calls git and python3; reaches github.com and upgrade.odoo.com
What it does
Odoo Upgrade Advisor is an agent skill from sickn33/agentic-awesome-skills. Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code migrations. It works with Odoo. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Code migrations
Example prompts
- “/odoo-upgrade-advisor”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Activate: Mention @odoo-upgrade-advisor, state your current and target version.
- Plan: Receive the full upgrade roadmap and risk assessment.
- Execute: Get a step-by-step upgrade command sequence.
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.comupgrade.odoo.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Odoo Upgrade Advisor loads about 1.3k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 334 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 334 words, ~1,293 tokens.
Download SKILL.mdSave it as
.claude/skills/odoo-upgrade-advisor/SKILL.md (or your agent's skills folder).- name
- odoo-upgrade-advisor
- description
- Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.
- risk
- safe
- source
- self
- date_added
- 2026-09-04
Odoo Upgrade Advisor
Overview
Upgrading Odoo between major versions (e.g., v15 → v16 → v17) requires careful preparation, testing, and validation. This skill provides a structured pre-upgrade checklist, guides you through the upgrade tools (Odoo Upgrade Service and OpenUpgrade), and gives you a post-upgrade validation protocol.
When to Use This Skill
- Planning a major Odoo version upgrade.
- Identifying which custom modules need to be migrated.
- Running the upgrade on a staging environment before production.
- Validating the system after an upgrade.
How It Works
- Activate: Mention
@odoo-upgrade-advisor, state your current and target version. - Plan: Receive the full upgrade roadmap and risk assessment.
- Execute: Get a step-by-step upgrade command sequence.
Upgrade Paths
| From | To | Supported? | Tool |
|---|---|---|---|
| v16 | v17 | ✅ Direct | Odoo Upgrade Service / OpenUpgrade |
| v15 | v16 | ✅ Direct | Odoo Upgrade Service / OpenUpgrade |
| v14 | v15 | ✅ Direct | Odoo Upgrade Service / OpenUpgrade |
| v14 | v17 | ⚠️ Multi-hop | v14→v15→v16→v17 (cannot skip) |
| v13 or older | any | ❌ Not supported | Manual migration required |
Examples
Example 1: Pre-Upgrade Checklist
BEFORE YOU START:
☑ 1. List all installed modules (Settings → Technical → Modules)
Export to CSV and review for custom/OCA modules
☑ 2. Check OCA compatibility matrix for each community module
https://github.com/OCA/maintainer-tools/wiki/Migration-Status
☑ 3. Take a full backup (database + filestore) — your restore point
☑ 4. Clone production to a staging environment
☑ 5. Run the Odoo Upgrade pre-analysis:
https://upgrade.odoo.com/ → Upload DB → Review breaking changes report
☑ 6. Review custom modules against migration notes
(use @odoo-migration-helper for per-module analysis)
☑ 7. Upgrade and test in staging → Fix all errors → Re-test
☑ 8. Schedule a production maintenance window
☑ 9. Notify users of scheduled downtime
☑ 10. Perform production upgrade → Validate → Go/No-Go decisionExample 2: Community Upgrade with OpenUpgrade
# Clone OpenUpgrade for the TARGET version (e.g., upgrading to v17)
git clone https://github.com/OCA/OpenUpgrade.git \
--branch 17.0 \
--single-branch \
/opt/openupgrade
# Run the migration against your staging database
python3 /opt/openupgrade/odoo-bin \
--update all \
--database odoo_staging \
--config /etc/odoo/odoo.conf \
--stop-after-init \
--load openupgrade_framework
# Review the log for errors before touching production
tail -200 /var/log/odoo/odoo.log | grep -E "ERROR|WARNING|Traceback"Example 3: Post-Upgrade Validation Checklist
After upgrading, validate these critical areas before going live:
Accounting:
☑ Trial Balance totals match the pre-upgrade snapshot
☑ Open invoices, bills, and payments are accessible
☑ Bank reconciliation can be performed on a test statement
Inventory:
☑ Stock valuation report matches pre-upgrade (run Inventory Valuation)
☑ Open Purchase Orders and Sale Orders are visible
HR / Payroll:
☑ All employee records are intact
☑ Payslips from the last 3 months are accessible and correct
Custom Modules:
☑ Every custom module loaded without ImportError or XML error
☑ Run the critical business workflows end-to-end:
Create sale order → confirm → deliver → invoice → payment
Users & Security:
☑ User logins work correctly
☑ Access rights are preserved (spot-check 3-5 users)Best Practices
- ✅ Do: Always upgrade on a copy of production (staging) first — never the live instance.
- ✅ Do: Keep the old version running until the new version is fully validated and signed off.
- ✅ Do: Check OCA's migration status page: OCA Migration Status
- ✅ Do: Use the Odoo Upgrade Service pre-analysis report to get a list of breaking changes before writing any code.
- ❌ Don't: Skip intermediate versions — Odoo requires sequential upgrades (v14→v15→v16→v17).
- ❌ Don't: Upgrade custom modules and Odoo core simultaneously — adapt Odoo core first, then fix custom modules.
- ❌ Don't: Run OpenUpgrade against production directly — always test on a staging copy first.
Limitations
- Covers v14–v17 only. Versions v13 and older have a fundamentally different module structure and require manual migration.
- Enterprise-exclusive module changes (e.g.,
sign,account_accountant) may have undocumented breaking changes not included in OpenUpgrade. - The Odoo.sh automated upgrade path has a separate workflow (managed from the Odoo.sh dashboard) not covered here.
- OWL JavaScript component migration (legacy widget → OWL v16+) is a complex front-end topic beyond the scope of this skill.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/odoo-upgrade-advisor of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 2 other repositories
We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/odoo-upgrade-advisorantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/odoo-upgrade-advisor+1 more
- henryalouf/ruflow.agents/skills/odoo-upgrade-advisor.agents/skills/antigravity-awesome-skills/skills/odoo-upgrade-advisor+4 more
Compare with similar skills
Odoo Upgrade Advisor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Odoo Upgrade Advisor this skillsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Odoo Migration Copiloterpipe-org/mcp-odoo | 421 | — | ~770 | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Next Cache Components Adoptionvercel/next.js | 143k | 6 repos | ~8.3k | Automated safety check: Pass | MIT |
Similar skills
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
- Official
Next Cache Components Adoption
vercel/next.js
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces.
Deprecate R Functions and Arguments
tidyverse/dplyr
Walks through deprecating an R function or argument in a package: lifecycle warning, silenced tests, a new snapshot test, documentation badge and NEWS entry.
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Works with
Categories
Questions about Odoo Upgrade Advisor
What does Odoo Upgrade Advisor do?
Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation. Odoo Upgrade Advisor is an agent skill from sickn33/agentic-awesome-skills. Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.
When should I use Odoo Upgrade Advisor?
Odoo Upgrade Advisor fits situations like: tasks that involve Code migrations.
How do I install Odoo Upgrade Advisor in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a claude-code`. Or copy the skill folder (skills/odoo-upgrade-advisor in sickn33/agentic-awesome-skills) into .claude/skills/odoo-upgrade-advisor in your project. Claude Code loads it when a task matches its description.
How do I install Odoo Upgrade Advisor in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a codex`. Or copy the skill folder (skills/odoo-upgrade-advisor in sickn33/agentic-awesome-skills) into .agents/skills/odoo-upgrade-advisor in your project. Codex loads it when a task matches its description.
Can I use Odoo Upgrade Advisor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill odoo-upgrade-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/odoo-upgrade-advisor, .gemini/skills/odoo-upgrade-advisor, .github/skills/odoo-upgrade-advisor and .opencode/skills/odoo-upgrade-advisor in your project.
What does Odoo Upgrade Advisor need to run?
Going by SKILL.md and its folder, Odoo Upgrade Advisor needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3.
Does Odoo Upgrade Advisor access the network?
SKILL.md names 2 domains. In commands or code: github.com and upgrade.odoo.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Odoo Upgrade Advisor safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Odoo Upgrade Advisor use?
Odoo Upgrade Advisor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Odoo Upgrade Advisor use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Odoo Upgrade Advisor?
Skills that share tags, products or a category with Odoo Upgrade Advisor: Odoo Migration Copilot (erpipe-org/mcp-odoo, 421 stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Odoo Upgrade Advisor?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.