Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

thesis-docx Skill

Repository ↗

by the-shy123456★ 4841 skills

Install

What it does

写论文的skill

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Other
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/the-shy123456-thesis-docx.svg)](https://mcp.popnx.com/en/skills/the-shy123456-thesis-docx)

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
thesis-docx
llmfitclaude-videoVideoCaptionerclaude-cookbooks
Makerthe-shy123456AlexsJonesbradautomatesWEIFENG2333anthropics
Skills11114
GitHub stars48439,09621,24916,57754,867
Last code changeApr 9, 2026Nov 18, 2026Sep 25, 2026Sep 12, 2026Nov 17, 2026
LicenseMITMITMITGPL-3.0MIT

1 skills (instruction sets) by the-shy123456 that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor

Install

Is it safe?

  • Who made it

    GitHub account the-shy123456 (person), 3 years old

  • Use and upkeep

    ★ 484 stars, few users so far · code last changed Apr 9, 2026

  • Any scripts?

    5 scripts that can run on a computer: scripts/audit_docx_ooxml.py, scripts/check_word_com.ps1, scripts/export_word_pdf.ps1, scripts/normalize_word_styles.ps1 and 1 more

  • Uses the internet?

    No internet calls found in the scripts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit df5ad2e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (366). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /thesis-docx or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /thesis-docx or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the thesis-docx folder at ~/.agents/skills/thesis-docx

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick thesis-docx

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick thesis-docx

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: thesis-docx
description: Create, revise, and format thesis or dissertation Word documents with strict academic formatting control. Use when an AI agent needs to generate or revise thesis content, normalize Word styles, follow a school template, fix captions or page numbers or section levels, or produce evidence-based Mermaid figures and LaTeX-formatted code listings for a thesis document.
---

# Thesis DOCX

## Overview

Use this skill for thesis-oriented `.docx` work where content quality and
format fidelity both matter. Prefer Microsoft Word desktop automation over
WPS-like alternatives whenever the task involves batch formatting, styles,
captions, pagination, tables of contents, or cross-references.

This skill is designed to avoid the most common thesis-editing failure mode:
the agent makes broad formatting changes too early, introduces new layout
problems, and then forces the user to catch them one by one. The default
behavior should therefore be:

1. audit first,
2. separate explicit school requirements from unspecified formatting,
3. fix only what is justified,
4. re-check page by page before claiming completion.

## Workflow

1. Check Microsoft Word and COM/DOM automation first.
   - On Windows, run:
   ```powershell
   powershell -ExecutionPolicy Bypass -File scripts/check_word_com.ps1 -Json
   ```
   - If Word is missing, COM is unavailable, or DOM access fails:
     - Stop the automation-heavy plan.
     - Tell the user to install desktop Microsoft Word.
     - Explain briefly that WPS or similar tools are likely to degrade layout
       fidelity for thesis formatting.
2. Read the user's real constraints before editing.
   - Collect the thesis template, school formatting guide, screenshots,
     existing document, sample pages, and any explicit chapter rules.
   - If the user gave formal requirements, follow them strictly.
   - If the user did not give requirements, do not invent school-specific
     standards. Use conservative academic defaults and say that they are
     defaults.
   - Explicitly classify requirements into two buckets before editing:
     - `must enforce`: school guide, template, user-confirmed style rules
     - `preserve current state`: anything the school guide does not define
3. Audit the DOCX / OOXML before risky bulk edits.
   - Prefer `scripts/audit_docx_ooxml.py` before large-scale formatting.
   - Use it to detect hidden indentation, section drift, stale REF display
     text, and style-ID mismatches before deciding on a repair strategy.
4. Standardize with styles, not scattered direct formatting.
   - Reuse and repair existing styles whenever possible.
   - Create missing styles only when no matching style exists.
   - Keep body text, headings, figure captions, table captions, references,
     abstract, and appendix styles separate and consistent.
   - Before changing any style globally, inspect whether the document contains
     direct paragraph formatting or OOXML overrides that will survive the style
     change.
5. Edit content only from user-provided facts.
   - Expand, polish, or reorganize thesis text only within the user's topic,
     evidence, codebase, notes, or source material.
   - Do not invent experimental data, system structure, entities, or results.
   - Do not expose agent reasoning or data-feeding context inside the thesis
     prose. Forbidden patterns include thesis-language such as:
     - "根据已有工程"
     - "根据现有代码"
     - "将任务书和代码喂给模型后"
     - "通过分析用户提供的代码"
     - any wording that sounds like an AI workflow note instead of thesis prose
   - Write in normal thesis voice, not in prompt-engineering voice, review
     voice, or chain-of-thought voice.
   - Prefer neutral academic narration that reads like student writing, e.g.
     "本文设计并实现了……", "系统采用了……", "在该模块中……"
   - Avoid first-order meta-explanations about how the text was generated,
     inferred, or assembled.
6. Generate figures only when the source material is sufficient.
   - Use Mermaid for architecture diagrams, E-R diagrams, flow charts, state
     diagrams, and similar thesis figures.
   - Base every node, field, relation, and dependency on real materials from
     the user, such as code, SQL schema, API docs, project docs, or the thesis
     draft itself.
   - If the materials are insufficient, refuse to fabricate the figure and ask
     for the missing source information.
7. Typeset code with LaTeX conventions when thesis code excerpts are needed.
   - Keep only the code relevant to the argument.
   - Preserve real identifiers from the user's code or design.
   - Avoid synthetic filler code written only to look complete.
8. Audit before you claim completion.
   - Run a structure audit first: styles, sections, captions, references,
     page number scheme, cross-references, hidden paragraph overrides.
   - Then export the document to PDF from Word and review page by page.
   - Only say the task is complete after the PDF-level audit passes or after
     you clearly state the remaining manual visual checks.

## Style Strategy

- Treat styles as the single source of truth for formatting.
- Prefer these logical style buckets:
  - `Body Text`
  - `Heading 1` / `Heading 2` / `Heading 3`
  - `Figure Caption`
  - `Table Caption`
  - `References`
  - `Abstract`
  - `Keywords`
  - `Appendix Title`
- If the document already has equivalent styles, map to them and normalize
  their font, spacing, indentation, and numbering behavior.
- If direct formatting conflicts with styles, reduce the direct formatting and
  bring the document back under style control.
- Do not globally normalize sections that the school guide does not specify.
  Examples of high-risk overreach:
  - page header/footer redesign when the user only asked for headings
  - changing code box appearance when the task is only about references
  - normalizing table internals when the school guide does not regulate them
- When a visual issue remains after style normalization, inspect hidden OOXML
  state such as `firstLineChars`, numbering indentation, `titlePg`,
  `differentFirstPageHeaderFooter`, REF field display text, and direct run
  formatting.

## Audit-First Discipline

Before bulk editing, produce and internally follow a checklist like this:

1. Which parts are explicitly regulated by the school guide?
2. Which parts are user-defined house rules?
3. Which parts are currently acceptable and must be preserved?
4. Which problems are structural vs. visual-only?
5. Which fixes can be done safely through styles?
6. Which fixes require Word COM or OOXML-level patching?

Do not say "finished" merely because a structural audit looks good. For thesis
work, pagination and page-level rendering are part of correctness.

## High-Risk Pitfalls

Read `references/failure-patterns-and-quality-gates.md` before large-scale
formatting work. In particular, guard against:

- style names that look correct but map to the wrong style IDs
- paragraph-level direct formatting that overrides the intended style
- `firstLineChars` or numbering indentation creating invisible extra indents
- TOC fields or cross-reference fields showing stale display text
- section-level first-page settings causing missing headers or page numbers
- Word vs. WPS differences for table row height, vertical alignment, and code
  box title clipping
- punctuation normalization that accidentally rewrites DOI, URLs, code, or
  English references

## Visual Review Rule

For school-format-sensitive thesis work, final verification should prefer this
order:

1. Word COM/DOM structural checks
2. Word export to PDF
3. page-by-page PDF review
4. only then final delivery language

If page rendering cannot be verified, say so explicitly instead of implying the
 formatting is fully validated.

## Figure Rules

- Use Mermaid when a thesis figure is needed and the structure can be traced to
  real source material.
- Keep the diagram academically neutral and concise.
- Avoid decorative labels, chatty callouts, and speculative entitie

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
484
Maker
the-shy123456
License
MIT
Last code change
Apr 9, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
skill, thesis