latex-workshop
Skill4 starsChanged 4 months agoMITView on GitHub
Use when compiling or troubleshooting a LaTeX document inside a VS Code project whose build is governed by LaTeX Workshop. Do not use for LaTeX compilation outside a VS Code project.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- daidaibunny/agent-skillstheir own version, first seen May 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- daidaibunny/agent-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bib-auditSkill
- bootstrap-dispatcher-runtimeSkill
- ci-debugSkill
- cloud-filesSkill
- connect-googleSkill
- daily-planSkill
- distill-to-ruttersSkill
- email-clientSkill
- email-triageSkill
- find-handoff-candidatesSkill
- formal-prose-reviewSkill
- get-weatherSkill
- git-workflowSkill
- hook-makerSkill
- initialize-tddSkill
- install-launchersSkill
- list-managerSkill
- llm-wakeupSkill
- loose-modeSkill
- make-tex-docstringSkill
- math-dependency-graphSkill
- milestone-loggingSkill
- node-certifySkill
- node-driftSkill
- notation-reviewSkill
- online-calendarSkill
- pdf-to-markdownSkill
- prepare-handoffSkill
- proof-auditSkill
- recurring-tasksSkill
- refactor-nodeSkill
- regenerate-blueprintsSkill
- relocate-nodesSkill
- semantic-integrationSkill
- send-feedbackSkill
- setup-interface-managerSkill
- skill-makerSkill
- technical-flow-reviewSkill
- tight-modeSkill
- tool-applicabilitySkill
- update-standardsSkill
- using-compassSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Do not assume that outputs belong beside the source file, that latexmk is the intended tool, or that _build is the correct outdir unless …
- Distinctive: line 26
Check workspace-level config first:
- Distinctive: line 29
Look for relevant LaTeX Workshop settings, especially:
- Distinctive: line 33
If no workspace-level override exists, check user-level VS Code settings:
- Very specific: line 38
If the outdir contains %DIR%, resolve it relative to the directory of the target .tex file.
- Distinctive: line 42
Prefer the configured recipe/tool behavior when it is readable from settings.
- Very specific: line 43
If no recipe/tool information is available, use the effective outdir setting and a conservative latexmk fallback.
- Distinctive: line 45
If there is a repo script or Makefile that clearly matches the configured LaTeX Workshop workflow, it is fine to use that instead.
- Distinctive: line 58
Read artifacts from the effective output location.
- Distinctive: line 62
If an earlier compile was run in the wrong location, say so plainly and switch to the configured location for later runs.
- Distinctive: line 68
If fallback behavior was used because LaTeX Workshop settings were incomplete, say exactly what was missing.
- Distinctive: line 87
Treat user mentions of VS Code or LaTeX Workshop as a signal to inspect these settings before compiling.
- Distinctive: line 89
Prefer matching LaTeX Workshop behavior over ad hoc shell habits.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- BEGIN BLUEPRINT INTERFACES -->Generated from
blueprint.yaml. Do not edit this block by hand.
Used Interfaces: none
<!-- END BLUEPRINT INTERFACES -->Skill: latex-workshop
Goal
Behave the way VS Code LaTeX Workshop is configured to behave for the target LaTeX document.
Do not assume that outputs belong beside the source file, that latexmk is the
intended tool, or that _build is the correct outdir unless the effective
LaTeX Workshop configuration implies that.
Workflow
- Resolve the effective LaTeX Workshop configuration.
- Check workspace-level config first:
.vscode/settings.json- any
*.code-workspacefile in the repo
- Look for relevant LaTeX Workshop settings, especially:
latex-workshop.latex.outDirlatex-workshop.latex.recipeslatex-workshop.latex.tools
- If no workspace-level override exists, check user-level VS Code settings:
- Linux:
~/.config/Code/User/settings.json - macOS:
~/Library/Application Support/Code/User/settings.json - Windows:
%APPDATA%\\Code\\User\\settings.json
- Linux:
- Workspace-level config overrides user-level config.
- If the outdir contains
%DIR%, resolve it relative to the directory of the target.texfile.
- Reconstruct the LaTeX Workshop build behavior.
- Prefer the configured recipe/tool behavior when it is readable from settings.
- If no recipe/tool information is available, use the effective outdir setting
and a conservative
latexmkfallback. - If there is a repo script or Makefile that clearly matches the configured LaTeX Workshop workflow, it is fine to use that instead.
- Compile with the effective behavior.
- Typical fallback when an outdir is configured:
latexmk -pdf -outdir="<resolved-outdir>" -interaction=nonstopmode -halt-on-error "<file>.tex"- Typical fallback when no outdir is configured:
latexmk -pdf -interaction=nonstopmode -halt-on-error "<file>.tex"- Read artifacts from the effective output location.
- Inspect logs, PDFs, and bibliography artifacts in the resolved output directory, not next to the source file unless the effective config implies that.
- If an earlier compile was run in the wrong location, say so plainly and switch to the configured location for later runs.
- Report the source of truth.
- State whether the effective behavior came from workspace config, user config, or a fallback.
- If fallback behavior was used because LaTeX Workshop settings were incomplete, say exactly what was missing.
Retrieval Commands
- Workspace-level search:
rg -n 'latex-workshop\\.latex\\.(outDir|recipes|tools)' .vscode *.code-workspace- User-level search on Linux:
rg -n 'latex-workshop\\.latex\\.(outDir|recipes|tools)' ~/.config/Code/User/settings.jsonNotes
- There is usually no direct terminal command that means "invoke LaTeX Workshop itself." In practice, use the discovered LaTeX Workshop settings to reconstruct the intended build behavior.
- Treat user mentions of VS Code or LaTeX Workshop as a signal to inspect these settings before compiling.
- Prefer matching LaTeX Workshop behavior over ad hoc shell habits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.