agentleFS
letsloose501letsloose501/sqs-agent-memory/skills/latex/SKILL.md

latex

Skill2 starsChanged 9 days agoApache-2.0View on GitHub

Produces compilable LaTeX for formulas, theorems, proofs, derivations, algorithms, tables, TikZ plots and structured academic text on any technical topic, not one narrow field. Use on "write the theorem and proof", "make Beamer slides / a presentation", "derive the formula", "typeset this", "a .tex file". Three modes: Document (a full .tex), Snippet (one formula / table / algorithm), Beamer (slides). For Beamer, trigger whenever the words slides, presentation, beamer or talk appear.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    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
  1. Distinctive:

    Check Beamer first: it has the clearest signals.

    line 19
  2. Very specific:

    Only a title or theses: build the full skeleton with \todo{} in the empty places.

    line 27
  3. Distinctive:

    Never invent theorems, lemmas or numerical results that were not given.

    line 28
  4. Very specific:

    Every \begin{} is closed by \end{}.

    line 54
  5. Very specific:

    No proof given by the user: do not invent one.

    line 56
  6. Distinctive:

    If a TeX distribution is installed, compile and read the log before delivering.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LaTeX: formulas, theorems, proofs, slides

Compilable LaTeX for mathematically dense text on any subject. Open the references by mode; do not keep everything in your head.

Step 1. Pick the mode

Check Beamer first: it has the clearest signals.

Beamer Mode: the words slides, presentation, beamer, talk, slide deck, a request to prepare a talk from a paper or draft, "title slide" and similar section names. Use references/preamble.md (Beamer part) and references/beamer.md. Do not use the Document Mode preamble or structure.

  • A finished manuscript or paper exists: move its content onto slides exactly, without distortion.
  • Only a title or theses: build the full skeleton with \todo{} in the empty places.
  • Never invent theorems, lemmas or numerical results that were not given.

Document Mode: a theorem / lemma / proposition / corollary / definition (with or without a proof), a multi-step derivation, a convergence analysis, an algorithm with justification, an introduction or literature review, a self-contained report or preprint. Deliver a full .tex file.

Snippet Mode: one formula or system of formulas, an algorithm or pseudocode alone, a results table, a TikZ/pgfplots plot, any fragment to paste into someone else's template. Only the body (no \documentclass, no preamble), in the chat as a code block, not a file (unless a file was asked for).

Unsure which mode: one question, "the whole document, a fragment, or slides?".

References by step

NeedOpen
Document Mode preamble (packages, theorem environments, notation macros)references/preamble.md
Beamer preamble, theme, color schemereferences/preamble.md (Beamer part)
Slide content: sections, citation footnotes, theorems on a slide, algorithms, results tables, frame rules, the full template, the checklistreferences/beamer.md
Theorems and proofs, formula style, notation, algorithms (algorithm2e), results tables, TikZ/pgfplotsreferences/math-standards.md
Document structure by type (theorem/proof, convergence analysis, derivation, literature review), bibliography (own list / BibTeX+natbib / BibLaTeX+Biber)references/document-structure.md
Phrases to avoid, the pre-delivery checklist, what to do with an incomplete requestreferences/writing-quality.md
The full Document Mode templatereferences/templates.md

Required before delivery

  • Every \begin{} is closed by \end{}; every numbered environment has a \label{}; every \ref{} / \eqref{} / \cref{} resolves. The detailed checklist: references/writing-quality.md.
  • No proof given by the user: do not invent one; put \begin{proof} with a \todo{} plan instead of a finished argument.
  • Author, institution, talk topic not given: put \todo{} or ask; never copy the sample data from the references.
  • If a TeX distribution is installed, compile and read the log before delivering; if it is not, say the file was not compiled.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.