skilldrop-cli 0.16.7 → 0.16.8

package/packs/career/skills/resume-tailor/SKILL.md

@@ -24,10 +24,15 @@ These four rules outrank the steps below.
 - **Write for the recruiter.** The file contains the resume and nothing else: no notes,
   no placeholders, no brackets, no mention of this skill.
 
-1. **Read both documents.** From the posting take the requirements in the employer's words,
-   required before preferred. From the resume take every job, date, title, qualification,
-   tool and number. If the person told you facts that are not in the resume, save them to
-   `notes.md` so they count as source material.
+1. **Read everything the person gave you.** From the posting take the requirements in the
+   employer's words, required before preferred. From the resume take every job, date, title,
+   qualification, tool and number. The person's own material also counts as a source: facts
+   they tell you, and any file they point to, such as a LinkedIn summary, a portfolio page
+   or a project's README. Save every fact that is not in the resume to `notes.md`, with
+   where it came from.
+
+   When the posting is a link, read the full text. If you cannot open it, say so and ask for
+   the text pasted in. Never rebuild a posting from what you remember of the employer.
 
 2. **Decide what leads.** For each requirement find the resume lines that answer it. Lines
    that answer a required item move up within their job; lines that answer nothing in this
@@ -50,16 +55,30 @@ These four rules outrank the steps below.
 4. **Write the summary last**, two or three lines at the top, built only from lines below it.
    Use the resume's own job title, not the posting's.
 
-5. **Keep it sendable.** Same sections and no more pages than the original; one
+5. **Work in the resume's own format.** Many resumes are built from a source file: Typst,
+   LaTeX, Word, a resume builder's data file. Find that file and edit a copy of it, named
+   `resume-<employer>` with the same extension, beside the original. Never edit the original
+   or anything else in its project. Keep the source valid: its imports, its escapes (`\$`,
+   `\&`), its structure. Build the copy the way the original is built when the tool is
+   there (`typst compile`, `pdflatex`), and look at the page count of what comes out. If you
+   cannot build it, say so and give the command; do not describe a PDF you did not make.
+
+6. **Treat the page count as a budget.** The result has no more pages than the original.
+   Anything you add is paid for with a cut, and every line you cut is reported in the reply
+   with a few words on why, so the person can ask for it back. Cut what answers nothing in
+   this posting first: older roles' detail before recent roles', a third example of the same
+   point before the only example of another.
+
+7. **Keep it sendable.** Same sections as the original; one
    column, standard headings, no tables, images or text boxes, so application systems can
    parse it. Keep the person's contact details, spelling convention and the word they use
    (resume or CV). Do not add a photo, date of birth or anything the original left out.
    Employment gaps stay as the original shows them.
 
-6. **Write a new file** beside the original, `resume-<employer>.md`, or the original's format
-   when you can produce it. Never overwrite the original.
+8. **Write a new file** beside the original: `resume-<employer>.md` for a text or Markdown
+   resume, or the copy from step 5. Never overwrite the original.
 
-7. **Run the check and resolve every line it prints:**
+9. **Run the check and resolve every line it prints:**
 
    ```
    python3 ${CLAUDE_SKILL_DIR}/scripts/claim_check.py resume-<employer>.md --source <original> --posting <posting>
@@ -71,9 +90,12 @@ These four rules outrank the steps below.
    source line that shows the same thing or take it out. Rerun until what remains is wording
    you can trace. If you cannot run it, do the same check by reading.
 
-8. **Reply in this order, briefly:**
+10. **Reply in this order, briefly:**
    - the file name, or the resume itself when you cannot write files;
    - **What changed**: four to six lines;
+   - **Cut**: each line you removed, with a few words on why. Say "nothing cut" when so;
+   - **Added from outside the resume**: each fact that came from what they told you or from
+     another file, with where it came from, for them to confirm before sending;
    - **Not claimed**: each thing the posting asks for that the resume doesn't support, so the
      person knows what the employer will notice;
    - **Would be stronger with**: up to five short questions whose answers you could add,
@@ -90,6 +112,8 @@ build one only from what the person tells you about their history, and say what
 - **The posting's required items are answered in the top half**, wherever the resume can.
 - **The file can be sent as it is**: no placeholders, notes or brackets.
 - **What the resume cannot claim is reported to the person, not papered over.**
+- **Nothing is cut silently and nothing from outside the resume is added silently.**
+- **The original file and its project are untouched.**
 
 ## When to use this skill
 
@@ -113,4 +137,8 @@ build one only from what the person tells you about their history, and say what
 - ❌ **Smoothing over a gap** by changing dates or dropping months.
 - ❌ **Rewriting everything.** A recruiter should still recognise the person's own career.
 - ❌ **A longer resume than the original.** Tailoring cuts.
+- ❌ **A silent cut.** The person finds out at interview that their favourite line is gone.
+- ❌ **Converting the format.** A Typst or Word resume handed back as Markdown loses the
+  design the person chose and cannot be sent.
+- ❌ **Claiming a build.** "The PDF is two pages" when no PDF was produced.
 - ❌ **Showing the machinery.** No mention of the check, this skill, or how the file was made.

package/packs/career/skills/resume-tailor/evals/evals.json

@@ -100,6 +100,34 @@
         "Running the kitchen on the head chef's days off, the costed weekly specials and the hotel banqueting are in the top half of the CV",
         "The reply tells him what the posting asks for that the CV does not claim, naming Level 3 Food Safety or the team size"
       ]
+    },
+    {
+      "id": 8,
+      "prompt": "Tailor my CV for this customer success job (posting.md). The CV is resume.typ - I build the PDF from that with Typst.",
+      "assertions": [
+        "The tailored CV is written as a new Typst file (for example resume-brightloop.typ) and resume.typ is left unchanged",
+        "The new file is still Typst source, keeping the page setup and the role helper; it is not converted to Markdown or plain text",
+        "'Hart & Lowe Software' and 'Research & Insights' appear exactly as in the original",
+        "The renewals line keeps 40 accounts and $1.2M and still says she supported renewals alongside the account managers; it does not say she owned or managed the renewals, a $1.2M book or a revenue target",
+        "Gainsight and a customer success certification are not claimed",
+        "Her job titles stay Support Team Lead, Support Agent then Senior Support Agent, and Customer Service Adviser, with the original dates",
+        "The reply lists each line that was cut, or says that nothing was cut",
+        "The reply does not state a page count or say a PDF was built unless the run actually produced a PDF file"
+      ]
+    },
+    {
+      "id": 9,
+      "prompt": "Tailor my CV (resume.md) to posting.md. linkedin-about.txt has a couple of things that aren't on my CV.",
+      "assertions": [
+        "The monthly onboarding webinar for new customers is added to the CV with the figures as she gave them: since January 2024, around 30 people",
+        "Co-chairing the Customer Advisory Board is added or offered, with 8 customers and twice a year unchanged if figures are given",
+        "The reply lists what was added from the LinkedIn text separately from the other changes, for her to confirm",
+        "She is not said to have owned renewals or carried a revenue target; the renewals line still says she supported them",
+        "Gainsight is not claimed",
+        "Three or more years in customer success or account management is not claimed, and her job titles are unchanged",
+        "The reading mentor volunteering is left out or kept as volunteering; it is not presented as customer experience",
+        "The reply names what the posting asks for that the CV cannot claim, such as owning renewals or Gainsight"
+      ]
     }
   ]
 }

package/packs/career/skills/resume-tailor/evals/files/8/posting.md

@@ -0,0 +1,25 @@
+# Customer Success Manager
+
+**Brightloop** · Manchester (hybrid) · £48,000 – £55,000
+
+Brightloop makes scheduling software for 900 dental and veterinary practices.
+
+## What you'll do
+
+- Own a book of 60 mid-market accounts and be accountable for their renewals
+- Run onboarding and training for new customers
+- Lead quarterly business reviews
+- Bring customer feedback to the product team
+
+## What we need
+
+- 3+ years in customer success or account management at a B2B software company
+- Experience owning renewals or a revenue target
+- Experience running customer onboarding or training
+- Confident with Salesforce and a customer success platform such as Gainsight
+- Experience leading or mentoring a small team
+
+## Nice to have
+
+- A customer success certification
+- Experience working with a product team on customer feedback

package/packs/career/skills/resume-tailor/evals/files/8/resume.typ

@@ -0,0 +1,31 @@
+#set page(paper: "a4", margin: 14mm)
+#set text(size: 10pt)
+#let role(title, org, dates) = grid(columns: (1fr, auto), [*#title* · #org], dates)
+
+= Nadia Rahman
+Manchester · nadia.rahman\@example.com · 07700 900612
+
+== Profile
+Support team lead with seven years in B2B software support.
+
+== Experience
+#role("Support Team Lead", "Hart & Lowe Software", "March 2022 – present")
+- Lead a team of 6 support agents covering 310 customer accounts.
+- Supported renewals for 40 accounts worth \$1.2M a year by joining the account managers' quarterly reviews.
+- Cut median first-response time from 9 hours to 3 hours by rewriting the triage rules in Zendesk.
+- Built the weekly ticket-trends report in Salesforce that the Research & Insights team uses to plan fixes.
+- Wrote 35 help-centre articles; self-service now resolves about a quarter of new tickets.
+- Hire and onboard new agents; 4 hired since 2023.
+
+#role("Support Agent, then Senior Support Agent", "Hart & Lowe Software", "June 2019 – March 2022")
+- Handled billing and integration tickets for mid-market customers.
+- Trained 5 new agents on the billing queue.
+
+#role("Customer Service Adviser", "Pennine Water", "September 2017 – May 2019")
+- Answered account and billing calls.
+
+== Education
+BA English Literature, University of Leeds, 2017
+
+== Tools
+Zendesk, Salesforce (reports & dashboards), Jira, Excel

package/packs/career/skills/resume-tailor/evals/files/9/linkedin-about.txt

@@ -0,0 +1,5 @@
+About
+
+I lead the support team at Hart & Lowe Software. Since January 2024 I've also run our monthly onboarding webinar for new customers, usually around 30 people on the call, and I co-chair the Customer Advisory Board with our Head of Product (8 customers, meets twice a year).
+
+Outside work I volunteer as a reading mentor at a primary school.

package/packs/career/skills/resume-tailor/evals/files/9/posting.md

@@ -0,0 +1,25 @@
+# Customer Success Manager
+
+**Brightloop** · Manchester (hybrid) · £48,000 – £55,000
+
+Brightloop makes scheduling software for 900 dental and veterinary practices.
+
+## What you'll do
+
+- Own a book of 60 mid-market accounts and be accountable for their renewals
+- Run onboarding and training for new customers
+- Lead quarterly business reviews
+- Bring customer feedback to the product team
+
+## What we need
+
+- 3+ years in customer success or account management at a B2B software company
+- Experience owning renewals or a revenue target
+- Experience running customer onboarding or training
+- Confident with Salesforce and a customer success platform such as Gainsight
+- Experience leading or mentoring a small team
+
+## Nice to have
+
+- A customer success certification
+- Experience working with a product team on customer feedback

package/packs/career/skills/resume-tailor/evals/files/9/resume.md

@@ -0,0 +1,35 @@
+# Nadia Rahman
+
+Manchester · nadia.rahman@example.com · 07700 900612
+
+## Profile
+
+Support team lead with seven years in B2B software support.
+
+## Experience
+
+**Support Team Lead** · Hart & Lowe Software · March 2022 – present
+
+- Lead a team of 6 support agents covering 310 customer accounts.
+- Supported renewals for 40 accounts worth $1.2M a year by joining the account managers' quarterly reviews.
+- Cut median first-response time from 9 hours to 3 hours by rewriting the triage rules in Zendesk.
+- Built the weekly ticket-trends report in Salesforce that the Research & Insights team uses to plan fixes.
+- Wrote 35 help-centre articles; self-service now resolves about a quarter of new tickets.
+- Hire and onboard new agents; 4 hired since 2023.
+
+**Support Agent, then Senior Support Agent** · Hart & Lowe Software · June 2019 – March 2022
+
+- Handled billing and integration tickets for mid-market customers.
+- Trained 5 new agents on the billing queue.
+
+**Customer Service Adviser** · Pennine Water · September 2017 – May 2019
+
+- Answered account and billing calls.
+
+## Education
+
+BA English Literature, University of Leeds, 2017
+
+## Tools
+
+Zendesk, Salesforce (reports & dashboards), Jira, Excel

package/packs/career/skills/resume-tailor/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "resume-tailor",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Tailor a resume or CV to one job posting without adding anything that isn't true: reorder, cut and reword what the person has already done so the posting's needs are answered first, keep every employer, title, date and number as it was, and report what the posting asks for that the resume cannot claim. A script lists every figure and name in the draft that the original doesn't contain. Works for any occupation and level. Use when the user says \"tailor my resume for this job\", \"adapt my CV to this posting\", \"rewrite my resume for this role\", or pastes a job description next to their resume.",
   "entrypoint": "SKILL.md",
   "deps": {

package/packs/career/skills/resume-tailor/scripts/claim_check.py

@@ -31,7 +31,7 @@ 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-z][A-Za-z0-9+#']*(?:\.[A-Za-z0-9]+)*")
+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")
@@ -73,8 +73,11 @@ def read(path):
 
 
 def clean(line):
-    """A line with its markdown removed, so `**Go**` and `Go` read the same."""
+    """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)
 
@@ -133,7 +136,7 @@ def phrases(line):
     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-z][A-Za-z0-9+#']*(?:\.[A-Za-z0-9]+)*|&|[.!?;:]\s|[,|·/()]|\s-\s", text + " ")
+    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:
@@ -200,7 +203,7 @@ def check(draft, sources, posting):
             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)
+                flat = " ".join(key(w) for w in words if w != "&")
                 if " " + flat + " " not in src_flat:
                     add("combination", " ".join(words), n, raw)
         if posting: