What it does
写论文的skill
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Otros
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/the-shy123456-thesis-docx)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este thesis-docx | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| Autor | the-shy123456 | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skills | 1 | 1 | 1 | 1 | 4 |
| Estrellas de GitHub | 484 | 39.096 | 21.249 | 16.577 | 54.867 |
| Último cambio de código | 9 abr 2026 | 18 nov 2026 | 25 sept 2026 | 12 sept 2026 | 17 nov 2026 |
| Licencia | MIT | MIT | MIT | GPL-3.0 | MIT |
1 skills (conjuntos de instrucciones) de the-shy123456 que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
El autor no lo indica · los skills con SKILL.md funcionan en apps compatibles con Agent Skills, como Claude Code, Codex y Cursor
Instalar
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 9 abr 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
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 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de Claude Code
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
Vuelve a abrir Claude Code y escribe /thesis-docx, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Vuelve a abrir Claude Code y escribe /thesis-docx, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
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 2Coloca la carpeta tú mismo
Coloca la carpeta thesis-docx en ~/.agents/skills/thesis-docx
~ es tu carpeta de inicio ($HOME)
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Vuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de Cursor
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
En el chat Agent de Cursor escribe / y elige thesis-docx
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
En el chat Agent de Cursor escribe / y elige thesis-docx
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en 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 entitieConversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 484
- Autor
- the-shy123456
- Licencia
- MIT
- Último cambio de código
- 9 abr 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1
- Temas
- skill, thesis