Latex Writing

Enforces semantic LaTeX markup so your documents mean what they say, not just look right. Catches the classic antipattern of bold labels in itemize lists and pushes you toward proper description environments. Also handles cleveref for cross-references and csquotes for quotations. The real win is the literate programming support: in .nw files it enforces noweb's double-bracket notation for code identifiers instead of manually escaping underscores in texttt. Saves you from a lot of tedious backslashing and makes the source readable. Activates automatically when you're editing .tex or .nw files, or when you mention LaTeX tooling like BibTeX or PythonTeX.

skills.sh installs: 344
GitHub stars: 1
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dbosk/claude-skills --skill latex-writing --agent claude-code

Installs into .claude/skills of the current project.

Files

LaTeX Writing Best Practices

This skill guides the creation of well-structured, semantically correct LaTeX documents following established best practices.

Core Principle: Semantic Markup

Use LaTeX environments that match the semantic meaning of the content, not just the visual appearance.

List Environments: When to Use What

Use `description` for Term-Definition Pairs

When you have labels followed by explanations, definitions, or descriptions, use the description environment:

\begin{description}
\item[Term] Definition or explanation of the term
\item[Label] Content associated with the label
\item[Property] Description of the property
\end{description}

NEVER do this:

\begin{itemize}
\item \textbf{Term:} Definition or explanation
\item \textbf{Label:} Content associated with label
\end{itemize}

Common Use Cases for `description`

SKILL.md on GitHub

Details

Repository: github.com/dbosk/claude-skills
Categories: Documentation, Code Review & Quality
First seen: Jun 3, 2026