Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Produce properly-formatted tracked changes for a Word document.
Install DOCX Tracked Changes
$ npx skills add mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills docx-tracked-changes --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/docx-tracked-changes .claude/skills/docx-tracked-changes && 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 "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .claude/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changesType 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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills docx-tracked-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/docx-tracked-changes .agents/skills/docx-tracked-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .agents/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills docx-tracked-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/docx-tracked-changes .cursor/skills/docx-tracked-changes && 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 "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .cursor/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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/mohitagw15856/pm-claude-skills.git --path skills/docx-tracked-changes--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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills docx-tracked-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/docx-tracked-changes .gemini/skills/docx-tracked-changes && 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 "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .gemini/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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 mohitagw15856/pm-claude-skills docx-tracked-changesInstalls 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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/docx-tracked-changes .github/skills/docx-tracked-changes && 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 "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .github/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills docx-tracked-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/docx-tracked-changes .opencode/skills/docx-tracked-changes && 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 "docx-tracked-changes" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/docx-tracked-changes into .opencode/skills/docx-tracked-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-tracked-changes", 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
docx-tracked-changes- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 669 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce properly-formatted tracked changes for a Word document.
- Works in 8 steps: Redline Summary → Top-Level Changes → Line-by-Line Tracked Changes → …
- Asked to redline a document
- SKILL.md covers Required Inputs, Output Structure, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
DOCX Tracked Changes is an agent skill from mohitagw15856/pm-claude-skills. Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.
Its SKILL.md is about 1.4k 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 Documents & Office, covering Word documents. It works with Microsoft Word. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to redline a document
- Suggest edits to a contract
- Create tracked changes for review
- Mark up a document with proposed revisions
Example prompts
- “/docx-tracked-changes”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
DOCX Tracked Changes loads about 1.4k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 669 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 669 words, ~1,365 tokens.
Download SKILL.mdSave it as
.claude/skills/docx-tracked-changes/SKILL.md (or your agent's skills folder).- name
- docx-tracked-changes
- description
- Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.
Word Doc Tracked Changes Skill
Produces properly-structured tracked changes for a Word document — insertions, deletions, replacements, and margin comments formatted so they can be applied directly to the source document. Built to leverage Opus 4.7 improvements in .docx redlining and tracked changes generation.
Required Inputs
Ask the user for these if not provided:
- The document (paste the text or upload the .docx)
- Review type (legal review / copy edit / substantive rewrite / compliance check / plain English rewrite)
- Review scope (full document / specific sections / specific clause type)
- Reviewer role (author / manager / legal counsel / subject matter expert)
Output Structure
1. Redline Summary
Document: [Name or identifier] Review type: [As stated] Reviewer: [Role] Total changes: [Insertions: N / Deletions: N / Comments: N] Overall assessment: [1-2 sentences — is this document close to final, or does it need substantial revision?]
2. Top-Level Changes
Changes that affect the meaning or structure of the document:
Change N — [Section or paragraph reference]
- Original: "[Exact original text]"
- Suggested: "[Proposed new text]"
- Reason: [Why this change — substantive/legal/clarity]
3. Line-by-Line Tracked Changes
For each paragraph that needs changes, format as:
[Paragraph reference — e.g. "Section 3, Paragraph 2"]
Original:
[Exact original paragraph]
Tracked changes:
[Same paragraph with deletions marked as
strikethroughand insertions marked as bold]
Clean version:
[Final clean text after applying changes]
4. Margin Comments
Comments that flag issues without proposing a specific wording change:
Comment N — [Location] "[Comment text — written as the reviewer would write it. Direct, specific, actionable.]"
Comments are for things like:
- "This clause conflicts with Section 7 — please reconcile"
- "Missing definition of [term] used throughout"
- "Confirm figure with finance team"
5. Stylistic Edits
Line-level stylistic changes (if scope includes copy editing):
| Location | Before | After | Reason |
|---|---|---|---|
| Para 3 | [Text] | [Text] | [Readability/grammar/consistency] |
6. Pattern Flags
Issues that repeat across the document:
[Pattern — e.g. "Passive voice overuse"]
- Instances: [count]
- Examples: [2-3 specific locations]
- Suggested approach: [How to address]
7. Review Completeness
| Review dimension | Covered |
|---|---|
| Grammar and syntax | Yes / No |
| Clarity and readability | Yes / No |
| Substantive accuracy | Yes / No / N/A |
| Compliance/legal check | Yes / No / N/A |
| Consistency with referenced documents | Yes / No / N/A |
8. How to Apply These Changes
Instructions for applying the redline:
In Microsoft Word:
- Enable Track Changes (Review tab → Track Changes)
- Apply the changes from Section 3 in order
- Add comments from Section 4 using Review → New Comment
- Send the redlined document back to the reviewer
In Google Docs:
- Switch to Suggesting mode (top right pencil icon)
- Apply the changes from Section 3
- Add comments using the comment button in the margin
Show full SKILL.md (251 more words)Show less
Quality Checks
- Every tracked change has the original text preserved exactly
- Substantive changes are separated from stylistic changes
- Comments are written as the reviewer would write them, not meta-commentary
- Pattern issues identified separately from individual changes
- Application instructions match the target platform
Anti-Patterns
- Do not paraphrase original text when creating tracked deletions — the original text must be preserved exactly, character for character, or the tracked change cannot be reviewed against source
- Do not mix substantive changes with stylistic edits in the same section — reviewers need to approve substantive changes at a different threshold than copy edits
- Do not write margin comments as meta-commentary about the review process ("This section needs work") — comments must be actionable instructions the author can act on
- Do not flag every imperfect sentence as a change — over-redlining trains authors to accept changes without reading, which defeats the purpose of tracked review
- Do not produce a redline without a summary of top-level changes — reviewers read the summary first and use it to decide which changes to scrutinise in detail
Example Trigger Phrases
- "Redline this contract"
- "Create tracked changes for this document"
- "Mark up this document with proposed edits"
- "Review this and suggest changes in tracked changes format"
- "Give me a redline version of this draft"
Why This Works Better on Opus 4.7
Tracked changes require the model to preserve source text exactly while suggesting alternatives — earlier models would paraphrase the original or lose track of which text was original vs suggested. Opus 4.7 improvements specifically target this workflow.
© mohitagw15856, 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/docx-tracked-changes of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
DOCX Tracked Changes 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 |
|---|---|---|---|---|---|---|
| DOCX Tracked Changes this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 782 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9k | — | ~19k | Automated safety check: Pass | Apache-2.0 |
Similar skills
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
BiSheng DOCX Builder
dataelement/bisheng
Builds or edits Word .docx documents inside BiSheng's code executor with python-docx, handling Chinese fonts, tables of contents, page numbers and official-document layout.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Works with
Categories
Questions about DOCX Tracked Changes
What does DOCX Tracked Changes do?
Produce properly-formatted tracked changes for a Word document. DOCX Tracked Changes is an agent skill from mohitagw15856/pm-claude-skills. Produce properly-formatted tracked changes for a Word document.
When should I use DOCX Tracked Changes?
DOCX Tracked Changes fits situations like: asked to redline a document; suggest edits to a contract; create tracked changes for review; mark up a document with proposed revisions.
How do I install DOCX Tracked Changes in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a claude-code`. Or copy the skill folder (skills/docx-tracked-changes in mohitagw15856/pm-claude-skills) into .claude/skills/docx-tracked-changes in your project. Claude Code loads it when a task matches its description.
How do I install DOCX Tracked Changes in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a codex`. Or copy the skill folder (skills/docx-tracked-changes in mohitagw15856/pm-claude-skills) into .agents/skills/docx-tracked-changes in your project. Codex loads it when a task matches its description.
Can I use DOCX Tracked Changes 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 mohitagw15856/pm-claude-skills --skill docx-tracked-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docx-tracked-changes, .gemini/skills/docx-tracked-changes, .github/skills/docx-tracked-changes and .opencode/skills/docx-tracked-changes in your project.
What does DOCX Tracked Changes need to run?
SKILL.md names no scripts, command-line tools or credentials: DOCX Tracked Changes is instructions for the agent only.
Does DOCX Tracked Changes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is DOCX Tracked Changes 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 DOCX Tracked Changes use?
DOCX Tracked Changes 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 DOCX Tracked Changes use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 DOCX Tracked Changes?
Skills that share tags, products or a category with DOCX Tracked Changes: Markitdown (ImCa0/just-laws, 782 stars), DOCX (rvdbreemen/OTGW-firmware, 207 stars), Gzh Design (isjiamu/gzh-design-skill, 3.9k stars) and Word Document Reader and Writer (HKUDS/DeepTutor, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains DOCX Tracked Changes?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.