jd-analyserlisted

# JD Analyser **When to use:** the moment a job description arrives — pasted, URL, or screenshot — and before any CV or cover-letter skill writes a line. ## Why this exists A Power BI apprenticeship was once read wrong. Its *mission* bullets said "take ownership of Power BI developments of increasing complexity", so a Power-BI-specialist CV was drafted with DAX and data-modelling framing. The JD's actual requirement list was four lines long and did not mention Power BI at all. Its first mission line read: *"we will support your skills development on the Power BI tool."* They were hiring to train. The candidate caught it and called the draft delusional. Reading responsibilities as requirements inflates the CV, invites interview questions you cannot defend, and mis-positions you against the role. This skill exists to make that mistake structurally impossible. --- ## Step 0 — Quick score first Before anything else, output one line: `**<Company> — <Role>. MATCH X/5.** <one-sentence reason>` Then run the analysis. Do not build any document until the user gives a go-ahead. A fast, honest verdict is worth more to them than a slow, thorough one they did not ask for yet. ## Step 1 — Load ground truth 1. **`facts.md`** — the only source of claimable facts. Its **Evidence Index** carries per-skill caveats, and those caveats are binding. If it says *"SharePoint — not verified, never claim"*, then SharePoint never appears, no matter what the JD wants. 2. **`profile.yml`