Claude Cursor Skill

export

Convert thesis chapters and reading notes from Markdown to Word (.docx) and package for submission. Use when preparing materials for supervisors or examiners.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download yha9806-academic-writing-toolkit-.claude_skills_export-184e482.zip · 7 KB

Install

skills CLI npx skills add https://github.com/yha9806/academic-writing-toolkit/tree/main/.claude/skills/export
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install yha9806-academic-writing-toolkit@llmmart
Git git clone https://github.com/yha9806/academic-writing-toolkit.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole yha9806/academic-writing-toolkit collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/export — Document Export Skill

Running Python helpers

Choose the interpreter before running the examples. For a globally installed copy, use the private runtime recorded by its installer. In a checkout or linked workspace, use AWT_PYTHON when set, otherwise the toolkit's .venv (follow the skill directory link back to the toolkit): Scripts/python.exe on Windows, bin/python on macOS/Linux. Without that environment, check that python (Windows) or python3 (macOS/Linux) actually runs and has the helper's dependencies. Replace the example's python3 with that executable. In PowerShell, prefix a quoted executable with &; keep commands on one line and quote file paths.

Purpose

Convert thesis chapters and reading notes from Markdown to Word (.docx) format and package them into a ZIP archive for submission to supervisors or examiners. This skill is user-invoked only and will not be triggered automatically.

Trigger Words

This skill activates on: /export. It is never invoked automatically by the model.

Parameters

  • $ARGUMENTS[0] -- scope: chapters | notes | all (default: all)
  • $ARGUMENTS[1] -- language filter: en-only | all (default: all)

Examples:

  • /export chapters en-only -- export only chapter files, skip files with significant CJK content
  • /export notes all -- export only reading notes, include all languages
  • /export -- export everything, all languages

Workflow

  1. Resolve every source first (Advisory here; Enforced in the AWT app). Before converting, confirm that every author-year citation in chapters/ has a lint-conforming notes file under literature/reading_notes/, and that references.bib (when present) neither contains entries nothing cites nor lacks an entry a chapter cites:

    python3 .claude/skills/audit/scripts/audit-claim-positioning.py --base-dir chapters --bib references.bib --json
    

    Stop and report if anything is unresolved. On this surface nothing blocks you from exporting anyway — say so if you do. In the AWT app the same condition is a typed denial (EXPORT_SOURCES_UNRESOLVED) on the export_docx tool, and the export does not run.

  2. Check dependencies. Verify that pypandoc is installed AND a working pandoc binary is on PATH (the script smoke-probes via pypandoc.get_pandoc_version()). If pypandoc/pandoc are unavailable, fall back to python-docx + markdown. Report which conversion method is being used.

    Run from the project root.

  3. Run the conversion script.

    python3 .claude/skills/export/scripts/convert_to_docx.py --base-dir "{project_root}" --output-dir "{project_root}/final_output" --scope {scope} --lang-filter {lang_filter}
    
  4. Report results.

    ## Export Complete
    
    | Item | Value |
    |------|-------|
    | Files converted | {N} |
    | Files skipped (language filter) | {N} |
    | Output directory | {path} |
    | ZIP archive | {path} |
    | Total size | {size} |
    
    Conversion method: {pandoc | python-docx fallback}
    

Constraints

  1. User-invoked only. This skill has disable-model-invocation: true and must not run unless the user explicitly calls /export.
  2. No hardcoded paths. All paths are derived from arguments or project root.
  3. No emoji in output.
  4. Preserve formatting as much as possible during conversion -- headings, tables, block quotes, inline code.
Files (academic-writing-toolkit)
  • scripts
    • convert_to_docx.py 16 KB
      Loading…
    • requirements.txt 1 KB
      Loading…
  • SKILL.md 3.6 KB
    ---
    name: export
    description: Convert thesis chapters and reading notes from Markdown to Word (.docx) and package for submission. Use when preparing materials for supervisors or examiners.
    disable-model-invocation: true
    allowed-tools: Bash, Read, Glob, Write
    ---
    
    # /export — Document Export Skill
    
    ## Running Python helpers
    
    Choose the interpreter before running the examples. For a globally installed
    copy, use the private runtime recorded by its installer. In a checkout or linked
    workspace, use `AWT_PYTHON` when set, otherwise the toolkit's `.venv` (follow the
    skill directory link back to the toolkit): `Scripts/python.exe` on Windows,
    `bin/python` on macOS/Linux. Without that environment, check that `python`
    (Windows) or `python3` (macOS/Linux) actually runs and has the helper's dependencies.
    Replace the example's `python3` with that executable. In PowerShell, prefix a
    quoted executable with `&`; keep commands on one line and quote file paths.
    
    ## Purpose
    
    Convert thesis chapters and reading notes from Markdown to Word (.docx) format and package them into a ZIP archive for submission to supervisors or examiners. This skill is user-invoked only and will not be triggered automatically.
    
    ## Trigger Words
    
    This skill activates on: `/export`. It is never invoked automatically by the model.
    
    ## Parameters
    
    - `$ARGUMENTS[0]` -- **scope**: `chapters` | `notes` | `all` (default: `all`)
    - `$ARGUMENTS[1]` -- **language filter**: `en-only` | `all` (default: `all`)
    
    Examples:
    - `/export chapters en-only` -- export only chapter files, skip files with significant CJK content
    - `/export notes all` -- export only reading notes, include all languages
    - `/export` -- export everything, all languages
    
    ## Workflow
    
    0. **Resolve every source first (Advisory here; Enforced in the AWT app).**
       Before converting, confirm that every author-year citation in `chapters/`
       has a lint-conforming notes file under `literature/reading_notes/`, and
       that `references.bib` (when present) neither contains entries nothing
       cites nor lacks an entry a chapter cites:
    
       ```
       python3 .claude/skills/audit/scripts/audit-claim-positioning.py --base-dir chapters --bib references.bib --json
       ```
    
       Stop and report if anything is unresolved. On this surface nothing blocks
       you from exporting anyway — say so if you do. In the AWT app the same
       condition is a typed denial (`EXPORT_SOURCES_UNRESOLVED`) on the
       `export_docx` tool, and the export does not run.
    
    1. **Check dependencies.** Verify that `pypandoc` is installed AND a working `pandoc` binary is on PATH (the script smoke-probes via `pypandoc.get_pandoc_version()`). If pypandoc/pandoc are unavailable, fall back to `python-docx` + `markdown`. Report which conversion method is being used.
    
       **Run from the project root.**
    
    2. **Run the conversion script.**
       ```
       python3 .claude/skills/export/scripts/convert_to_docx.py --base-dir "{project_root}" --output-dir "{project_root}/final_output" --scope {scope} --lang-filter {lang_filter}
       ```
    
    3. **Report results.**
       ```
       ## Export Complete
    
       | Item | Value |
       |------|-------|
       | Files converted | {N} |
       | Files skipped (language filter) | {N} |
       | Output directory | {path} |
       | ZIP archive | {path} |
       | Total size | {size} |
    
       Conversion method: {pandoc | python-docx fallback}
       ```
    
    ## Constraints
    
    1. **User-invoked only.** This skill has `disable-model-invocation: true` and must not run unless the user explicitly calls `/export`.
    2. **No hardcoded paths.** All paths are derived from arguments or project root.
    3. **No emoji** in output.
    4. **Preserve formatting** as much as possible during conversion -- headings, tables, block quotes, inline code.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.