agentsclimarketplace
Sign in

Remote latex setup

Skill InvisCat/remote-latexmk/.agents/skills/remote-latex-setup

Connect a remote-latexmk client or coding-agent Plugin to an existing private server. Use for first login, server URL or token changes, private CA configuration, or auth login and doctor errors. Do not use for server installation, paper compilation, or storage cleanup.From its SKILL.md

Install
npx -y skills add InvisCat/remote-latexmk --skill remote-latex-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

Connect Remote LaTeX

Use the remote-latexmk client command named rlatexmk. Do not invoke the unrelated TeX Live latexmk command.

Never ask the user to paste a token into the Agent. Never write credentials to .latexmk.json, the paper workspace, shell history, or command arguments.

Workflow

  1. If a saved login exists, run rlatexmk doctor. It checks service health and identity, protocol compatibility, configured authentication, and local project-cache Git policy.
  2. If login is missing or the server changed, ask only for the server address. Tell the user to run rlatexmk auth login --server SERVER themselves in a trusted interactive terminal. A bare host and an explicit http:// URL without a port use HTTP port 8080. An https:// URL without a port uses the standard HTTPS port. Explicit schemes and ports are preserved.
  3. Explain the order of auth login: it normalizes the address, checks public health, service identity, and protocol compatibility, and only then opens the hidden remote-latexmk API-token prompt. It verifies authenticated read access before saving the login. A failure does not replace the saved login.
  4. If login fails, ask for the exact error text but never the token. Read references/login-errors.md and give the narrow matching correction. Do not weaken TLS, authentication, network policy, or path boundaries.
  5. After a successful login, run rlatexmk doctor once to check the remaining local policy. Do not ask for more connection details when it succeeds.

For an existing user-managed token file or private CA, preview the non-secret configuration before applying it:

rlatexmk setup --json --server SERVER_URL --token-file TOKEN_FILE
rlatexmk setup --yes --json --server SERVER_URL --token-file TOKEN_FILE

Add the same --ca-file CA_FILE to both commands when a private CA is needed. Do not read, print, summarize, copy, or edit the token or CA file. Show the resolved non-secret paths and ask for explicit confirmation before apply.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.