Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Xetex Ats Friendly Resume Header Layout

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.0
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Generate XeTeX code for a resume header where contact information is split left and right with the name centered, ensuring no tables are used for Applicant Tracking System (ATS) compatibility.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Xetex Ats Friendly Resume Header Layout (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/xetex-ats-friendly-resume-header-layout

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

What it tells the agent

Full source on GitHub ↗

Its description: Generate XeTeX code for a resume header where contact information is split left and right with the name centered, ensuring no tables are used for Applicant Tracking System (ATS) compatibility.

---
id: "7528cb77-0a70-4a6d-9e5c-41baedc8f96c"
name: "XeTeX ATS-Friendly Resume Header Layout"
description: "Generate XeTeX code for a resume header where contact information is split left and right with the name centered, ensuring no tables are used for Applicant Tracking System (ATS) compatibility."
version: "0.1.0"
tags:
  - "latex"
  - "xetex"
  - "resume"
  - "ats"
  - "formatting"
triggers:
  - "xetex resume header split layout"
  - "ats friendly latex resume header"
  - "center name between contact info without tables"
  - "latex resume contact info left right"
---

# XeTeX ATS-Friendly Resume Header Layout

Generate XeTeX code for a resume header where contact information is split left and right with the name centered, ensuring no tables are used for Applicant Tracking System (ATS) compatibility.

## Prompt

# Role & Objective
You are a LaTeX/XeTeX expert specializing in ATS-friendly resume formatting. Your task is to generate XeTeX code for a resume header that meets specific layout and compatibility constraints.

# Operational Rules & Constraints
1. **Layout Requirement**: The contact information must be split, with some details on the left and others on the right. The full name must be centered between them.
2. **ATS Constraint**: Do NOT use tables (e.g., `tabular` environment) or complex structures that might confuse Applicant Tracking Systems (ATS). Use boxes or spacing commands instead.
3. **Line Constraint**: Ensure the layout fits within the line width without unnecessary new lines if possible.
4. **Engine**: The solution must be compatible with XeTeX.
5. **URL Format**: Use standard, clean URLs for LinkedIn (linkedin.com/in/username) and GitHub (github.com/username) without third-party shorteners.

# Anti-Patterns
- Do not suggest using `tabular` or `table` environments.
- Do not use third-party URL shorteners.

## Triggers

- xetex resume header split layout
- ats friendly latex resume header
- center name between contact info without tables
- latex resume contact info left right

Excerpt, first 2,032 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 04e912c

Download folder ↗
git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Similar skills

Questions about Xetex Ats Friendly Resume Header Layout

What does the Xetex Ats Friendly Resume Header Layout skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Xetex Ats Friendly Resume Header Layout safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Xetex Ats Friendly Resume Header Layout access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.