agentleFS
wp225wp225/ai-job-assist/.claude/skills/verify-application-docs/SKILL.md

verify-application-docs

Skill0 starsChanged 3 months agoMITView on GitHub

Verify, compile, and inspect tailored LaTeX resumes and cover letters for factual accuracy, requirement coverage, visual layout, and ATS text extraction.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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 both documents for:

    line 24
  2. Distinctive:

    If compilation fails, report the error and revise only the minimum necessary LaTeX source.

    line 46
  3. Distinctive:

    no section heading, role title, or education title is orphaned at a page break.

    line 60
  4. Distinctive:

    no clipped text, broken links, overflow, or excessive whitespace.

    line 61
  5. Very specific:

    If pdftotext is available, run:

    line 67
  6. Very specific:

    Delete resume.txt after checking it.

    line 81
  7. Very specific:

    If pdftotext is unavailable, report that ATS text extraction was skipped and complete visual keyword checks instead.

    line 83
  8. Distinctive:

    Do not mark documents ready until every required check passes.

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Verify Application Documents

Goal

Validate the tailored resume and cover letter before /apply reports the application materials as ready.

Step 1: Load Sources

Read:

  • data/candidate-profile/candidate-profile.md
  • data/job-evaluations/<company>--<role>.md
  • documents/cv_resume/<company>/<role>/resume.tex
  • documents/cv_resume/<company>/<role>/cover-letter.tex

Step 2: Verify Content

Check both documents for:

  • unsupported or exaggerated candidate claims;
  • incorrect dates, titles, employers, metrics, certifications, or eligibility;
  • missing material job requirements;
  • inconsistent claims between resume and cover letter;
  • generic or unsupported company statements;
  • spelling, grammar, and language consistency.

The resume must not hide genuine gaps through keyword stuffing. The cover letter may honestly bridge adjacent experience but must not present it as a direct match.

Step 3: Compile Documents

Compile both files:

cd documents/cv_resume/<company>/<role>
lualatex -interaction=nonstopmode resume.tex
lualatex -interaction=nonstopmode cover-letter.tex

If compilation fails, report the error and revise only the minimum necessary LaTeX source. Recompile until successful.

Step 4: Inspect PDFs

Visually inspect:

  • resume.pdf
  • cover-letter.pdf

Confirm:

  • resume is exactly two pages;
  • cover letter is exactly one page;
  • no section heading, role title, or education title is orphaned at a page break;
  • no clipped text, broken links, overflow, or excessive whitespace;
  • contact details are visible;
  • cover-letter signature is visible.

Step 5: Check ATS Text Layer

If pdftotext is available, run:

cd documents/cv_resume/<company>/<role>
pdftotext -layout resume.pdf resume.txt

Check that:

  • text extracts without replacement characters or (cid:...) markers;
  • email and phone appear as literal text;
  • role titles, companies, dates, and section order extract clearly;
  • truthful required job keywords appear where appropriate.

Delete resume.txt after checking it.

If pdftotext is unavailable, report that ATS text extraction was skipped and complete visual keyword checks instead.

Step 6: Report Results

Return a pass/fail checklist for:

  • factual accuracy;
  • job requirement coverage;
  • resume and cover-letter consistency;
  • LaTeX compilation;
  • resume page count;
  • cover-letter page count;
  • visual layout;
  • ATS text extraction;
  • keyword coverage.

Do not mark documents ready until every required check passes.

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.