skilldrop-cli 0.16.6 → 0.16.8

package/packs/career/skills/cover-letter/evals/files/7/resume.md

@@ -0,0 +1,23 @@
+LEO TANAKA
+Edinburgh | leo.tanaka@example.com | 07700 900271
+
+Sous Chef, The Larder at Queensgate (80-cover restaurant), Edinburgh
+May 2022 - present
+- Run the kitchen on the head chef's two days off each week.
+- Lead a brigade of 6 on service.
+- Write and cost the weekly specials; do the fish and vegetable orders.
+- Trained 3 commis chefs, one now a chef de partie.
+- Keep the allergen matrix up to date for every menu change.
+- Environmental health inspection in 2025: rated 5.
+
+Chef de Partie, Harbour Rooms Hotel, Leith
+March 2019 - April 2022
+- Ran the sauce section; covered banqueting for weddings in summer.
+
+Commis Chef, Harbour Rooms Hotel, Leith
+August 2017 - March 2019
+
+TRAINING
+SVQ Level 3 Professional Cookery, Edinburgh College, 2019
+Level 2 Food Safety and Hygiene for Catering, renewed 2024
+Allergen awareness training, 2024

package/packs/career/skills/cover-letter/manifest.json

@@ -0,0 +1,37 @@
+{
+  "name": "cover-letter",
+  "version": "0.1.0",
+  "description": "Write a cover letter for one job from the person's resume and the posting: under a page, opening on the strongest evidence for the role, two or three specifics matched to what the employer asked for, and no enthusiasm, company facts or experience the person didn't supply. A script lists every figure and name in the letter that their own material doesn't contain. Works for any occupation and level. Use when the user says \"write a cover letter for this job\", \"draft a covering letter\", \"write the cover note for my application\", or needs an application email to go with a resume.",
+  "entrypoint": "SKILL.md",
+  "deps": {
+    "npm": [],
+    "pip": []
+  },
+  "env": {
+    "required": [],
+    "optional": []
+  },
+  "related": [
+    "job-fit-analysis",
+    "output-hygiene",
+    "resume-tailor"
+  ],
+  "tags": [
+    "cover-letter",
+    "job-application",
+    "resume",
+    "career",
+    "job-search",
+    "writing"
+  ],
+  "permissions": {
+    "network": [],
+    "commands": [],
+    "files": "named-paths",
+    "notes": "Reads the draft, source and posting files it is given. Writes nothing."
+  },
+  "model": {
+    "tier": "standard",
+    "rationale": "A short letter from supplied facts, with a script listing every figure and name the person's material doesn't contain."
+  }
+}

package/packs/career/skills/cover-letter/scripts/claim_check.py

@@ -0,0 +1,250 @@
+#!/usr/bin/env python3
+"""List what a tailored resume or cover letter says that the candidate's own material doesn't.
+
+  python3 claim_check.py DRAFT --source RESUME [--source NOTES ...] [--posting POSTING] [--json]
+
+DRAFT is the text you are about to send. Each --source is something the candidate wrote or
+told you: the original resume, notes from the conversation. --posting is the job posting.
+
+It reports four kinds of finding, each with the line it is on:
+
+  number       a figure in the draft that no source contains ("35%", "$2M", "team of 8")
+  name         a named thing in the draft that no source contains: a tool, an employer, a
+               certification, a degree ("Kubernetes", "Epic", "Green Belt")
+  combination  capitalised words that each appear in a source but never together
+               ("Senior Manager" when the source has "Senior Analyst" and "Office Manager")
+  borrowed     wording the draft shares with the posting and no source uses. Fine when the
+               source shows the same thing in other words; a false claim when it doesn't.
+
+A name or number that the posting contains is marked "in posting": right when the draft is
+talking about the employer, wrong when it is claimed as the candidate's own.
+
+It reads text, so it cannot tell a true claim from a false one. It tells you where to look.
+Exit status: 0 nothing found, 1 findings, 2 a file could not be read. Standard library only.
+"""
+import argparse
+import json
+import re
+import sys
+
+MULT = {"k": 1e3, "thousand": 1e3, "m": 1e6, "mm": 1e6, "million": 1e6,
+        "bn": 1e9, "b": 1e9, "billion": 1e9}
+NUMBER = re.compile(r"(?<![\w.])(\d[\d,]*(?:\.\d+)?)(?:(k|mm|m|bn|b)\b|\s?(thousand|million|billion)\b)?"
+                    r"(\s?%|\s?percent\b|\s?per cent\b)?", re.I)
+WORD = re.compile(r"(?<![A-Za-z0-9])\.?[A-Za-z][A-Za-z0-9+#']*(?:\.[A-Za-z0-9]+)*")
+LIST_MARK = re.compile(r"^\s*(?:[-*•–>]+|\d+[.)]|#+|\|)\s*")
+LINK = re.compile(r"\[([^\]]*)\]\([^)]*\)")
+SUFFIXES = ("ations", "ation", "ments", "ment", "ings", "ing", "ers", "ies", "ed", "er", "es", "s", "ly")
+
+# Words that start a line or a sentence with a capital letter and name nothing.
+PLAIN = set("""
+a an and are as at be been both but by for from had has have he her his i if in into is it its
+me my no not of on or our she so that the their them then there these they this to up us was
+we were what when where which who why with you your dear sincerely regards kind best yours
+faithfully hiring manager team committee recruiter sir madam re subject date enclosed
+summary profile objective experience employment work history education skills tools
+certifications certification qualifications training projects awards languages interests
+references available request professional career key core technical additional other
+volunteering volunteer contact details achievements highlights about present current
+january february march april may june july august september october november december
+jan feb mar apr jun jul aug sep sept oct nov dec monday tuesday wednesday thursday friday
+saturday sunday full part time application applying while although though because since
+during after before however also please thank thanks between over across within having most each every one two three
+""".split())
+DATE_LINE = re.compile(r"^\s*(?:\d{1,2}(?:st|nd|rd|th)?\s+)?[A-Z][a-z]{2,8}\.?\s+(?:\d{1,2}(?:st|nd|rd|th)?,?\s+)?\d{4}\s*$")
+# The joining words allowed inside a capitalised phrase: "Head of Geography".
+JOINERS = {"of", "and", "for", "the", "in", "at", "&", "de"}
+STOP = PLAIN | set("""
+able across after also been before being between can could did does doing each every experience
+experienced including into just like more most much need needs over role roles some such than
+them through under using very well will within without work worked working would years year
+have with that this from your their about must should strong good great team teams including
+ability skills skill knowledge new help helps support supports ensure make makes
+""".split())
+
+
+def read(path):
+    try:
+        with open(path, encoding="utf-8", errors="replace") as f:
+            return f.read()
+    except OSError as e:
+        print("claim_check: cannot read %s: %s" % (path, e.strerror), file=sys.stderr)
+        sys.exit(2)
+
+
+def clean(line):
+    """A line with its markup removed, so `**Go**` and `Go` read the same. Resumes kept as
+    Typst or LaTeX source escape `$`, `&`, `%` and `#`; the escapes are dropped too."""
+    line = LINK.sub(r"\1", line)
+    line = re.sub(r"\\([$&%#_])", r"\1", line)
+    line = re.sub(r"(?<![$£€\w.,])\d+(?:\.\d+)?(?:em|mm|pt|cm|px|fr)\b", " ", line)  # layout lengths
+    line = line.replace("’", "'").replace("‘", "'").replace("–", " - ").replace("—", " - ")
+    return re.sub(r"[*_`~]", "", line)
+
+
+def numbers(text):
+    """{(value, is_percent)} for every figure in the text. "$2M" and "2 million" are one value."""
+    found = set()
+    for m in NUMBER.finditer(text):
+        try:
+            value = float(m.group(1).replace(",", ""))
+        except ValueError:
+            continue
+        unit = (m.group(2) or m.group(3) or "").lower()
+        found.add((value * MULT.get(unit, 1), bool(m.group(4))))
+    return found
+
+
+def stem(word):
+    w = word.lower().strip("'.")
+    if w.endswith("'s"):
+        w = w[:-2]
+    for s in SUFFIXES:
+        if w.endswith(s) and len(w) - len(s) >= 4:
+            return w[: -len(s)]
+    return w
+
+
+def key(word):
+    """How a name is compared: case, dots, a plural, a possessive or a contraction don't matter."""
+    w = word.lower().strip("'")
+    w = re.sub(r"'(?:s|m|d|ve|ll|re|t)$", "", w)
+    w = w.replace(".", "") or w
+    return w[:-1] if len(w) > 4 and w.endswith("s") and not w.endswith("ss") else w
+
+
+def vocabulary(text):
+    names, stems = set(), set()
+    for line in text.splitlines():
+        for w in WORD.findall(clean(line)):
+            names.add(key(w))
+            stems.add(stem(w))
+    flat = " ".join(key(w) for line in text.splitlines() for w in WORD.findall(clean(line)))
+    return names, stems, " " + flat + " "
+
+
+def looks_named(word):
+    """True for a word that is a name whatever its position: AWS, JavaScript, C++, k8s, .NET."""
+    body = word.lstrip(".")
+    return bool(re.search(r"[A-Z]", body[1:]) or re.search(r"[0-9+#]", body) or word.startswith("."))
+
+
+def phrases(line):
+    """Runs of capitalised or name-shaped words in one line, as lists of words.
+
+    The first word of a line or sentence is capitalised by grammar, not because it is a name,
+    so it only counts when it is name-shaped itself or opens a longer capitalised run."""
+    text = LIST_MARK.sub("", clean(line))
+    out, run, start_of_sentence = [], [], True
+    tokens = re.findall(r"(?<![A-Za-z0-9])\.?[A-Za-z][A-Za-z0-9+#']*(?:\.[A-Za-z0-9]+)*|&|[.!?;:]\s|[,|·/()]|\s-\s", text + " ")
+    for i, tok in enumerate(tokens):
+        if not (tok[0].isalpha() or tok[0] in ".&") or tok.strip() in (".", "!", "?", ";", ":"):
+            if run:
+                out.append(run)
+            run = []
+            start_of_sentence = tok.strip() in (".", "!", "?")
+            continue
+        if "'" in tok and key(tok) in PLAIN:  # I'm, I've, we'd
+            tok = key(tok)
+        capital = tok[0].isupper() or looks_named(tok)
+        if capital and not (start_of_sentence and not looks_named(tok) and tok.lower() in PLAIN):
+            run.append((tok, start_of_sentence))
+        elif run and tok.lower() in JOINERS and i + 1 < len(tokens) and tokens[i + 1][:1].isupper():
+            run.append((tok, False))
+        else:
+            if run:
+                out.append(run)
+            run = []
+        start_of_sentence = False
+    if run:
+        out.append(run)
+    cleaned = []
+    for r in out:
+        # A lone sentence-opening word ("Led", "Built") is grammar, not a name.
+        if len(r) == 1 and r[0][1] and not looks_named(r[0][0]):
+            continue
+        # A sentence-opening verb in front of a name ("Led AWS migration") is dropped from the run.
+        if len(r) > 1 and r[0][1] and not looks_named(r[0][0]) and r[0][0].lower() not in PLAIN:
+            r = r[1:] if r[0][0].lower().endswith(("ed", "ing")) else r
+        words = [w for w, _ in r]
+        while words and words[-1].lower() in JOINERS:
+            words.pop()
+        if words:
+            cleaned.append(words)
+    return cleaned
+
+
+def check(draft, sources, posting):
+    src_names, src_stems, src_flat = vocabulary("\n".join(sources))
+    src_numbers = numbers("\n".join(clean(s) for s in sources))
+    post_names, post_stems, _ = vocabulary(posting or "")
+    post_numbers = numbers(clean(posting or ""))
+    findings, seen = [], set()
+
+    def add(kind, what, n, line, in_posting=False):
+        if (kind, what.lower()) in seen:
+            return
+        seen.add((kind, what.lower()))
+        findings.append({"kind": kind, "text": what, "line": n, "context": line.strip()[:160],
+                         "in_posting": in_posting})
+
+    for n, raw in enumerate(draft.splitlines(), 1):
+        line = clean(raw)
+        if not line.strip() or DATE_LINE.match(LIST_MARK.sub("", line)):
+            continue  # a letter's own date line claims nothing
+        body = LIST_MARK.sub("", line)
+        for m in NUMBER.finditer(body):
+            got = next(iter(numbers(m.group(0))), None)
+            if got and got not in src_numbers:
+                add("number", m.group(0).strip(), n, raw, got in post_numbers)
+        for words in phrases(raw):
+            content = [w for w in words if w.lower() not in JOINERS]
+            missing = [w for w in content if key(w) not in src_names and w.lower() not in PLAIN]
+            if missing:
+                add("name", " ".join(words), n, raw, all(key(w) in post_names for w in missing))
+            elif len(content) > 1 and all(w.lower() not in PLAIN for w in content):
+                flat = " ".join(key(w) for w in words if w != "&")
+                if " " + flat + " " not in src_flat:
+                    add("combination", " ".join(words), n, raw)
+        if posting:
+            for w in WORD.findall(body):
+                s = stem(w)
+                if (len(s) >= 4 and w.lower() not in STOP and s in post_stems and s not in src_stems
+                        and key(w) not in src_names and not w[0].isupper() and not looks_named(w)):
+                    add("borrowed", w.lower(), n, raw, True)
+    return findings
+
+
+def main():
+    ap = argparse.ArgumentParser(description="List what a draft says that the candidate's own material doesn't.")
+    ap.add_argument("draft")
+    ap.add_argument("--source", action="append", required=True, metavar="FILE",
+                    help="the candidate's own resume or notes; repeat for more than one")
+    ap.add_argument("--posting", metavar="FILE", help="the job posting")
+    ap.add_argument("--json", action="store_true")
+    a = ap.parse_args()
+
+    findings = check(read(a.draft), [read(p) for p in a.source], read(a.posting) if a.posting else None)
+    if a.json:
+        print(json.dumps({"draft": a.draft, "findings": findings}, indent=1))
+        return 1 if findings else 0
+    if not findings:
+        print("PASS  %s: every figure and name is in the source material." % a.draft)
+        return 0
+    labels = {"number": "Figures not in the source", "name": "Names not in the source",
+              "combination": "Words the source has, but not together",
+              "borrowed": "Wording taken from the posting"}
+    print("REVIEW  %s: %d item(s) to check against the source material." % (a.draft, len(findings)))
+    for kind in ("number", "name", "combination", "borrowed"):
+        rows = [f for f in findings if f["kind"] == kind]
+        if not rows:
+            continue
+        print("\n%s (%d)" % (labels[kind], len(rows)))
+        for f in rows:
+            note = "  [in posting]" if f["in_posting"] and kind != "borrowed" else ""
+            print("  line %d: %s%s\n      %s" % (f["line"], f["text"], note, f["context"]))
+    return 1
+
+
+if __name__ == "__main__":
+    sys.exit(main())

package/packs/career/skills/job-fit-analysis/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: job-fit-analysis
+description: Compare a job posting with a resume and say honestly whether to apply: each requirement marked met, partly met, not shown or not met, with the resume line it rests on; the requirements an employer screens on listed first; and the questions whose answers would change the picture. Works for any occupation and level. Use when the user asks "am I a good fit for this job", "should I apply for this", "how does my resume match this posting", or wants the gaps between a job description and their CV before applying.
+---
+
+# job-fit-analysis
+
+You compare one job posting with one person's resume and tell them where they stand before
+they spend an evening on the application. The reader is the candidate. They need a straight
+answer, the evidence behind it, and to know which gaps are real and which are only missing
+from the page. It works the same for a nurse, a warehouse supervisor, a graduate or a staff
+engineer: the posting sets the requirements, the resume is the evidence.
+
+## How to respond
+
+These four rules outrank the steps below.
+
+- **Answer first.** The first sentence answers what they asked: apply or don't, and why.
+  The whole analysis is in the reply. Do not put it in a file unless they ask for one.
+- **Use only what you were given.** The resume and what the person told you are the only
+  evidence. Nothing is credited because people in that job usually have it.
+- **Deliver from what you have.** With a posting and three lines about the person, compare
+  those. Do not stop to ask for a full resume.
+- **Write to the candidate.** Address them as "you", never by name or as "he", "she" or
+  "the candidate". Plain words, no scoring jargon, no mention of this skill. When they gave
+  you a few lines and no resume, say "what you told me", never "your resume".
+
+1. **Read everything the person gave you.** The resume is the main evidence, and so is
+   any other file of theirs they point to or that sits beside it: a LinkedIn summary, a
+   portfolio page, a project's README. Evidence from one of those counts in full: mark the
+   requirement `Met` or `Partly` on the strength of it, say where it came from, and say it
+   is not on the resume yet, because the employer will only see the resume.
+
+   When the posting is a link, read the full text. If you cannot open it, say so in one line
+   and ask for the text pasted in. Give no verdict and list no requirements for a posting you
+   have not read, and never rebuild one from what you remember of the employer. Do not guess
+   at why the link would not open.
+
+2. **List the posting's requirements.** Keep the employer's own wording. Sort
+   them into what the posting calls required and what it calls preferred. When the posting
+   doesn't say, treat what it lists first or repeats as required, and say you inferred it.
+
+3. **Find what could get the application rejected.** Two kinds of requirement do it: the
+   ones a recruiter or an application form checks before anyone reads the rest (a licence or
+   registration, a degree, a certification, a minimum number of years, the right to work,
+   location or shift, a clearance, a language), and any other required item the resume does
+   not meet, such as a named system the posting lists under "must have". These go first,
+   because one of them outweighs five met skills.
+
+4. **Mark each requirement against the evidence** with one of four words:
+   - **Met**: the resume shows it. Quote the line.
+   - **Partly**: the resume shows something close, smaller or older. Say what it shows and
+     what is short: "team of 12; the posting asks for 20 or more".
+   - **Not shown**: the resume is silent. The person may well have it.
+   - **Not met**: the resume shows otherwise, such as a diploma where a degree is required
+     or two years where five are asked for.
+
+   A similar tool is not the named tool. Cerner is not Epic, an in-house warehouse system is
+   not SAP: when the posting requires the named one, mark it `Not met` and give the similar
+   one as the nearest thing you have. A related task is not the named skill: cashing up a
+   till is not bookkeeping in Xero, so that is `Not shown`.
+
+   Take lengths of time only from dates the resume gives for that exact thing. When the
+   posting asks for two years of something and the resume shows the activity with no start
+   date, mark it `Partly`, say the resume doesn't show how long, and ask. Never state a
+   duration you worked out from a neighbouring date.
+
+5. **Give a verdict the person can act on.** Open with a plain sentence that says whether
+   to apply, in the terms they asked ("Yes, apply", "Apply, but expect the degree to be a
+   problem", "Probably not worth your weekend unless..."), then one of four labels and the
+   reason:
+   - **Strong match**: every required item is met, or partly met with close evidence.
+   - **Worth applying**: nothing that would get it rejected is unmet, and most of the rest
+     is met.
+   - **Long shot**: something that could get it rejected is unmet. Say what would have to be
+     true for it to be worth the time, and whether you would still send it.
+   - **Not a match**: a requirement that cannot be worked around is unmet, such as a licence.
+
+   Write the table first and take the count from it. The opening sentence counts every
+   required item that is `Not met` or `Partly`, not only the worst one: "four of the six required items aren't met: the degree, the team size,
+   advanced Excel and SAP". It must agree with the table below it. Give the verdict on what
+   you know now; say what answer would raise it, but do not make the verdict wait on the
+   answer. Do not soften a long shot into encouragement, do not harden a workable gap into a
+   refusal, and do not give a percentage.
+
+6. **Say what to bring forward.** List the two to four things already in the resume that
+   answer the posting best and are buried, understated or worded differently from the
+   posting. Give the resume's wording and the posting's wording side by side.
+
+7. **Close with what to do next**, in two to four lines: what to lead the application with,
+   what to say about the main gap, and the one or two questions whose answers would change
+   the verdict ("Have you used Epic anywhere? If so, where and for how long?"). When a
+   required item is not shown, ask once whether anything outside the resume covers it: a
+   side project, a repository, a portfolio, a volunteer role. People leave their best
+   evidence off the page. Anything you credited from another file goes here too, as a line
+   to add to the resume. Never tell
+   them to add a keyword they have not said is true, and do not end on a list of questions
+   with no advice.
+
+8. **Lay the reply out in this order:** the answer and verdict; what could get it rejected;
+   one table covering every requirement (requirement, required or preferred, status,
+   evidence); what to bring forward; what to do next. Each requirement appears in the table
+   once and nothing is repeated in a second table or restated section by section.
+
+   Match the length to what you were given. A short posting and a few lines about the person
+   gets a short answer: the verdict, one line per requirement, and what to do, in under 250
+   words and with no table. A full resume against a long posting gets the table, and still
+   fits a page.
+
+**With a posting and no resume**, compare against whatever the person said about themselves,
+mark the rest `Not shown`, and say a resume would settle those. **With a resume and no
+posting**, ask for the posting in one line: there is nothing to compare against.
+
+## Quality bar
+
+- **Every Met and Partly quotes the resume.** A status with no line behind it is a guess.
+- **What could get the application rejected is named first**, never left as one row among many.
+- **No length of time appears that the resume's own dates don't give.**
+- **`Not shown` and `Not met` are kept apart.** One is a question, the other is a gap.
+- **Nothing is credited that the resume or the person doesn't state.**
+- **The verdict matches the table.** An unmet required degree cannot sit under "strong
+  match", and a verdict that names one gap cannot sit over a table that shows four.
+
+## When to use this skill
+
+- ✅ Deciding whether a posting is worth applying for
+- ✅ Finding the gaps between a resume and a posting before tailoring the resume
+- ✅ Checking several postings against one resume to choose where to spend effort
+
+## When NOT to use this skill
+
+- ❌ Rewriting the resume for the posting. Use `resume-tailor`.
+- ❌ Writing the cover letter. Use `cover-letter`.
+- ❌ Critiquing the resume as a document, with no job in mind. Use `doc-critique`.
+
+## Anti-patterns to avoid
+
+- ❌ **"87% match."** A percentage hides which requirement is the problem.
+- ❌ **Cheerleading.** "You'd be a great fit!" over an unmet required degree wastes the
+  person's evening.
+- ❌ **Crediting the usual.** "As a nurse you will have used Epic" is an invention.
+- ❌ **Treating a similar tool as the named one.**
+- ❌ **Advising them to add keywords** so the resume passes a filter. If it isn't true it
+  doesn't go in.
+- ❌ **Judging the person.** No remarks on age, gaps, family, health or anything a recruiter
+  may not lawfully weigh.
+- ❌ **Inventing the posting.** A link you could not open is not a posting you have read.
+- ❌ **Answering in a file.** They asked a question; the answer belongs in the reply.
+- ❌ **A verdict with no advice.** "Long shot" followed by questions leaves them where they
+  started.
+- ❌ **Showing the machinery.** No status legend longer than a line, no account of how the
+  comparison was produced, no remark about what you could or couldn't save.

package/packs/career/skills/job-fit-analysis/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Am I a good fit for this job? Here's the posting and my resume",
+    "should_trigger": true
+  },
+  {
+    "query": "Should I apply for this role or is it a stretch?",
+    "should_trigger": true
+  },
+  {
+    "query": "What's missing from my CV for this job description?",
+    "should_trigger": true
+  },
+  {
+    "query": "Compare my resume against these three postings and tell me which to go for",
+    "should_trigger": true
+  },
+  {
+    "query": "Tailor my resume to this job posting",
+    "should_trigger": false
+  },
+  {
+    "query": "Write a cover letter for this role",
+    "should_trigger": false
+  },
+  {
+    "query": "Critique my resume, it's not for any particular job",
+    "should_trigger": false
+  },
+  {
+    "query": "Compare these three applicant tracking systems for our HR team",
+    "should_trigger": false
+  }
+]

package/packs/career/skills/job-fit-analysis/evals/evals.json

@@ -0,0 +1,102 @@
+{
+  "skill_name": "job-fit-analysis",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "My CV is in resume.md and the job I'm looking at is in posting.md. Am I a good fit? Be honest, I don't want to waste a weekend on it.",
+      "assertions": [
+        "The Epic requirement is marked as not met, partly met or not shown, and the reply says her CV shows Cerner, not Epic, naming both systems",
+        "Basic Life Support instructor certification is shown as not held: the CV has BLS provider only",
+        "The teaching requirement is credited from precepting newly qualified nurses (9 preceptees) or the 2022 mentorship module, and the reply notes or asks how long she has been precepting, because the CV does not show two years of it",
+        "NMC registration, a nursing degree and at least 3 years of post-registration medical-surgical experience are each marked as met",
+        "A master's degree and simulation lab experience are shown as not held or not shown, and as preferred items, not required ones",
+        "The reply opens with an overall verdict on whether to apply, before the requirement-by-requirement detail",
+        "It points to the sepsis screening guide or the Cerner superuser role as existing evidence worth bringing forward",
+        "It does not credit her with any tool, qualification or experience that is not in the CV, and does not advise adding one"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Thinking of applying for this (posting.md). My resume's in resume.md. What are my chances and what's missing?",
+      "assertions": [
+        "The bachelor's degree is marked as required and not met: the resume shows a high school diploma and 18 uncompleted college credits",
+        "The degree gap is stated in the verdict or before the detailed list, as something likely to screen him out, not only as one row among many",
+        "The team-size requirement is marked short, with both numbers: he supervises 12 and the posting asks for 20 or more",
+        "SAP Extended Warehouse Management is marked not shown or partly met, and the reply says the resume shows an in-house warehouse system instead",
+        "Advanced Excel is not marked fully met: the resume shows rosters and attendance in Excel, and pivot tables and VLOOKUP are not shown",
+        "The safety record (zero lost-time incidents for 14 months) and the forklift certification are marked as met, quoting the resume",
+        "The overall verdict is not a strong match, and matches the unmet degree requirement",
+        "It does not advise him to claim a degree, SAP experience, a bigger team or any keyword he has not shown"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Is this worth applying for? I've been a barista for 4 years, shift lead for the last 2 - I do the rota for 9 people, the weekly stock order and cashing up. No degree.\n\nOffice Manager, Pell & Dray Architects (14 staff)\n- 2+ years in an office administration role\n- Managing supplier relationships and ordering\n- Organising staff schedules and meeting rooms\n- Bookkeeping experience with Xero\n- Confident with Microsoft 365\n- Friendly first point of contact for clients and visitors",
+      "assertions": [
+        "It delivers a requirement-by-requirement comparison from what was given, and does not stop to ask for a resume first",
+        "The 2+ years of office administration is marked not met or named as the main gap, since the experience is in a cafe and not an office",
+        "The rota for 9 people is credited against organising staff schedules, and the weekly stock order against ordering, each citing what the person said",
+        "Xero is marked not shown or not met, and cashing up is not presented as Xero or bookkeeping-software experience",
+        "Microsoft 365 is marked not shown or asked about, not assumed",
+        "The lack of a degree is not treated as a gap, because the posting does not ask for one",
+        "It gives an overall verdict that is honest about the office-experience gap",
+        "It does not invent an employer name, a qualification, a tool or any experience the person did not state"
+      ]
+    },
+    {
+      "id": 4,
+      "held_out": "2026-10-05",
+      "prompt": "Would I get anywhere with this? CV is resume.md, job is posting.md.",
+      "assertions": [
+        "The qualification requirement is marked not met: she has AAT Level 3 and two of five Level 4 units, not Level 4 complete or part-qualified ACCA or CIMA",
+        "The 2 years in a management accounts or analyst role is marked not met or short: her roles are accounts payable clerk and finance administrator",
+        "Power BI is shown as not held, and the Excel workbook is not presented as Power BI experience",
+        "Advanced Excel is credited from the workbook with pivot tables and lookups, quoting the CV",
+        "Variance analysis and budget commentary are marked not shown or not met",
+        "Sage 200 and the accruals for goods received not invoiced are credited as relevant evidence",
+        "The reply opens with a clear answer on whether to apply",
+        "It does not credit her with any qualification, tool or experience that is not in the CV"
+      ]
+    },
+    {
+      "id": 5,
+      "held_out": "2026-10-05",
+      "prompt": "Head chef job at a hotel, posting.md. My CV's resume.md. Realistic or not?",
+      "assertions": [
+        "Level 3 Food Safety is marked not met: he holds Level 2, and his Level 3 is in Professional Cookery, which is a different qualification",
+        "Team size is marked short with both numbers: a brigade of 6 against 12 or more",
+        "Running the kitchen on the head chef's two days off is credited toward the sous-chef-with-full-responsibility requirement, quoting the CV",
+        "Costing is credited from the weekly specials, and the 70% gross profit target is noted as not shown",
+        "Banqueting is credited from covering weddings at Harbour Rooms Hotel, and hotel experience is marked met",
+        "The reply gives a clear answer on whether it is realistic",
+        "It does not credit him with a qualification, a cover count, a team size or a system that is not in the CV"
+      ]
+    },
+    {
+      "id": 6,
+      "prompt": "Am I a fit for this? CV is resume.md, job is posting.md. My LinkedIn about text is in linkedin-about.txt too.",
+      "assertions": [
+        "The onboarding or training requirement is credited from the monthly onboarding webinar described in the LinkedIn text",
+        "The reply says that evidence is not on the CV and should be added to it",
+        "Owning renewals is marked partly or not met: she supported renewals alongside the account managers and did not own them",
+        "The 3+ years in customer success or account management is marked not met or partly: her roles are in support",
+        "Gainsight is marked not shown or not met, and Salesforce is credited from the CV",
+        "Leading a small team is marked met from leading 6 support agents",
+        "Working with a product team on feedback is credited from the Customer Advisory Board or the ticket-trends report",
+        "The reply opens with a clear answer on whether to apply"
+      ]
+    },
+    {
+      "id": 7,
+      "prompt": "Would I be a fit for this one? https://careers.brightloop.example/jobs/4471 - my CV is resume.md",
+      "assertions": [
+        "The reply says it could not open or read the link",
+        "It asks for the posting's text to be pasted in or saved as a file",
+        "It does not list the job's requirements or mark any as met or not met, as though it had read the posting",
+        "It gives no verdict on fit",
+        "It does not state what Brightloop does or what the role involves",
+        "The reply is short, about 120 words or fewer"
+      ]
+    }
+  ]
+}

package/packs/career/skills/job-fit-analysis/evals/files/1/posting.md

@@ -0,0 +1,28 @@
+# Clinical Nurse Educator — Surgical Division
+
+**Northfield General Hospital** · Full time, permanent · Band 6
+
+Northfield General is a 320-bed teaching hospital. The Surgical Division's education team supports 240 nursing staff across five wards.
+
+## The role
+
+You will plan and deliver clinical education for surgical nursing staff: induction for new starters, annual skills updates, and ward-based teaching after incidents and audits.
+
+## You must have
+
+- Current NMC registration (adult)
+- A nursing degree
+- At least 2 years' experience teaching, precepting or mentoring clinical staff
+- At least 3 years' post-registration experience in an acute surgical or medical-surgical setting
+- Experience using Epic, including supporting colleagues with it
+
+## It would help if you have
+
+- A master's degree in nursing or education, or to be working towards one
+- Basic Life Support instructor certification
+- Experience running sessions in a simulation lab
+- Experience writing teaching materials or guidelines
+
+## How to apply
+
+Send a CV and a cover letter of no more than one page to the Surgical Education Lead. Closing date 24 October 2026.