Agent skill

Journal Copyeditor DOCX

by mikemikeqqq in mikemikeqqq/copyeditor-skill

Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals.

MITAuto-check passedDocuments & Office

Install Journal Copyeditor DOCX

skills CLI
$ npx skills add mikemikeqqq/copyeditor-skill --skill journal-copyeditor-docx -a claude-code

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

GitHub CLI
$ gh skill install mikemikeqqq/copyeditor-skill journal-copyeditor-docx --agent claude-code

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

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
journal-copyeditor-docx
GitHub stars
292
Token cost
~3.9k tokens
SKILL.md length
1,776 words
Files
40 (incl. scripts, references, assets)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals.

  • Works in 12 steps: Language and Readability → Theory and Argument Quality → Construct and Terminology Consistency → …
  • The user asks to proofread
  • SKILL.md covers Default Scope, Intake Profile, Non-Negotiable Editorial… and Edit, Comment, or Report…, plus 6 more sections
  • Calls python

What it does

Journal Copyeditor DOCX is an agent skill from mikemikeqqq/copyeditor-skill. Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals. Use when the user asks to proofread, line-edit, polish, revise, redline, or prepare a manuscript with tracked changes, editor comments, a clean accepted copy, PDF review copy, and a structured editorial report. The skill preserves existing formatting, revisions, comments, citation fields, equations, tables, figures, footnotes, and document structure while auditing language…

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 43 other files, including scripts, reference files and assets (for example `README.en.md`, `README.md` and `agents/openai.yaml`).

It sits in Documents & Office, covering Word documents and Citation management. It works with Microsoft Word. The licence is MIT.

When your agent uses it

  • The user asks to proofread
  • Prepare a manuscript with tracked changes
  • Editor comments
  • A clean accepted copy

Example prompts

  • “/journal-copyeditor-docx”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Language and Readability
  2. Theory and Argument Quality
  3. Construct and Terminology Consistency
  4. Methods and Statistical Reporting
  5. Citations and References
  6. Submission Suitability and Reviewer Risk
  7. Document Integrity
  8. Baseline Inspection
  9. Editorial Map
  10. Tracked Copyedit
  11. Comments and Review Report
  12. Clean Derivative and PDF

What it can do on your machine

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

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • python

    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

Journal Copyeditor DOCX loads about 3.9k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 198 tokens; SKILL.md has 1,776 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from mikemikeqqq/copyeditor-skill at commit df3738b, republished under its MIT licence (© mikemikeqqq). 1,776 words, ~3,896 tokens.

Download SKILL.mdSave it as .claude/skills/journal-copyeditor-docx/SKILL.md (or your agent's skills folder). This skill also uses 39 other files; get the full folder from GitHub.
name
journal-copyeditor-docx
description
Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals. Use when the user asks to proofread, line-edit, polish, revise, redline, or prepare a manuscript with tracked changes, editor comments, a clean accepted copy, PDF review copy, and a structured editorial report. The skill preserves existing formatting, revisions, comments, citation fields, equations, tables, figures, footnotes, and document structure while auditing language, argument logic, construct terminology, methods, statistical reporting, citation-reference correspondence, causal claims, reviewer risks, and document integrity. It supports target-journal profiles when supplied but does not assume any specific journal.

Journal Copyeditor DOCX

Conduct publication-oriented copyediting and consistency review of academic manuscripts in .docx format. Apply the core docx skill for document editing, tracked changes, comments, rendering, and integrity verification.

Default Scope

For a request described as comprehensive, submission-ready, or journal copyediting, perform all of the following unless the user narrows the task:

  1. Language and readability editing.
  2. Theory, argument, and claim-boundary review.
  3. Construct and terminology consistency review.
  4. Methodological and statistical reporting audit.
  5. Citation and reference correspondence audit.
  6. Target-journal or journal-neutral submission-suitability review.
  7. DOCX structure, formatting, field, revision, and rendering validation.

Intake Profile

Determine from the manuscript and request:

  • manuscript file and supplementary files;
  • target journal, discipline, and article type, if specified;
  • English variety and citation style, if specified;
  • editing intensity: light, medium, heavy, or comprehensive;
  • required reviewer name and initials;
  • required deliverables.

If the target journal is not specified, use a journal-neutral, high-quality academic profile appropriate to the discipline. Do not infer or hard-code a particular journal. If a journal is specified and current author guidance is needed, verify only against the journal's official current instructions and state the profile used in the report.

Default reviewer identity: Copy Editor / CE.

Non-Negotiable Editorial Contract

  • Preserve the source file. Work only on copies.
  • Preserve all existing tracked revisions and comments in the tracked deliverable.
  • Preserve citation-manager fields, cross-references, equations, hyperlinks, footnotes/endnotes, section breaks, tables, figures, captions, numbering, and styles.
  • Do not fabricate, infer, or repair empirical facts without evidence from the supplied manuscript or verified source files.
  • Do not invent theories, constructs, mechanisms, hypotheses, citations, sample details, analyses, coefficients, p-values, confidence intervals, or reference metadata.
  • Do not strengthen novelty, causality, generalizability, or managerial implications beyond what the design and evidence support.
  • Use the same term for the same construct. Do not rotate technical terms for stylistic variety.
  • Make the smallest safe tracked edit. Avoid paragraph-wide delete-and-reinsert revisions for ordinary copyediting.
  • Make substantive meaning changes only when clearly supported. Otherwise add a concise Word comment and report item.
  • Never silently reconcile conflicting values. Flag them and identify every affected location.
  • Do not update citation fields, reference-manager fields, numbering fields, or cross-references unless explicitly requested and verified.

Edit, Comment, or Report Decision Rule

Edit directly with tracked changes when the correction is local, unambiguous, and meaning-preserving, including grammar, syntax, punctuation, concision, transition, terminology normalization, and defensible hedging.

Add a Word comment when resolution requires author knowledge, new evidence, reanalysis, construct choice, theoretical repositioning, methodological justification, or interpretation of conflicting values.

Add a report item when the issue is global, repeated, submission-level, or difficult to anchor at one location. Use both a comment and a report item for serious issues.

Do not use comments for routine grammar edits.

Comprehensive Audit Domains

1. Language and Readability
  • Correct grammar, punctuation, spelling, agreement, syntax, articles, prepositions, parallelism, and word choice.
  • Replace translationese and Chinese-influenced sentence structure with natural academic English.
  • Reduce redundancy, nominalization, vague pronouns, unnecessary passive voice, inflated wording, and AI-like filler.
  • Improve paragraph unity, topic sentences, transitions, and section flow.
  • Preserve technical nuance and the authors' intended meaning.

Open references/language-and-argument.md for detailed rules.

2. Theory and Argument Quality
  • Check that each section performs its proper function.
  • Trace the logic from research problem to gap, research question, theory, hypotheses, findings, contributions, implications, limitations, and conclusion.
  • Test whether each claim has a stated basis, logical bridge, boundary, and evidentiary support.
  • Flag unsupported novelty claims, missing comparators, circular logic, construct substitution, post hoc theorizing, and implications that exceed the findings.
  • Do not introduce a new theory, construct, mechanism, or citation unless clearly marked as an editorial recommendation.

Open references/theory-construct-review.md.

3. Construct and Terminology Consistency

Create an internal construct dictionary covering:

  • canonical construct name and abbreviation;
  • conceptual definition and defining attributes;
  • conceptual domain, referent, unit, and level of analysis;
  • temporal status and dimensional structure;
  • role in the theoretical and empirical model;
  • operationalization, manipulation, proxy, or scale;
  • item labels, subdimensions, and scoring direction;
  • expected relationship with other variables;
  • neighboring constructs that require differentiation;
  • sections, tables, figures, and appendices where the construct appears.

Apply a general construct-differentiation check rather than relying on fixed construct pairs. For every focal and neighboring construct, compare definition, conceptual domain, referent, level, temporal scope, dimensionality, nomological role, and operationalization. Verify that:

  • one construct is not given multiple labels without justification;
  • one label is not used for substantively different constructs;
  • distinct constructs have an explicit conceptual boundary rather than merely different names;
  • the measure or manipulation represents the stated construct rather than an adjacent attribute;
  • proxies, indicators, dimensions, mechanisms, outcomes, and manipulation checks are not presented as interchangeable;
  • construct meaning remains stable across theory, hypotheses, methods, results, discussion, tables, figures, and appendices.

Flag duplicated or mismatched items, undeveloped or unmeasured constructs, silent changes in level or referent, and distinctions that require author judgment or additional validity evidence.

4. Methods and Statistical Reporting

Check across text, tables, figures, notes, appendices, and supplementary materials:

  • study numbering, sample sizes, exclusions, cell sizes, demographics, and conditions;
  • variable names, coding, reference categories, scale anchors, item wording, reliability, validity, and manipulation checks;
  • coefficients, standard errors, test statistics, degrees of freedom, p-values, confidence intervals, effect sizes, odds ratios, and directions;
  • model names, bootstrap samples, conditional effects, indirect-effect scale, covariates, robustness checks, and stated conclusions;
  • causal language, mediation language, and generalization relative to design.

Do not alter a numerical result merely because it appears wrong. Flag it, report the locations, and request verification.

Open references/methods-statistics-review.md.

5. Citations and References
  • Match in-text citations to reference entries and identify uncited references.
  • Check names, years, suffixes, citation order, duplicate records, incomplete metadata, DOI/URL formatting, and inconsistent journal-title styling.
  • Preserve reference-manager fields. Do not convert fields to plain text unless explicitly requested.
  • Do not fabricate or replace references. When external verification is requested, use authoritative bibliographic sources and clearly distinguish verified corrections from editorial suspicions.

Open references/citation-reference-review.md.

6. Submission Suitability and Reviewer Risk

If a target journal is supplied, assess fit using its verified profile. Otherwise assess against general standards for a strong peer-reviewed article in the discipline.

Review for:

  • unclear marketing, management, social-science, or discipline-specific problem relevance;
  • incremental contribution or excessive overlap with adjacent research;
  • weak mechanism, missing boundary conditions, construct overlap, and overclaimed novelty;
  • identification weaknesses, manipulation confounds, common-method concerns, selective controls, or outcome-validity problems;
  • weak connection among abstract, introduction, results, discussion, and conclusion;
  • practical implications unsupported by the evidence;
  • missing ethics, consent, transparency, data availability, funding, conflict, or AI-use statements when applicable.

Assign risk severity using references/reviewer-risk-rubric.md.

Show full SKILL.md (709 more words)Show less
7. Document Integrity

Audit before and after editing:

  • existing revisions and comments;
  • field codes and hyperlinks;
  • equations and symbols;
  • tables, figures, captions, and image relationships;
  • footnotes/endnotes;
  • headings, numbering, page/section breaks, headers/footers, and styles;
  • unexpected CJK characters, mojibake, replacement glyphs, missing text, formatting drift, and corrupted package parts.

Open references/tracked-changes-integrity.md.

Workflow

Phase 1: Baseline Inspection
  1. Copy the source into a dedicated work directory.
  2. Confirm that the DOCX opens and is a valid ZIP package.
  3. Run scripts/audit_docx.py on the source.
  4. Run scripts/audit_citations.py and scripts/audit_statistics.py when relevant.
  5. Record source counts for paragraphs, tables, figures, fields, comments, revisions, sections, footnotes, and hyperlinks.
  6. Render the source and inspect representative high-risk pages before editing.
Phase 2: Editorial Map
  1. Identify article structure and study structure.
  2. Build the construct dictionary and study-consistency matrix.
  3. Identify global terminology decisions before local editing.
  4. Separate copyediting issues from author-decision issues.
  5. Establish a target-journal profile only when one is specified.
Phase 3: Tracked Copyedit

Preferred implementation order:

  1. Microsoft Word automation with Track Changes, when available.
  2. A reliable office automation path that preserves revisions and fields.
  3. Targeted OOXML redlines using the core docx skill, followed by strict structural and visual validation.

Edit paragraph by paragraph and table by table. Preserve local run formatting. Use verified global replacement only for low-risk, exact terminology normalization.

Phase 4: Comments and Review Report

Add comments for unresolved author decisions. Comments should:

  • identify the exact issue;
  • explain why it matters;
  • specify the action or evidence needed;
  • avoid rewriting the manuscript in the comment.

Prepare a separate review report using references/report-template.md. For comprehensive tasks, the report must cover:

  • major language issues;
  • construct and terminology inconsistencies;
  • theoretical and logical weaknesses;
  • methodological and statistical inconsistencies;
  • citation and reference problems;
  • potential reviewer concerns;
  • issues requiring clarification, reanalysis, or substantive revision;
  • journal profile and style assumptions used;
  • integrity and validation summary.
Phase 5: Clean Derivative and PDF

Create the clean DOCX from the tracked copy, not from the source:

  • accept all revisions in the clean derivative;
  • remove comments from the clean derivative unless the user requests otherwise;
  • preserve all substantive document structures and fields;
  • export the clean version to PDF.

Never accept revisions or remove comments in the tracked deliverable.

Phase 6: Validation and Visual QA
  1. Reopen all DOCX deliverables.
  2. Run scripts/audit_docx.py on tracked and clean copies.
  3. Confirm source structures were retained unless intentionally changed.
  4. Confirm tracked insertion/deletion and comment counts are plausible.
  5. Confirm the clean copy contains no unresolved revision markup.
  6. Render the tracked and clean DOCX files with the core docx renderer.
  7. Inspect every page at normal reading scale.
  8. Check title/abstract, tables, figures, equations, references, appendices, comment locations, and edited high-density pages at higher zoom.
  9. Correct and repeat until all gates pass.

Default Deliverables

For a comprehensive manuscript request, provide:

  1. manuscript_tracked_changes.docx
  2. manuscript_clean.docx
  3. manuscript_clean.pdf
  4. copyediting_manuscript_review_report.docx

Optionally provide machine-readable audit files in a separate audit/ folder, but do not clutter the main delivery unless requested.

For limited proofreading or a user-specified output, deliver only the requested files.

Final Quality Gates

Do not deliver until all applicable gates pass:

  • source file remains unchanged;
  • tracked edits are local and reviewable;
  • existing revisions/comments are preserved in tracked output;
  • clean output has revisions accepted and review comments removed as intended;
  • figures, tables, fields, equations, footnotes, and hyperlinks remain intact;
  • no unexpected characters, mojibake, missing glyphs, clipping, overlap, or broken page layout;
  • no unsupported factual, theoretical, methodological, or bibliographic additions;
  • all serious unresolved issues appear in comments or the report;
  • every delivered DOCX has been rendered and visually inspected page by page.

Stop Conditions

Stop and repair before delivery if any of the following occurs:

  • document corruption or missing package relationships;
  • lost fields, citations, figures, tables, equations, footnotes, comments, or revisions;
  • whole-paragraph redline blocks caused by routine language editing;
  • formatting drift in inserted text;
  • unexplained numerical changes;
  • unexpected CJK or mojibake in an English manuscript;
  • incomplete clean acceptance or residual comments in the clean deliverable;
  • inability to render and visually verify the final document.

If a limitation cannot be resolved, disclose it precisely and do not describe the output as fully validated.

Bundled Audit Scripts

bash
python scripts/audit_docx.py manuscript.docx --json audit_docx.json --markdown audit_docx.md
python scripts/audit_citations.py manuscript.docx --json citation_audit.json --markdown citation_audit.md
python scripts/audit_statistics.py manuscript.docx --json statistics_audit.json --markdown statistics_audit.md

These scripts are heuristic evidence-gathering tools. Verify each flagged issue in context before editing or commenting.

© mikemikeqqq, 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 39 other files (scripts, references, assets) in the repository root of mikemikeqqq/copyeditor-skill.

  • SKILL.md
  • .gitignore
  • LICENSE
  • README.en.md
  • README.md
  • agents/openai.yaml
  • assets/icon.svg
  • assets/readme/editor-comments-example.png
  • assets/readme/revision-plan-example.png
  • assets/readme/tracked-changes-example.png
  • references/academic-critical-style.md
  • references/chinese-influenced-english.md
  • references/citation-reference-review.md
  • references/citations-and-report.md
  • references/copyediting-contract.md
  • references/deliverable-packaging.md
  • references/format-preservation.md
  • … and 23 more

Open the folder on GitHubat commit df3738b

Compare with similar skills

Journal Copyeditor DOCX 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.

Journal Copyeditor DOCX compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Journal Copyeditor DOCX this skillmikemikeqqq/copyeditor-skill292—~3.9kAutomated safety check: PassMIT
Latex To Word Workflowhajimi-kun/latex-to-word-workflow128—~2.3kAutomated safety check: PassMIT
Review Papermaxwell2732/my-submission-formatting-agent111—~1.2kAutomated safety check: PassNone
De Aigc Skillsbrycewang-stanford/Auto-Empirical-Research-Skills4.6k—~5kAutomated safety check: PassCustom licence
Bibliographyaipoch/medical-research-skills1.9k—~1.6kAutomated safety check: PassMIT
Docsagentdocsagent/docsagent625—~834Automated safety check: PassNone

Similar skills

  • Latex To Word Workflow

    hajimi-kun/latex-to-word-workflow

    Load when the user asks to convert an academic LaTeX manuscript, thesis, or report into an editable Word DOCX, adapt it to a Word template, preserve citations or cross-references, or diagnose a…

    128 GitHub stars~2.3k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed
  • Review Paper

    maxwell2732/my-submission-formatting-agent

    Comprehensive manuscript review covering argument structure, methodology, citation completeness, writing quality, and potential referee objections.

    111 GitHub stars~1.2k tokensUpdated 6 mo ago
    Documents & OfficeAuto-check passed
  • De Aigc Skills

    brycewang-stanford/Auto-Empirical-Research-Skills

    中英双语学术降 AIGC / bilingual academic de-AIGC skill. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.

    4.6k GitHub stars~5k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed
  • Bibliography

    aipoch/medical-research-skills

    Classifies and organizes literature by theme, method, and conclusion; use when you need to batch-read a folder of PDF/MD/DOCX/TXT files and output a structured CSV for literature reviews and…

    1.9k GitHub stars~1.6k tokensUpdated 24 days ago
    Documents & OfficeAuto-check passed
  • Docsagent

    docsagent/docsagent

    Search and manage private, local document collections (PDF, PPTX, DOCX) offline.

    625 GitHub stars~834 tokensUpdated 13 days ago
    Documents & OfficeAuto-check passed
  • Scholar Auto Research

    joshzyj/open-scholar-skill

    Stable, deterministic social-science research-paper pipeline from idea or data to verified manuscript, citations, replication package, and final md/docx/tex/pdf outputs.

    168 GitHub stars~21k tokensUpdated 22 days ago
    Documents & OfficeAuto-check passed

Works with

Questions about Journal Copyeditor DOCX

What does Journal Copyeditor DOCX do?

Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals. Journal Copyeditor DOCX is an agent skill from mikemikeqqq/copyeditor-skill.docx) files across disciplines and target journals.

When should I use Journal Copyeditor DOCX?

Journal Copyeditor DOCX fits situations like: the user asks to proofread; prepare a manuscript with tracked changes; editor comments; A clean accepted copy.

How do I install Journal Copyeditor DOCX in Claude Code?

Run `npx skills add mikemikeqqq/copyeditor-skill --skill journal-copyeditor-docx -a claude-code`. Or copy the skill folder (the mikemikeqqq/copyeditor-skill repository) into .claude/skills/journal-copyeditor-docx in your project. Claude Code loads it when a task matches its description.

How do I install Journal Copyeditor DOCX in Codex?

Run `npx skills add mikemikeqqq/copyeditor-skill --skill journal-copyeditor-docx -a codex`. Or copy the skill folder (the mikemikeqqq/copyeditor-skill repository) into .agents/skills/journal-copyeditor-docx in your project. Codex loads it when a task matches its description.

Can I use Journal Copyeditor DOCX 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 mikemikeqqq/copyeditor-skill --skill journal-copyeditor-docx -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journal-copyeditor-docx, .gemini/skills/journal-copyeditor-docx, .github/skills/journal-copyeditor-docx and .opencode/skills/journal-copyeditor-docx in your project.

What does Journal Copyeditor DOCX need to run?

Going by SKILL.md and its folder, Journal Copyeditor DOCX needs the command-line tools its instructions call (python).

Does Journal Copyeditor DOCX 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 Journal Copyeditor DOCX 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Journal Copyeditor DOCX use?

Journal Copyeditor DOCX is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Journal Copyeditor DOCX use?

About 3.9k tokens (SKILL.md is roughly 16k 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 16k tokens, read only when the agent opens those files.

What are the alternatives to Journal Copyeditor DOCX?

Skills that share tags, products or a category with Journal Copyeditor DOCX: Latex To Word Workflow (hajimi-kun/latex-to-word-workflow, 128 stars), Review Paper (maxwell2732/my-submission-formatting-agent, 111 stars), De Aigc Skills (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Bibliography (aipoch/medical-research-skills, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Journal Copyeditor DOCX?

mikemikeqqq (a GitHub user) maintains it in mikemikeqqq/copyeditor-skill, which has 292 GitHub stars. The repository was last updated on July 23, 2026.

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