What is check-structure?

A resume structure checker that looks for missing sections, contact details, date problems, and formatting risks. An applicant tracking system, or ATS, is software employers use to read and sort resumes.

Use it to check whether a resume is complete and machine-readable. It requires a parsed resume in the expected JSON format.

It identifies layout and parsing problems that could cause an ATS to miss information, without needing a job description. It does not measure keyword matching or give an overall ATS score.

check-structure — Skill for Claude Code and Codex by dcassil: A resume structure checker that looks for missing sections…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/dcassil/resume-kit/check-structure

Any agent

npx skills add dcassil/resume-kit --skill check-structure

Clone the repo

git clone --depth 1 https://github.com/dcassil/resume-kit

Made for: Claude Code, Codex.

Or install resume-intelligence, the plugin that ships this one along with the rest of its 31 skills, 1 command, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dcassil/resume-kit/check-structure.svg)](https://agentmods.dev/skills/dcassil/resume-kit/check-structure)

Your own site

<a href="https://agentmods.dev/skills/dcassil/resume-kit/check-structure"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/check-structure.svg" alt="Measured on agentmods" height="20"></a>

Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 826 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00097	$0.00826
Opus 5	$0.00048	$0.00413
Sonnet 5	$0.00019	$0.00165
Haiku 4.5	$0.00010	$0.00083

Measured 3d ago against content hash 719a6fcf2986, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-structure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/resume-intelligence/skills/check-structure/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Renamed: check-structure was check-ats-structure before v1.0.0 (see RIT-A-0005).

check-structure — resume-only structural / parse check

Prerequisites

Run the shared Prerequisites gate first — see _shared/prerequisites.md.

Required input: a ResumeDocument JSON — the active_resume pointer in resume-kit/config.json (or an explicit resume JSON path the caller passes).
Does NOT need a job. This check is job-independent; do not require or read a JobDescription.
If the resume JSON is missing (no active_resume, file absent, or a raw PDF/DOCX where a ResumeDocument JSON is required): STOP. Do not guess and do not run on partial input. Tell the caller: run parse-resume first to produce the ResumeDocument JSON, then re-run this skill.

Purpose

Surface the structural signal a resume can be judged on without any job: how complete its key sections are, and concrete, deterministic recommendations for things that trip applicant tracking systems — missing contact fields, absent canonical sections, malformed dates, and non-ASCII / formatting parse risks.

This is deliberately one job: structure only. It never reports keyword coverage, matched/missing job terms, skills coverage, or any composite/overall ATS score — those require a job description and belong to check-keywords. Keeping this skill structure-only means an agent has exactly one obvious skill to run for "will an ATS parse this resume correctly?"

How to invoke

Prefer the MCP tool in-process; use the CLI when scripting.

CLI

resume-tool check-structure --resume <resume.json> [--output {json,text,md}] [--strict]

MCP tool: resume_check_ats_structure

Input field: resume (a serialized ResumeDocument). There is no job and no alias_file — structure scoring is job-independent, so no synonym index is involved.

Output (`AtsStructureReport`)

Field	Type	Notes
`section_completeness`	float (0–100)	How many key resume sections are present
`recommendations`	list of strings	Deterministic structural fixes (contact info, section presence, dates, non-ASCII / formatting risks)

Read the full file on GitHub · 81 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 81 lines · 97 tokens per session scan A 719a6fcf2986

Subscribe to this mod's changes

check-structure is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 23d ago), licensed Apache-2.0. It adds 97 tokens to every session and 826 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens