agentleFS
clearsmogclearsmog/claude-skills/compile/SKILL.md

compile

Skill2 starsChanged 9 months agoMITView on GitHub

Compile any supported file type. Detects format (.typ, .qmd, .py) and runs appropriate build command.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use expert-reset, updates and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jtenniswoodSkill

    expert-reset

    Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.

    Also in 3 projects that use this

  • jtenniswoodSkill

    updates

    Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.

    Also in 3 projects that use this

  • MicrosoftSkill

    pr-review

    Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --root if the file imports packages from a parent directory

    line 30
  2. Distinctive:

    Check exit code for compilation errors

    line 31
  3. Distinctive:

    Verify output files were created (if applicable)

    line 49
  4. Very specific:

    Use Read tool on PNGs to visually inspect for overflow, blank pages, missing figures

    line 64

“Common” is measured: kept by at least 6 in 10 of the 9 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

Compile Document

Detect file format and run the appropriate build command.

Format Detection

Determine file type from extension:

  • .typ → Typst document
  • .qmd → Quarto slides
  • .py → Python script

Note: For .tex (LaTeX/Beamer), configure compilation at project level with project-specific TEXINPUTS and bibtex paths.

Compilation Commands

For .typ files (Typst):

typst compile [--root ..] FILENAME.typ
  • Use --root if the file imports packages from a parent directory
  • Check exit code for compilation errors
  • Typst compilation is single-pass (no multi-pass needed)

For .qmd files (Quarto):

quarto render FILENAME.qmd
  • Or use project-specific deploy script if available

For .py files (Python):

uv run FILENAME.py
  • Check exit code
  • Verify output files were created (if applicable)

Post-Compilation Checks

  1. Check for warnings:
    • .typ: Check stderr for warnings
    • .qmd: Check for render warnings
    • .py: Check for tracebacks or warnings
  2. Verify output exists and has non-zero file size
  3. Visual spot-check (.typ files only):
    • Render sample pages to PNG: typst compile FILE.typ /tmp/preview-{0p}.png
    • For documents (>3 pages): render pages 1, middle, and last
    • For presentations: render all slides
    • Use Read tool on PNGs to visually inspect for overflow, blank pages, missing figures
    • See typst/references/visual-verification.md for full checklist
  4. Report results:
    • Compilation success/failure
    • Warning count
    • Output file path and size
    • Visual check: PASS / issues noted

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.