メニュー
Create, edit, and compile LaTeX documents. Use when working with .tex files, fixing LaTeX compilation errors, or preparing TeX sources for reliable builds, including Scientific WorkPlace (SWP) compatibility issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when working on Alessandro's Windows machine through Codex, especially for PowerShell vs cmd.exe behavior, PATH refreshes, quoted Program Files paths, sandbox escalation, local command-line tools, Git/GitHub CLI, or Windows-specific setup quirks.
Proofread, analyze, and safely modify Microsoft Word .docx documents, especially academic reflective writing, application forms, assignments, and templates with section word or character limits. Use when Codex needs to extract Word document text, read surrounding instruction files for context, count words by section, check author-date references against in-text citations, verify that cited references exist, produce a proofread copy, or apply paragraph-level edits while preserving the original document.
Draft referee reports for economics and closely related academic papers from PDF manuscripts. Use when Codex needs to read a paper PDF, extract text with pdfplumber, optionally normalize extracted notes with pandoc, and produce a referee report with three sections: (1) overview and overall assessment, (2) major comments, and (3) minor comments.
Create, edit, review, build, and debug modern Fortran code and projects. Use when Codex needs to work with `.f90`, `.f95`, `.f03`, `.f08`, `.F90`, Makefiles or build scripts for Fortran, especially when the preferred compiler is Intel `ifx` from oneAPI on Windows, and when code should follow modern Fortran best practices from Fortran-lang.
Use only for MATLAB code involving GPU-specific constructs or GPU execution, such as gpuArray, arrayfun on GPU, GPU vectorization, GPU memory use, or value function iteration intended to run on the GPU. For ordinary CPU MATLAB .m editing, use the matlab skill instead.
Use for all MATLAB .m editing, review, debugging, refactoring, and CPU performance work. This is the default MATLAB skill for scripts, functions, numerical workflows, interpolation, search, optimization, and value function iteration unless the user specifically needs GPU constructs such as gpuArray or arrayfun on GPU; in that case also use matlab-gpu.
| name | latex |
| description | Create, edit, and compile LaTeX documents. Use when working with .tex files, fixing LaTeX compilation errors, or preparing TeX sources for reliable builds, including Scientific WorkPlace (SWP) compatibility issues. |
Produce compilable LaTeX sources and resolve common build failures quickly.
On Windows, pdflatex is expected to be available on PATH through MiKTeX or another TeX distribution. Use this discovery order only if pdflatex is not resolving in the current shell:
pdflatex on PATH.Get-Command pdflatex -ErrorAction SilentlyContinue or where.exe pdflatex.%LOCALAPPDATA%\Programs\MiKTeX\miktex\bin\x64, %LOCALAPPDATA%\MiKTeX\miktex\bin\x64, and %APPDATA%\MiKTeX\miktex\bin\x64.pdflatex.exe path immediately for the current build, quoting it when needed.Use pdftotext for lightweight PDF text checks before falling back to Python PDF libraries.
Prefer the real Poppler pdftotext.exe installed under C:\Program Files\Poppler\...\Library\bin when available. Do not create or rely on a pdftotext.cmd shim.
Use this discovery order if pdftotext is needed:
pdftotext on PATH.Get-Command pdftotext -ErrorAction SilentlyContinue and where.exe pdftotext.C:\Program Files\Git\mingw64\bin\pdftotext.exe can be used only as a diagnostic or temporary fallback, not as the preferred permanent setup.Do not say that the local shell does not expose pdftotext until checking the preferred Program Files Poppler path.
\input{tcilatex} before every compilation.% \input{tcilatex} unless the user explicitly requires SWP-only compatibility.\documentclass{beamer}).Scientific WorkPlace (SWP) may inject \input{tcilatex}. In standard LaTeX environments this often fails because tcilatex.tex is not available. Default action: comment out that line, then compile.
If the user is building from VS Code LaTeX Workshop and the build fails through latexmk with a message about missing perl or a missing script engine, treat that as an editor recipe problem rather than a TeX-source problem. Prefer a workspace-level LaTeX Workshop recipe that uses pdflatex directly instead of latexmk, especially when pdflatex works but latexmk depends on a Perl engine that is not installed.