Agent skill

Adeu Redlining

by dealfluence in dealfluence/adeu

A skill your agent uses when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing…

MITAuto-check passedDocuments & Office

Install Adeu Redlining

skills CLI
$ npx skills add dealfluence/adeu --skill adeu-redlining -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dealfluence/adeu adeu-redlining --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dealfluence/adeu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/adeu-redlining .claude/skills/adeu-redlining && rm -rf skills-src

Use ~/.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/

Facts

Skill name
adeu-redlining
GitHub stars
165
Token cost
~2.4k tokens
SKILL.md length
1,087 words
Files
5 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing…

  • Works in 3 steps: MCP tools available. If you see Adeu MCP… → Bash available, no MCP tools. Shell out… → Neither available. Tell the user.…
  • Negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes
  • SKILL.md covers When to use this skill, Execution path — pick once,…, Core workflow and Critical gotchas, plus 2 more sections
  • Calls uvx, npx and uv

What it does

Adeu Redlining is an agent skill from dealfluence/adeu. Use this skill when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing tracked changes, replying to comments, comparing two versions, sanitizing author metadata, or finalizing a contract for distribution. Use whenever the user mentions redlines, track changes, contract review, .docx editing, or a Word document they want changed, even if they don't name a specific tool. Do NOT use for creating a…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/cli-fallback.md`, `references/criticmarkup.md` and `references/mcp-tools.md`). Compatibility notes: Requires either the Adeu MCP server (preferred — Node @adeu/mcp-server or Python adeu) OR uvx for the CLI fallback. Live MS Word integration requires Windows…

It sits in Documents & Office, covering Word documents and Contract review. It works with Microsoft Word, Python and Model Context Protocol. The repository describes itself as: docx ↔ LLM translator. Projects .docx office files to Markdown for editing. Projects edits back to OOXML as tracked changes (redlines). Python and Node.js implementations. The licence is MIT.

When your agent uses it

  • Negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes
  • Rejecting existing tracked changes
  • Replying to comments
  • Comparing two versions

Example prompts

  • “/adeu-redlining”

Requirements

  • Python 3
  • Node.js
  • Compatibility (from SKILL.md): Requires either the Adeu MCP server (preferred — Node `@adeu/mcp-server` or Python `adeu`) OR `uvx` for the CLI fallback. Live MS Word integration requires Windows + the Python `adeu` server.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. MCP tools available. If you see Adeu MCP tools in the session (read_docx, process_document_batch, accept_all_changes, diff_docx_files…
  2. Bash available, no MCP tools. Shell out to the Python CLI: uvx adeu . This is the only CLI Adeu ships — there is no Node CLI. Load…
  3. Neither available. Tell the user. Suggested install lines, in this order

What it can do on your machine

Read from SKILL.md and the folder at commit 096baa8. 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:

    • uvx
    • npx
    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uvx, npx and uv, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Requires either the Adeu MCP server (preferred — Node `@adeu/mcp-server` or Python `adeu`) OR `uvx` for the CLI fallback. Live MS Word integration requires Windows + the Python `adeu` server.

    From compatibility in the SKILL.md frontmatter.

Context cost

Adeu Redlining loads about 2.4k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 152 tokens; SKILL.md has 1,087 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~152
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7k

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 dealfluence/adeu at commit 096baa8, republished under its MIT licence (© dealfluence). 1,087 words, ~2,350 tokens.

Download SKILL.mdSave it as .claude/skills/adeu-redlining/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
adeu-redlining
description
Use this skill when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing tracked changes, replying to comments, comparing two versions, sanitizing author metadata, or finalizing a contract for distribution. Use whenever the user mentions redlines, track changes, contract review, .docx editing, or a Word document they want changed, even if they don't name a specific tool. Do NOT use for creating a Word document from scratch with no source file — use the docx skill for that.
compatibility
Requires either the Adeu MCP server (preferred — Node `@adeu/mcp-server` or Python `adeu`) OR `uvx` for the CLI fallback. Live MS Word integration requires Windows + the Python `adeu` server.
license
MIT (see LICENSE.txt)
metadata.homepage
https://adeu.ai
metadata.repository
https://github.com/dealfluence/adeu
metadata.version
1.18.2

Adeu — Tracked-Changes Redlining for .docx

Adeu is a Virtual DOM for Word documents. It translates .docx into LLM-friendly Markdown with CriticMarkup for tracked changes, lets you propose edits as native Word w:ins/w:del revisions, and writes the result back without destroying formatting, comments, or document structure.

When to use this skill

The user is working with an existing .docx and wants you to:

  • Propose edits that show up as Word Track Changes
  • Accept, reject, or reply to existing tracked changes and comments
  • Compare two versions of a document
  • Strip author metadata and lock a document for distribution
  • Read a contract intelligently, including its defined terms and cross-references

If the user wants a fresh Word document built from nothing, defer to the docx skill instead.

Execution path — pick once, then forget

Adeu runs in two modes. Pick the first that applies and stop:

  1. MCP tools available. If you see Adeu MCP tools in the session (read_docx, process_document_batch, accept_all_changes, diff_docx_files, finalize_document), use them. This is the preferred path on every platform. Load references/mcp-tools.md before planning any non-trivial batch.
  2. Bash available, no MCP tools. Shell out to the Python CLI: uvx adeu <subcommand>. This is the only CLI Adeu ships — there is no Node CLI. Load references/cli-fallback.md for the command surface and the JSON shape adeu apply expects.
  3. Neither available. Tell the user. Suggested install lines, in this order:
    • Claude Code plugin (covers everything): /plugin marketplace add dealfluence/adeu then /plugin install adeu-redlining@adeu-skills
    • Node MCP server (recommended for most users, zero Python required): npx -y @adeu/mcp-server
    • Python MCP server (required for Live MS Word integration on Windows, and for protection_mode="encrypt" on finalize_document): uvx --from adeu adeu-server
    • Python CLI only (for scripted/headless pipelines): uv tool install adeu

Do not present these as options to the user mid-task. Pick the available path and proceed.

Core workflow

Every redlining task follows the same shape. Follow it in order:

  1. Read first. Always read the document before editing. Use read_docx (MCP) or uvx adeu extract (CLI). For long contracts, start with mode="outline" to see the heading structure, then read specific pages.
  2. Plan the edits. Each edit is either a search-and-replace (most common), an accept/reject of an existing tracked change by ID, a reply to a comment by ID, or a structural table edit. Write the plan down explicitly before applying.
  3. Apply as one batch. Send all edits in a single process_document_batch call (MCP) or one adeu apply invocation (CLI). Edits apply sequentially: each edit evaluates against the document state produced by the edits before it, so dependent edits may be chained — a later edit must target the text as it reads after the earlier edits.
  4. Verify. If the user asked for a specific outcome, re-read the modified file with clean_view=true (MCP) or --clean (CLI) and confirm.

Batches are transactional: if any edit fails validation, the whole batch is rejected, nothing is written, and the error reports per-edit failures you can correct and resubmit.

Show full SKILL.md (598 more words)Show less

Critical gotchas

These are environment-specific facts that will trip you up if you assume Word/.docx behaves like plain text. Read this section every time.

  • IDs are session-bound. Change IDs (Chg:12) and comment IDs (Com:5) shift every time the document state changes. Before any accept, reject, or reply action, call read_docx immediately before the batch. Never reuse IDs from earlier in the conversation. Never reuse IDs across a save/reload boundary.

  • Batches apply sequentially and reject transactionally. You can rename X → Y and then in the same batch modify Y — but the second edit must target Y (the text as it reads after the rename), not the original X wording. Stale targets fail validation, and any validation failure rejects the whole batch (nothing is applied) with per-edit errors explaining what to fix.

  • target_text must be unique by default. match_mode: "strict" (the default) requires a single match. Either add surrounding context to disambiguate, or explicitly set match_mode: "first" or "all". Set regex: true to use a regular expression; capture groups are available as $1, $2 in new_text.

  • Do not write CriticMarkup tags manually. Never put {++, {--, {>>, or {== into new_text. Use the comment field on the edit to attach a margin comment. Adeu generates the tracked-change XML from your plain replacement text.

  • new_text supports Markdown. Headings (# through ######), **bold**, _italic_ (not *italic* — strictly underscores), and \n\n to split into paragraphs. Empty string deletes.

  • Read the appendix before editing structural references. read_docx projects a semantic appendix at the bottom of the document containing defined terms, cross-references ([~text~](#_Ref)), internal anchors ({#_BookmarkName}), and footnotes ([^fn-id]). Anything inside the <!-- READONLY_BOUNDARY_START --> marker is read-only — attempting to modify it via search-and-replace will be rejected. Use mode="appendix" to see it explicitly.

  • clean_view toggles the document state you see. clean_view=false (default) shows the raw document with all pending tracked changes inline as CriticMarkup. clean_view=true shows what the document would look like if every pending change were accepted. Choose deliberately — comparing the wrong view to user intent is the most common source of confusion.

  • Page indexing. page=N paginates the body. page='all' or omitting page with a search_query searches the whole document. Don't assume page numbers from the user's PDF viewer match Adeu's pagination — they often don't.

  • Live Word (Windows COM) is Python-only. If the user is editing the active document in Word, only the Python adeu server supports it. The Node server does not. Table row inserts/deletes are also not supported in Live Word mode — fall back to disk editing.

  • Multi-author redlines. If the document has tracked changes from multiple authors, edits that overlap another author's pending insertion are rejected to prevent silent destruction of their work. Tell the user; don't try to force it.

Edit types — quick reference

Use references/mcp-tools.md for the full schema. The five operations:

TypePurposeRequired fields
modifySearch-and-replace as a tracked changetarget_text, new_text
acceptFinalize an existing tracked changetarget_id (e.g. Chg:12)
rejectRevert an existing tracked changetarget_id
replyReply to an existing commenttarget_id (e.g. Com:5), text
insert_row / delete_rowAdd or remove a table rowtarget_text (a cell value to anchor on), plus position/cells for inserts

comment is optional on modify/accept/reject to attach a margin comment.

Reference loading

Load these only when relevant — they're not part of the base context:

  • references/mcp-tools.md — full MCP tool schemas, parameter details, process_document_batch discriminated union. Load before planning any non-trivial edit batch on the MCP path.
  • references/cli-fallback.md — uvx adeu subcommands and the edits.json shape. Load on the CLI path.
  • references/criticmarkup.md — CriticMarkup syntax and Adeu's semantic projections (footnotes, cross-refs, anchors, defined-terms appendix). Load when interpreting raw read_docx output or when the user asks about a marker like [^fn-3] or {#_BookmarkName}.

© dealfluence, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/adeu-redlining of dealfluence/adeu.

  • SKILL.md
  • LICENSE.txt
  • references/cli-fallback.md
  • references/criticmarkup.md
  • references/mcp-tools.md

Open the folder on GitHubat commit 096baa8

Compare with similar skills

Adeu Redlining 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.

Adeu Redlining compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Adeu Redlining this skilldealfluence/adeu165—~2.4kAutomated safety check: PassMIT
MineruNebutra/MinerU-Skill122—~1.4kAutomated safety check: PassMIT
Pii Contract Analyzegregmos/PII-Shield149—~8.9kAutomated safety check: NotesMIT
Contract Review Engineinfometa/workbuddyskills342—~1.8kAutomated safety check: PassNone
DOCXMemTensor/memmy-agent2.1k—~1.9kAutomated safety check: PassMIT
Office Open XML Utilitiespipeshub-ai/pipeshub-ai3.8k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into clean Markdown with MinerU — a fast, zero-config document parser for AI agents.

    122 GitHub stars~1.4k tokensUpdated 13 days ago
    Documents & OfficeAuto-check passed
  • Pii Contract Analyze

    gregmos/PII-Shield

    Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.

    149 GitHub stars~8.9k tokensUpdated 3 mo ago
    Legal & ComplianceAuto-check: notes
  • Contract Review Engine

    infometa/workbuddyskills

    Review contracts for risk (scenarios C5/C6) — background assessment before signing (counterparty qualification, transaction-mode legality, contract-form fit, special procedures) and clause-by-clause…

    342 GitHub stars~1.8k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • DOCX

    MemTensor/memmy-agent

    Create, read, edit, review, redline, comment on, merge, audit, render, and verify .docx Word documents, including layout-sensitive and OOXML-level work.

    2.1k GitHub stars~1.9k tokensUpdated 7 days ago
    Documents & OfficeAuto-check passed
  • Office Open XML Utilities

    pipeshub-ai/pipeshub-ai

    Unpacks a .docx or .pptx into pretty-printed XML, lets you make small targeted edits, and repacks it into a file Office will open.

    3.8k GitHub stars~1.1k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Markdown Exporter

    bowenliang123/markdown-exporter

    Convert Markdown text to DOCX, PPTX, XLSX, PDF, PNG, SVG, HTML, IPYNB, MD, CSV, JSON, JSONL, XML files, and extract code blocks in Markdown to Python, Bash,JS and etc files.

    271 GitHub starsUsed in 1 repo~5.3k tokens
    Documents & OfficeAuto-check passed

More from dealfluence/adeu

  • Hunt Comments

    dealfluence/adeu

    A skill your agent uses when hunting down verbose, narrative, or dead comments in the codebase to reduce comment noise and character counts.

    165 GitHub stars~355 tokensUpdated 2 days ago
    Auto-check passed
  • Analyze Branching

    dealfluence/adeu

    Formally analyzes control-flow branchings, cyclomatic complexity, nesting depths, and branch redundancies across Python and TypeScript engine files.

    165 GitHub stars~290 tokensUpdated 2 days ago
    Auto-check passed
  • Check Duplication

    dealfluence/adeu

    A skill your agent uses when checking for or pruning duplicate code blocks across source files.

    165 GitHub stars~291 tokensUpdated 2 days ago
    Auto-check passed

Questions about Adeu Redlining

What does Adeu Redlining do?

A skill your agent uses when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing…. Adeu Redlining is an agent skill from dealfluence/adeu.docx) — including proposing edits as tracked changes, accepting or rejecting existing tracked changes, replying to comments, comparing two versions, sanitizing author metadata, or finalizing a contract for distribution.

When should I use Adeu Redlining?

Adeu Redlining fits situations like: negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes; rejecting existing tracked changes; replying to comments; comparing two versions.

How do I install Adeu Redlining in Claude Code?

Run `npx skills add dealfluence/adeu --skill adeu-redlining -a claude-code`. Or copy the skill folder (skills/adeu-redlining in dealfluence/adeu) into .claude/skills/adeu-redlining in your project. Claude Code loads it when a task matches its description.

How do I install Adeu Redlining in Codex?

Run `npx skills add dealfluence/adeu --skill adeu-redlining -a codex`. Or copy the skill folder (skills/adeu-redlining in dealfluence/adeu) into .agents/skills/adeu-redlining in your project. Codex loads it when a task matches its description.

Can I use Adeu Redlining 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 dealfluence/adeu --skill adeu-redlining -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adeu-redlining, .gemini/skills/adeu-redlining, .github/skills/adeu-redlining and .opencode/skills/adeu-redlining in your project.

What does Adeu Redlining need to run?

Going by SKILL.md and its folder, Adeu Redlining needs the command-line tools its instructions call (uvx, npx and uv). Our summary lists: Python 3; Node.js. Compatibility (from SKILL.md): Requires either the Adeu MCP server (preferred — Node `@adeu/mcp-server` or Python `adeu`) OR `uvx` for the CLI fallback. Live MS Word integration requires Windows + the Python `adeu` server..

Does Adeu Redlining access the network?

SKILL.md contains no URLs. Its commands use uvx, npx and uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Adeu Redlining 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 Adeu Redlining use?

Adeu Redlining is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Adeu Redlining use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.

What are the alternatives to Adeu Redlining?

Skills that share tags, products or a category with Adeu Redlining: Mineru (Nebutra/MinerU-Skill, 122 stars), Pii Contract Analyze (gregmos/PII-Shield, 149 stars), Contract Review Engine (infometa/workbuddyskills, 342 stars) and DOCX (MemTensor/memmy-agent, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adeu Redlining?

dealfluence (a GitHub organization) maintains it in dealfluence/adeu, which has 165 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.

Source: dealfluence/adeu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.