Skip to content
Back to search

offersmith

MarketplaceWorks with Claude CodeGitHub

Offersmith: from your real experience to a job offer.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/anatolykoptev--offersmith/badge.svg)](/listings/anatolykoptev--offersmith)

HTML

<a href="/listings/anatolykoptev--offersmith"><img src="/api/listings/anatolykoptev--offersmith/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

As a Claude Code plugin

/plugin marketplace add anatolykoptev/offersmith
/plugin install offersmith@offersmith

On Claude Code 2.1.275 or later one step does both: `/plugin install offersmith --marketplace anatolykoptev/offersmith`.

Then ask for what you want ("start my master resume", "tailor my resume for this posting", "run the ATS check"). The skills carry the procedure; the scripts they call ship in the plugin.

Tools the skills use: `uv` and Python 3.13 (resolved by `uv`), poppler (`pdftotext`, `pdfinfo`), and for the resume and letter rendering `pandoc`, `typst` and `jq`. The LLM layers of the ATS check call the `claude` CLI and are optional (`--no-llm`).

As a command line tool

uv tool install git+https://github.com/anatolykoptev/offersmith
offersmith --resume resume.pdf --jd posting.txt --master "Your Name — master resume.md"

`offersmith` is the main command; `honest-ats` and `ats-check` are the same command under its earlier names. From a checkout, `./offersmith` runs the pinned environment from any directory. Reference: [docs/ats-check.md](docs/ats-check.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines
  1. {
  2. "name": "offersmith",
  3. "description": "Offersmith: from your real experience to a job offer.",
  4. "owner": { "name": "Anatoly Koptev" },
  5. "plugins": [
  6. {
  7. "name": "offersmith",
  8. "source": "./",
  9. "description": "Local job-application toolkit: master resume, tailored resume, cover letter, form answers, honest ATS check."
  10. }
  11. ]
  12. }
README.md · README · 83 lines
  1. # Offersmith
  2. **Offersmith: from your real experience to a job offer.**
  3. A local job-application toolkit for a coding agent, packaged as a Claude Code plugin. You keep one private bank of your true facts (the master resume). The agent cuts a tailored resume and a cover letter from it, checks the resume the way an applicant tracking system reads it, and drafts form answers, and every sentence traces back to a fact you recorded. Nothing is invented, and the ATS check never suggests claiming something you have not done.
  4. It prepares the application. It does not find postings or submit anything: a job-search service finds the posting, Offersmith gets your application ready for it.
  5. ## Workflow
  6. 1. **Master resume** (`master-resume`): your fact bank. Every bullet has an id, every number has one home and a source, a claim guard lists what you must not claim, and a linter keeps it consistent.
  7. 2. **Tailored resume** (`tailor-resume`): a one-to-two page cut from the master for one posting, in a parser-safe format, rendered to PDF and checked against format rules.
  8. 3. **Cover letter** (`cover-letter`): one page, PDF plus plain text. A fact map ties every factual sentence to a master id or a file, and a checker rejects untraced numbers, stock phrases and anything your claim guard forbids.
  9. 4. **ATS check** (`ats-check`): runs the PDF through five text extractors, matches the posting's requirements, and sorts every missing keyword into "true, add it", "gap, not yours to claim" or "rejected by your guard".
  10. 5. **Form answers** (`application-answers`): drafts the short fields from the master and leaves legal and personal questions (work authorization, salary, demographics) to you.
  11. ## Install
  12. ### As a Claude Code plugin
  13. ```
  14. /plugin marketplace add anatolykoptev/offersmith
  15. /plugin install offersmith@offersmith
  16. ```
  17. On Claude Code 2.1.275 or later one step does both: `/plugin install offersmith --marketplace anatolykoptev/offersmith`.
  18. Then ask for what you want ("start my master resume", "tailor my resume for this posting", "run the ATS check"). The skills carry the procedure; the scripts they call ship in the plugin.
  19. Tools the skills use: `uv` and Python 3.13 (resolved by `uv`), poppler (`pdftotext`, `pdfinfo`), and for the resume and letter rendering `pandoc`, `typst` and `jq`. The LLM layers of the ATS check call the `claude` CLI and are optional (`--no-llm`).
  20. ### As a command line tool
  21. ```
  22. uv tool install git+https://github.com/anatolykoptev/offersmith
  23. offersmith --resume resume.pdf --jd posting.txt --master "Your Name — master resume.md"
  24. ```
  25. `offersmith` is the main command; `honest-ats` and `ats-check` are the same command under its earlier names. From a checkout, `./offersmith` runs the pinned environment from any directory. Reference: [docs/ats-check.md](docs/ats-check.md).
  26. ## Configuration
  27. Put an `offersmith.toml` in the directory you work in, or in `~/.config/offersmith/`, or point `OFFERSMITH_CONFIG` at one:
  28. ```toml
  29. master = "~/offersmith/master/Your Name — master resume.md" # the fact bank
  30. guard = "" # default: "<stem> — claim guard.md" next to the master
  31. out_dir = "~/offersmith/out" # ATS reports go to <out_dir>/<resume stem>
  32. workday_base = "" # https://<tenant>.wdN.myworkdayjobs.com/<site>, for --workday-req
  33. ```
  34. `OFFERSMITH_MASTER`, `OFFERSMITH_GUARD`, `OFFERSMITH_OUT` and `OFFERSMITH_WORKDAY_BASE` override the file; a command-line flag overrides both. Keep your master outside this repository.
  35. A synthetic master, its sidecars, a resume and a letter for a made-up candidate (Jane Example) are in [`examples/`](examples/). Copy them as the starting point.
  36. ## The honesty principle
  37. - Every claim in a resume, letter or answer comes from a master bullet, a metrics row or a file you can open. A fact the master lacks is a question for you, never a sentence.
  38. - The claim guard is binding: wording you cannot support, numbers you decided not to use, names that must stay out of a letter.
  39. - The master has no absence notes ("never used X"): a skill you lack simply does not appear, and the one negative list is the guard.
  40. - The ATS check marks a missing keyword "true, add it" only when an id-carrying master bullet or the Skills table supports it, and it quotes that line so you can confirm the exact claim. A word found in a rule or a note is a coincidence, not evidence.
  41. - You say once how the work was done (for example that AI coding agents wrote the code under your review) and never hide it. See [docs/voice-and-truth.md](docs/voice-and-truth.md).
  42. ## What the ATS check can and cannot tell you
  43. - **Trust:** parse failures (the extractors really disagree, and the evidence quotes the text); which posting terms are literally absent from what a parser reads; where a term sits; the master-based split of true additions, gaps and rejected claims.
  44. - **Do not trust as a prediction:** the coverage percent or the AI grade. No public spec exists for Workday, HiredScore or Ashby ranking, so the AI layer is an LLM proxy and the coverage number is a relative guide for comparing two versions of the same resume against the same posting, not a probability of being shortlisted.
  45. - **Not modelled:** knock-out questions inside the application form, recruiter sourcing outside the ATS, DOCX-specific parsing, non-English resumes, OCR-based pipelines.
  46. - Knock-outs (years, degree, location, clearance) are surfaced for you to answer, never decided.
  47. The scoring rules, the extractors and the safety of the LLM calls are documented in [docs/ats-check.md](docs/ats-check.md).
  48. ## Privacy
  49. Everything runs on your machine: the master, resumes, letters and reports are files you own, and nothing is uploaded. The only data that leaves is what the ATS check's optional LLM layers send to the `claude` CLI (the posting text and your resume text, sandboxed, with no tools and no file access), and the posting fetch when you pass `--jd-url` or `--workday-req`. Run with `--no-llm` and a saved posting file to send nothing at all. This repository holds no real resume, master or posting.
  50. ## Development
  51. `uv sync --locked`, then `uv run pytest` (the letter and resume tests also need `pandoc`, `typst`, `jq` and poppler; in CI a missing tool fails the run). `uv run python tests/mutate.py` runs the mutation proof for the matching, scoring and config call sites. `claude plugin validate .` checks the manifests. Documents: [docs/INDEX.md](docs/INDEX.md).
  52. ## License
  53. Apache-2.0, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.