skilldrop-cli 0.16.6 → 0.16.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/catalogue.json +11 -1
- package/model-routing.json +16 -0
- package/package.json +1 -1
- package/packs/ai-engineering/skills/ai-usage-policy/evals/evals.json +30 -0
- package/packs/ai-engineering/skills/ai-usage-policy/evals/files/2/data-handling-sheet.md +18 -0
- package/packs/ai-engineering/skills/ai-usage-policy/evals/files/2/it-notes.md +31 -0
- package/packs/ai-engineering/skills/ai-usage-policy/evals/files/2/md-email.md +29 -0
- package/packs/api-builder/skills/tool-use-schema-writer/evals/evals.json +29 -0
- package/packs/api-builder/skills/tool-use-schema-writer/evals/files/2/book_appointment.ts +64 -0
- package/packs/career/loops/apply/LOOP.md +97 -0
- package/packs/career/loops/apply/evals/eval_queries.json +9 -0
- package/packs/career/loops/apply/evals/evals.json +27 -0
- package/packs/career/loops/apply/loop.json +52 -0
- package/packs/career/pack.json +77 -0
- package/packs/career/skills/application-form-answers/SKILL.md +146 -0
- package/packs/career/skills/application-form-answers/evals/eval_queries.json +34 -0
- package/packs/career/skills/application-form-answers/evals/evals.json +103 -0
- package/packs/career/skills/application-form-answers/evals/files/1/form.md +17 -0
- package/packs/career/skills/application-form-answers/evals/files/1/posting.md +20 -0
- package/packs/career/skills/application-form-answers/evals/files/1/resume.md +32 -0
- package/packs/career/skills/application-form-answers/evals/files/2/form.md +15 -0
- package/packs/career/skills/application-form-answers/evals/files/2/posting.md +21 -0
- package/packs/career/skills/application-form-answers/evals/files/2/resume.md +32 -0
- package/packs/career/skills/application-form-answers/evals/files/4/form.md +14 -0
- package/packs/career/skills/application-form-answers/evals/files/4/posting.md +25 -0
- package/packs/career/skills/application-form-answers/evals/files/4/resume.md +29 -0
- package/packs/career/skills/application-form-answers/evals/files/5/form.md +15 -0
- package/packs/career/skills/application-form-answers/evals/files/5/posting.md +18 -0
- package/packs/career/skills/application-form-answers/evals/files/5/resume.md +23 -0
- package/packs/career/skills/application-form-answers/evals/files/6/form.md +11 -0
- package/packs/career/skills/application-form-answers/evals/files/6/posting.md +28 -0
- package/packs/career/skills/application-form-answers/evals/files/6/resume.md +35 -0
- package/packs/career/skills/application-form-answers/evals/files/7/form.md +11 -0
- package/packs/career/skills/application-form-answers/evals/files/7/posting.md +19 -0
- package/packs/career/skills/application-form-answers/evals/files/7/resume.md +26 -0
- package/packs/career/skills/application-form-answers/manifest.json +31 -0
- package/packs/career/skills/cover-letter/SKILL.md +132 -0
- package/packs/career/skills/cover-letter/evals/eval_queries.json +34 -0
- package/packs/career/skills/cover-letter/evals/evals.json +100 -0
- package/packs/career/skills/cover-letter/evals/files/1/posting.md +28 -0
- package/packs/career/skills/cover-letter/evals/files/1/resume.md +35 -0
- package/packs/career/skills/cover-letter/evals/files/2/posting.md +20 -0
- package/packs/career/skills/cover-letter/evals/files/2/resume.md +32 -0
- package/packs/career/skills/cover-letter/evals/files/4/posting.md +19 -0
- package/packs/career/skills/cover-letter/evals/files/4/resume.md +26 -0
- package/packs/career/skills/cover-letter/evals/files/5/posting.md +21 -0
- package/packs/career/skills/cover-letter/evals/files/5/resume.md +32 -0
- package/packs/career/skills/cover-letter/evals/files/6/posting.md +25 -0
- package/packs/career/skills/cover-letter/evals/files/6/resume.md +29 -0
- package/packs/career/skills/cover-letter/evals/files/7/posting.md +18 -0
- package/packs/career/skills/cover-letter/evals/files/7/resume.md +23 -0
- package/packs/career/skills/cover-letter/manifest.json +37 -0
- package/packs/career/skills/cover-letter/scripts/claim_check.py +250 -0
- package/packs/career/skills/job-fit-analysis/SKILL.md +152 -0
- package/packs/career/skills/job-fit-analysis/evals/eval_queries.json +34 -0
- package/packs/career/skills/job-fit-analysis/evals/evals.json +102 -0
- package/packs/career/skills/job-fit-analysis/evals/files/1/posting.md +28 -0
- package/packs/career/skills/job-fit-analysis/evals/files/1/resume.md +35 -0
- package/packs/career/skills/job-fit-analysis/evals/files/2/posting.md +20 -0
- package/packs/career/skills/job-fit-analysis/evals/files/2/resume.md +32 -0
- package/packs/career/skills/job-fit-analysis/evals/files/4/posting.md +25 -0
- package/packs/career/skills/job-fit-analysis/evals/files/4/resume.md +29 -0
- package/packs/career/skills/job-fit-analysis/evals/files/5/posting.md +18 -0
- package/packs/career/skills/job-fit-analysis/evals/files/5/resume.md +23 -0
- package/packs/career/skills/job-fit-analysis/evals/files/6/linkedin-about.txt +5 -0
- package/packs/career/skills/job-fit-analysis/evals/files/6/posting.md +25 -0
- package/packs/career/skills/job-fit-analysis/evals/files/6/resume.md +35 -0
- package/packs/career/skills/job-fit-analysis/evals/files/7/resume.md +32 -0
- package/packs/career/skills/job-fit-analysis/manifest.json +31 -0
- package/packs/career/skills/resume-tailor/SKILL.md +144 -0
- package/packs/career/skills/resume-tailor/evals/eval_queries.json +34 -0
- package/packs/career/skills/resume-tailor/evals/evals.json +133 -0
- package/packs/career/skills/resume-tailor/evals/files/1/posting.md +26 -0
- package/packs/career/skills/resume-tailor/evals/files/1/resume.md +32 -0
- package/packs/career/skills/resume-tailor/evals/files/2/posting.md +19 -0
- package/packs/career/skills/resume-tailor/evals/files/2/resume.md +26 -0
- package/packs/career/skills/resume-tailor/evals/files/3/posting.md +21 -0
- package/packs/career/skills/resume-tailor/evals/files/3/resume.md +32 -0
- package/packs/career/skills/resume-tailor/evals/files/4/posting.md +28 -0
- package/packs/career/skills/resume-tailor/evals/files/4/resume.md +35 -0
- package/packs/career/skills/resume-tailor/evals/files/5/posting.md +20 -0
- package/packs/career/skills/resume-tailor/evals/files/5/resume.md +32 -0
- package/packs/career/skills/resume-tailor/evals/files/6/posting.md +25 -0
- package/packs/career/skills/resume-tailor/evals/files/6/resume.md +29 -0
- package/packs/career/skills/resume-tailor/evals/files/7/posting.md +18 -0
- package/packs/career/skills/resume-tailor/evals/files/7/resume.md +23 -0
- package/packs/career/skills/resume-tailor/evals/files/8/posting.md +25 -0
- package/packs/career/skills/resume-tailor/evals/files/8/resume.typ +31 -0
- package/packs/career/skills/resume-tailor/evals/files/9/linkedin-about.txt +5 -0
- package/packs/career/skills/resume-tailor/evals/files/9/posting.md +25 -0
- package/packs/career/skills/resume-tailor/evals/files/9/resume.md +35 -0
- package/packs/career/skills/resume-tailor/manifest.json +37 -0
- package/packs/career/skills/resume-tailor/scripts/claim_check.py +250 -0
- package/packs/data-analytics/skills/metric-definition/evals/evals.json +30 -0
- package/packs/data-analytics/skills/metric-definition/evals/files/2/tables.md +42 -0
- package/packs/data-analytics/skills/metric-definition/evals/files/2/thread.md +40 -0
- package/packs/dev-team/skills/contribution-wizard/evals/evals.json +29 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/AGENTS.md +9 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/CATALOG.md +18 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/CONTRIBUTING.md +45 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/OWNERS.md +7 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/INSTRUCTIONS.md +20 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/skill.yaml +11 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/detention-claim-letter/tests/cases.yaml +25 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/INSTRUCTIONS.md +20 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/skill.yaml +8 -0
- package/packs/dev-team/skills/contribution-wizard/evals/files/2/skills/rate-con-extractor/tests/cases.yaml +32 -0
- package/packs/dev-team/skills/devils-advocate/evals/evals.json +29 -0
- package/packs/dev-team/skills/devils-advocate/evals/files/2/signups.py +116 -0
- package/packs/dev-team/skills/devils-advocate/evals/files/2/test_signups.py +69 -0
- package/packs/dev-team/skills/release-notes/evals/evals.json +29 -0
- package/packs/dev-team/skills/release-notes/evals/files/2/commits.txt +35 -0
- package/packs/research/skills/source-synthesis/evals/evals.json +30 -0
- package/packs/research/skills/source-synthesis/evals/files/2/badge-data.md +27 -0
- package/packs/research/skills/source-synthesis/evals/files/2/director-email.md +16 -0
- package/packs/research/skills/source-synthesis/evals/files/2/exit-interviews.md +17 -0
- package/packs/research/skills/source-synthesis/evals/files/2/practice-weekly-article.md +21 -0
- package/packs/research/skills/source-synthesis/evals/files/2/staff-survey-summary.md +41 -0
- package/packs/solution-architect/skills/db-schema-design/evals/evals.json +29 -0
- package/packs/solution-architect/skills/db-schema-design/evals/files/2/current_tables.sql +29 -0
- package/packs/solution-architect/skills/db-schema-design/evals/files/2/notes.md +53 -0
- package/packs/solution-architect/skills/design-doc/evals/evals.json +29 -0
- package/packs/solution-architect/skills/design-doc/evals/files/2/brief.md +18 -0
- package/packs/solution-architect/skills/design-doc/evals/files/2/eng-notes.md +30 -0
- package/packs/solution-architect/skills/tech-comparison-matrix/evals/evals.json +29 -0
- package/packs/solution-architect/skills/tech-comparison-matrix/evals/files/2/requirements.md +20 -0
- package/packs/solution-architect/skills/tech-comparison-matrix/evals/files/2/vendor-notes.md +29 -0
- package/packs/sre-oncall/skills/postmortem-generator/evals/evals.json +30 -0
- package/packs/sre-oncall/skills/postmortem-generator/evals/files/2/pager-export.txt +22 -0
- package/packs/sre-oncall/skills/postmortem-generator/evals/files/2/slack-thread.txt +28 -0
- package/packs/stakeholder-comms/skills/guide-builder/evals/evals.json +29 -0
- package/packs/stakeholder-comms/skills/guide-builder/evals/files/2/api-notes.md +44 -0
- package/packs/stakeholder-comms/skills/guide-builder/evals/files/2/sample-booking.json +19 -0
- package/profiles.json +2 -2
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Maya Okafor, RN, BSN
|
|
2
|
+
|
|
3
|
+
Leeds, UK · maya.okafor@example.com · 07700 900142
|
|
4
|
+
|
|
5
|
+
## Profile
|
|
6
|
+
|
|
7
|
+
Registered nurse with six years on an acute medical-surgical ward. Charge nurse on rotation since 2023.
|
|
8
|
+
|
|
9
|
+
## Experience
|
|
10
|
+
|
|
11
|
+
**Staff Nurse, then Charge Nurse (rotating)** — Ward 14 Medical-Surgical, Aldermoor Hospital
|
|
12
|
+
August 2020 – present
|
|
13
|
+
|
|
14
|
+
- Care for up to 6 post-operative and acute medical patients per shift on a 28-bed ward.
|
|
15
|
+
- Take charge of the ward on rotation since March 2023: staffing, bed flow and escalation.
|
|
16
|
+
- Precept newly qualified nurses through their first 12 weeks; 9 preceptees so far.
|
|
17
|
+
- Wrote the ward's one-page guide to the sepsis screening tool and walked each shift through it at handover.
|
|
18
|
+
- Document in Cerner; ward superuser for the Cerner medication administration module since 2022.
|
|
19
|
+
- Member of the falls prevention working group.
|
|
20
|
+
|
|
21
|
+
**Healthcare Assistant** — Rowan Court Care Home
|
|
22
|
+
June 2017 – July 2020 (part time during degree)
|
|
23
|
+
|
|
24
|
+
- Personal care, observations and mealtime support for 30 residents.
|
|
25
|
+
|
|
26
|
+
## Education and registration
|
|
27
|
+
|
|
28
|
+
- BSc (Hons) Adult Nursing, University of Bradford, 2020
|
|
29
|
+
- NMC registered nurse (adult), registered 2020
|
|
30
|
+
- Mentorship and Assessment in Practice module, 2022
|
|
31
|
+
- Basic Life Support provider, renewed January 2026
|
|
32
|
+
|
|
33
|
+
## Other
|
|
34
|
+
|
|
35
|
+
- Volunteer first aider, Leeds 10K, 2023 and 2024
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
Operations Coordinator
|
|
2
|
+
Kestrel Freight Solutions - Columbus, OH - Full time
|
|
3
|
+
|
|
4
|
+
About the job
|
|
5
|
+
The Operations Coordinator keeps our cross-dock running to plan: scheduling inbound and outbound loads, coordinating with carriers, and reporting daily performance to the Operations Manager.
|
|
6
|
+
|
|
7
|
+
Requirements
|
|
8
|
+
- Bachelor's degree required
|
|
9
|
+
- 3+ years in warehouse or logistics operations
|
|
10
|
+
- Experience supervising or coordinating teams of 20 or more
|
|
11
|
+
- Advanced Excel (pivot tables, VLOOKUP)
|
|
12
|
+
- Experience with SAP Extended Warehouse Management
|
|
13
|
+
- Strong safety record and knowledge of OSHA requirements
|
|
14
|
+
|
|
15
|
+
Preferred
|
|
16
|
+
- Lean Six Sigma Green Belt
|
|
17
|
+
- Forklift certification
|
|
18
|
+
- Bilingual English/Spanish
|
|
19
|
+
|
|
20
|
+
Pay: $58,000 - $66,000. Day shift, Monday to Friday.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
Daniel Reyes
|
|
2
|
+
Columbus, OH | daniel.reyes@example.com | (614) 555-0137
|
|
3
|
+
|
|
4
|
+
SUMMARY
|
|
5
|
+
Warehouse shift supervisor with 8 years at a regional grocery distribution center.
|
|
6
|
+
|
|
7
|
+
EXPERIENCE
|
|
8
|
+
|
|
9
|
+
Shift Supervisor, Hartwell Foods Distribution Center, Columbus, OH
|
|
10
|
+
March 2021 - Present
|
|
11
|
+
- Supervise a second-shift team of 12 pickers and loaders.
|
|
12
|
+
- Build the weekly shift roster in Excel and track attendance.
|
|
13
|
+
- Zero lost-time incidents on my shift for the last 14 months.
|
|
14
|
+
- Run the start-of-shift safety briefing and train new hires on the pallet jack and the scanner.
|
|
15
|
+
- Work with the transport office to reorder loading when trucks arrive late.
|
|
16
|
+
- Use the company's in-house warehouse system to release pick waves and fix inventory mismatches.
|
|
17
|
+
|
|
18
|
+
Order Picker, then Forklift Operator, Hartwell Foods Distribution Center
|
|
19
|
+
June 2018 - March 2021
|
|
20
|
+
- Picked and loaded outbound grocery orders; moved to forklift after one year.
|
|
21
|
+
- Picked as trainer for new forklift operators in 2020.
|
|
22
|
+
|
|
23
|
+
Stock Associate, Brightway Home Improvement, Dayton, OH
|
|
24
|
+
2016 - 2018
|
|
25
|
+
|
|
26
|
+
EDUCATION
|
|
27
|
+
Westland High School, diploma, 2015
|
|
28
|
+
Columbus State Community College, 18 credits toward an associate degree in business (2019-2020, not completed)
|
|
29
|
+
|
|
30
|
+
CERTIFICATIONS
|
|
31
|
+
OSHA forklift operator certification, renewed 2025
|
|
32
|
+
First Aid/CPR, 2025
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Finance Analyst
|
|
2
|
+
|
|
3
|
+
**Orrell Leisure Group** · Birmingham · £36,000 – £40,000
|
|
4
|
+
|
|
5
|
+
Orrell runs 22 gyms across the Midlands. The Finance Analyst reports to the Financial Controller and produces the monthly management pack for site managers.
|
|
6
|
+
|
|
7
|
+
## What you'll do
|
|
8
|
+
|
|
9
|
+
- Build the monthly management accounts pack: variance to budget by site, with commentary
|
|
10
|
+
- Own the month-end close for payroll and utilities accruals
|
|
11
|
+
- Maintain the site-level budget model and reforecast each quarter
|
|
12
|
+
- Build dashboards in Power BI for the operations team
|
|
13
|
+
|
|
14
|
+
## What we need
|
|
15
|
+
|
|
16
|
+
- Part-qualified ACCA or CIMA, or AAT Level 4 complete
|
|
17
|
+
- At least 2 years in a management accounts or analyst role
|
|
18
|
+
- Advanced Excel (pivot tables, lookups, modelling)
|
|
19
|
+
- Experience preparing variance analysis and budget commentary
|
|
20
|
+
- Experience with Power BI or a similar reporting tool
|
|
21
|
+
|
|
22
|
+
## Nice to have
|
|
23
|
+
|
|
24
|
+
- Experience in a multi-site business
|
|
25
|
+
- Experience with Sage or NetSuite
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# Grace Mbeki
|
|
2
|
+
|
|
3
|
+
Birmingham · grace.mbeki@example.com · 07700 900455
|
|
4
|
+
|
|
5
|
+
## Work
|
|
6
|
+
|
|
7
|
+
**Accounts Payable Clerk** — Halden Building Supplies, Birmingham
|
|
8
|
+
February 2021 – present
|
|
9
|
+
|
|
10
|
+
- Process around 400 supplier invoices a month in Sage 200, matching each to its purchase order and delivery note.
|
|
11
|
+
- Reconcile 60 supplier statements each month and chase the differences.
|
|
12
|
+
- Prepare the fortnightly payment run for the Finance Manager to approve.
|
|
13
|
+
- Built an Excel workbook (pivot tables and lookups) that lists invoices on hold by reason; the purchasing team now uses it every week.
|
|
14
|
+
- Support month-end by posting accruals for goods received and not yet invoiced.
|
|
15
|
+
|
|
16
|
+
**Finance Administrator** — Corrin Dental Group, Solihull
|
|
17
|
+
September 2018 – January 2021
|
|
18
|
+
|
|
19
|
+
- Raised sales invoices, banked receipts and kept the petty cash for four practices.
|
|
20
|
+
|
|
21
|
+
## Qualifications
|
|
22
|
+
|
|
23
|
+
- AAT Level 3 Diploma in Accounting, 2020
|
|
24
|
+
- Studying AAT Level 4; two of five units passed
|
|
25
|
+
- A levels: Mathematics (B), Economics (C), 2018
|
|
26
|
+
|
|
27
|
+
## Tools
|
|
28
|
+
|
|
29
|
+
Sage 200, Excel, Microsoft Teams
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
Head Chef
|
|
2
|
+
Calder House Hotel, Peebles - 62 bedrooms, restaurant and events
|
|
3
|
+
|
|
4
|
+
You will lead the kitchen for our 120-cover restaurant and for weddings and events of up to 180 guests.
|
|
5
|
+
|
|
6
|
+
Requirements
|
|
7
|
+
- Level 3 Food Safety (Supervising Food Safety in Catering)
|
|
8
|
+
- Experience as a head chef, or as a sous chef with full responsibility for a kitchen
|
|
9
|
+
- Experience leading a team of 12 or more
|
|
10
|
+
- Menu design and costing to a gross profit target of 70%
|
|
11
|
+
- Experience of banqueting and events
|
|
12
|
+
- Stock control and supplier management
|
|
13
|
+
|
|
14
|
+
Desirable
|
|
15
|
+
- Experience in a hotel kitchen
|
|
16
|
+
- Experience with Procure Wizard or a similar ordering system
|
|
17
|
+
|
|
18
|
+
Salary 48,000 pounds plus tronc. Live-in available.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
LEO TANAKA
|
|
2
|
+
Edinburgh | leo.tanaka@example.com | 07700 900271
|
|
3
|
+
|
|
4
|
+
Sous Chef, The Larder at Queensgate (80-cover restaurant), Edinburgh
|
|
5
|
+
May 2022 - present
|
|
6
|
+
- Run the kitchen on the head chef's two days off each week.
|
|
7
|
+
- Lead a brigade of 6 on service.
|
|
8
|
+
- Write and cost the weekly specials; do the fish and vegetable orders.
|
|
9
|
+
- Trained 3 commis chefs, one now a chef de partie.
|
|
10
|
+
- Keep the allergen matrix up to date for every menu change.
|
|
11
|
+
- Environmental health inspection in 2025: rated 5.
|
|
12
|
+
|
|
13
|
+
Chef de Partie, Harbour Rooms Hotel, Leith
|
|
14
|
+
March 2019 - April 2022
|
|
15
|
+
- Ran the sauce section; covered banqueting for weddings in summer.
|
|
16
|
+
|
|
17
|
+
Commis Chef, Harbour Rooms Hotel, Leith
|
|
18
|
+
August 2017 - March 2019
|
|
19
|
+
|
|
20
|
+
TRAINING
|
|
21
|
+
SVQ Level 3 Professional Cookery, Edinburgh College, 2019
|
|
22
|
+
Level 2 Food Safety and Hygiene for Catering, renewed 2024
|
|
23
|
+
Allergen awareness training, 2024
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
About
|
|
2
|
+
|
|
3
|
+
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).
|
|
4
|
+
|
|
5
|
+
Outside work I volunteer as a reading mentor at a primary school.
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Customer Success Manager
|
|
2
|
+
|
|
3
|
+
**Brightloop** · Manchester (hybrid) · £48,000 – £55,000
|
|
4
|
+
|
|
5
|
+
Brightloop makes scheduling software for 900 dental and veterinary practices.
|
|
6
|
+
|
|
7
|
+
## What you'll do
|
|
8
|
+
|
|
9
|
+
- Own a book of 60 mid-market accounts and be accountable for their renewals
|
|
10
|
+
- Run onboarding and training for new customers
|
|
11
|
+
- Lead quarterly business reviews
|
|
12
|
+
- Bring customer feedback to the product team
|
|
13
|
+
|
|
14
|
+
## What we need
|
|
15
|
+
|
|
16
|
+
- 3+ years in customer success or account management at a B2B software company
|
|
17
|
+
- Experience owning renewals or a revenue target
|
|
18
|
+
- Experience running customer onboarding or training
|
|
19
|
+
- Confident with Salesforce and a customer success platform such as Gainsight
|
|
20
|
+
- Experience leading or mentoring a small team
|
|
21
|
+
|
|
22
|
+
## Nice to have
|
|
23
|
+
|
|
24
|
+
- A customer success certification
|
|
25
|
+
- Experience working with a product team on customer feedback
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Nadia Rahman
|
|
2
|
+
|
|
3
|
+
Manchester · nadia.rahman@example.com · 07700 900612
|
|
4
|
+
|
|
5
|
+
## Profile
|
|
6
|
+
|
|
7
|
+
Support team lead with seven years in B2B software support.
|
|
8
|
+
|
|
9
|
+
## Experience
|
|
10
|
+
|
|
11
|
+
**Support Team Lead** · Hart & Lowe Software · March 2022 – present
|
|
12
|
+
|
|
13
|
+
- Lead a team of 6 support agents covering 310 customer accounts.
|
|
14
|
+
- Supported renewals for 40 accounts worth $1.2M a year by joining the account managers' quarterly reviews.
|
|
15
|
+
- Cut median first-response time from 9 hours to 3 hours by rewriting the triage rules in Zendesk.
|
|
16
|
+
- Built the weekly ticket-trends report in Salesforce that the Research & Insights team uses to plan fixes.
|
|
17
|
+
- Wrote 35 help-centre articles; self-service now resolves about a quarter of new tickets.
|
|
18
|
+
- Hire and onboard new agents; 4 hired since 2023.
|
|
19
|
+
|
|
20
|
+
**Support Agent, then Senior Support Agent** · Hart & Lowe Software · June 2019 – March 2022
|
|
21
|
+
|
|
22
|
+
- Handled billing and integration tickets for mid-market customers.
|
|
23
|
+
- Trained 5 new agents on the billing queue.
|
|
24
|
+
|
|
25
|
+
**Customer Service Adviser** · Pennine Water · September 2017 – May 2019
|
|
26
|
+
|
|
27
|
+
- Answered account and billing calls.
|
|
28
|
+
|
|
29
|
+
## Education
|
|
30
|
+
|
|
31
|
+
BA English Literature, University of Leeds, 2017
|
|
32
|
+
|
|
33
|
+
## Tools
|
|
34
|
+
|
|
35
|
+
Zendesk, Salesforce (reports & dashboards), Jira, Excel
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Tom Lindqvist
|
|
2
|
+
|
|
3
|
+
Senior Backend Engineer · Stockholm · tom.lindqvist@example.com
|
|
4
|
+
|
|
5
|
+
## Experience
|
|
6
|
+
|
|
7
|
+
### Senior Backend Engineer — Fjordcart (e-commerce platform), 2021 – present
|
|
8
|
+
|
|
9
|
+
- Tech lead for the checkout team (4 engineers).
|
|
10
|
+
- Rewrote the order service from a Python monolith module into three Go services.
|
|
11
|
+
- Cut checkout API p95 latency from 800 ms to 300 ms by removing synchronous calls to the inventory service.
|
|
12
|
+
- Moved order events onto Kafka; the warehouse and email systems now consume the same stream.
|
|
13
|
+
- Run the services on AWS ECS with Terraform; on the on-call rota, one week in five.
|
|
14
|
+
- Integrated two payment providers through their hosted checkout APIs.
|
|
15
|
+
|
|
16
|
+
### Backend Engineer — Nordlys Media, 2018 – 2021
|
|
17
|
+
|
|
18
|
+
- Built the subscription billing service in Python and PostgreSQL.
|
|
19
|
+
- Reduced failed renewals by adding a retry schedule for declined cards.
|
|
20
|
+
- Mentored two junior engineers.
|
|
21
|
+
|
|
22
|
+
### Junior Developer — Brevik Consulting, 2016 – 2018
|
|
23
|
+
|
|
24
|
+
- Client projects in Python and Django.
|
|
25
|
+
|
|
26
|
+
## Skills
|
|
27
|
+
|
|
28
|
+
Go, Python, PostgreSQL, Kafka, AWS (ECS, RDS, SQS), Terraform, Datadog
|
|
29
|
+
|
|
30
|
+
## Education
|
|
31
|
+
|
|
32
|
+
MSc Computer Science, KTH Royal Institute of Technology, 2016
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "job-fit-analysis",
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"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.",
|
|
5
|
+
"entrypoint": "SKILL.md",
|
|
6
|
+
"deps": {
|
|
7
|
+
"npm": [],
|
|
8
|
+
"pip": []
|
|
9
|
+
},
|
|
10
|
+
"env": {
|
|
11
|
+
"required": [],
|
|
12
|
+
"optional": []
|
|
13
|
+
},
|
|
14
|
+
"related": [
|
|
15
|
+
"cover-letter",
|
|
16
|
+
"doc-critique",
|
|
17
|
+
"resume-tailor"
|
|
18
|
+
],
|
|
19
|
+
"tags": [
|
|
20
|
+
"job-search",
|
|
21
|
+
"resume",
|
|
22
|
+
"cv",
|
|
23
|
+
"job-posting",
|
|
24
|
+
"fit",
|
|
25
|
+
"career"
|
|
26
|
+
],
|
|
27
|
+
"model": {
|
|
28
|
+
"tier": "standard",
|
|
29
|
+
"rationale": "Matches a posting's requirements to resume lines and reports the gaps. The rule is mechanical: no line in the resume, no credit."
|
|
30
|
+
}
|
|
31
|
+
}
|
|
@@ -0,0 +1,144 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: resume-tailor
|
|
3
|
+
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.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# resume-tailor
|
|
7
|
+
|
|
8
|
+
You rewrite one person's resume for one job. Everything in the result was already true and
|
|
9
|
+
already theirs: you choose what leads, what is cut and how it is worded. You do not add an
|
|
10
|
+
employer, a title, a tool, a certificate or a number. The person signs this document and is
|
|
11
|
+
questioned on it at interview, so a claim they cannot back costs them the job later. It works
|
|
12
|
+
the same for any occupation; the posting sets the priorities and the resume sets the limits.
|
|
13
|
+
|
|
14
|
+
## How to respond
|
|
15
|
+
|
|
16
|
+
These four rules outrank the steps below.
|
|
17
|
+
|
|
18
|
+
- **Answer first.** The reply opens with the tailored resume, or the name of the file it is
|
|
19
|
+
in. No note about how it was made comes before it.
|
|
20
|
+
- **Use only what you were given.** The source is the person's resume plus anything they
|
|
21
|
+
told you. The posting says what to emphasise; it is never a source of facts about them.
|
|
22
|
+
- **Deliver from what you have.** A thin resume gets a tight, honest one-page result, not
|
|
23
|
+
questions before any work is done.
|
|
24
|
+
- **Write for the recruiter.** The file contains the resume and nothing else: no notes,
|
|
25
|
+
no placeholders, no brackets, no mention of this skill.
|
|
26
|
+
|
|
27
|
+
1. **Read everything the person gave you.** From the posting take the requirements in the
|
|
28
|
+
employer's words, required before preferred. From the resume take every job, date, title,
|
|
29
|
+
qualification, tool and number. The person's own material also counts as a source: facts
|
|
30
|
+
they tell you, and any file they point to, such as a LinkedIn summary, a portfolio page
|
|
31
|
+
or a project's README. Save every fact that is not in the resume to `notes.md`, with
|
|
32
|
+
where it came from.
|
|
33
|
+
|
|
34
|
+
When the posting is a link, read the full text. If you cannot open it, say so and ask for
|
|
35
|
+
the text pasted in. Never rebuild a posting from what you remember of the employer.
|
|
36
|
+
|
|
37
|
+
2. **Decide what leads.** For each requirement find the resume lines that answer it. Lines
|
|
38
|
+
that answer a required item move up within their job; lines that answer nothing in this
|
|
39
|
+
posting are shortened or cut. Jobs stay in the order the resume had them, and none is
|
|
40
|
+
removed if removing it would open a gap in the dates. A fact the person told you that
|
|
41
|
+
answers the posting goes where a recruiter sees it early, not at the bottom.
|
|
42
|
+
|
|
43
|
+
3. **Reword, within these limits:**
|
|
44
|
+
- **Fixed:** employer names, job titles, dates, qualifications, licences, and every
|
|
45
|
+
number. Copy them exactly. "Teacher" does not become "Learning Designer".
|
|
46
|
+
- **Free:** word order, verbs, which detail comes first, and using the posting's term for
|
|
47
|
+
something the resume already shows. "Built the weekly roster" may become "scheduled a
|
|
48
|
+
team of 12" because the resume says both things.
|
|
49
|
+
- **Never:** a tool, method, platform or certificate the resume doesn't name; a bigger
|
|
50
|
+
team, budget or scope; a result or percentage the resume doesn't give; a length of time
|
|
51
|
+
the dates of that job don't add up to; "familiar with" as a way to list something unused.
|
|
52
|
+
- A similar tool stays itself: ECS is not Kubernetes, Cerner is not Epic. You may name
|
|
53
|
+
the category it belongs to ("container orchestration on AWS ECS").
|
|
54
|
+
|
|
55
|
+
4. **Write the summary last**, two or three lines at the top, built only from lines below it.
|
|
56
|
+
Use the resume's own job title, not the posting's.
|
|
57
|
+
|
|
58
|
+
5. **Work in the resume's own format.** Many resumes are built from a source file: Typst,
|
|
59
|
+
LaTeX, Word, a resume builder's data file. Find that file and edit a copy of it, named
|
|
60
|
+
`resume-<employer>` with the same extension, beside the original. Never edit the original
|
|
61
|
+
or anything else in its project. Keep the source valid: its imports, its escapes (`\$`,
|
|
62
|
+
`\&`), its structure. Build the copy the way the original is built when the tool is
|
|
63
|
+
there (`typst compile`, `pdflatex`), and look at the page count of what comes out. If you
|
|
64
|
+
cannot build it, say so and give the command; do not describe a PDF you did not make.
|
|
65
|
+
|
|
66
|
+
6. **Treat the page count as a budget.** The result has no more pages than the original.
|
|
67
|
+
Anything you add is paid for with a cut, and every line you cut is reported in the reply
|
|
68
|
+
with a few words on why, so the person can ask for it back. Cut what answers nothing in
|
|
69
|
+
this posting first: older roles' detail before recent roles', a third example of the same
|
|
70
|
+
point before the only example of another.
|
|
71
|
+
|
|
72
|
+
7. **Keep it sendable.** Same sections as the original; one
|
|
73
|
+
column, standard headings, no tables, images or text boxes, so application systems can
|
|
74
|
+
parse it. Keep the person's contact details, spelling convention and the word they use
|
|
75
|
+
(resume or CV). Do not add a photo, date of birth or anything the original left out.
|
|
76
|
+
Employment gaps stay as the original shows them.
|
|
77
|
+
|
|
78
|
+
8. **Write a new file** beside the original: `resume-<employer>.md` for a text or Markdown
|
|
79
|
+
resume, or the copy from step 5. Never overwrite the original.
|
|
80
|
+
|
|
81
|
+
9. **Run the check and resolve every line it prints:**
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
python3 ${CLAUDE_SKILL_DIR}/scripts/claim_check.py resume-<employer>.md --source <original> --posting <posting>
|
|
85
|
+
```
|
|
86
|
+
In non-Claude IDEs the same file is at a plain relative path:
|
|
87
|
+
`python3 scripts/claim_check.py resume-<employer>.md --source <original> --posting <posting>`.
|
|
88
|
+
Add `--source notes.md` when you saved notes. It lists figures and names the original
|
|
89
|
+
doesn't contain, and wording shared only with the posting. For each line, point to the
|
|
90
|
+
source line that shows the same thing or take it out. Rerun until what remains is wording
|
|
91
|
+
you can trace. If you cannot run it, do the same check by reading.
|
|
92
|
+
|
|
93
|
+
10. **Reply in this order, briefly:**
|
|
94
|
+
- the file name, or the resume itself when you cannot write files;
|
|
95
|
+
- **What changed**: four to six lines;
|
|
96
|
+
- **Cut**: each line you removed, with a few words on why. Say "nothing cut" when so;
|
|
97
|
+
- **Added from outside the resume**: each fact that came from what they told you or from
|
|
98
|
+
another file, with where it came from, for them to confirm before sending;
|
|
99
|
+
- **Not claimed**: each thing the posting asks for that the resume doesn't support, so the
|
|
100
|
+
person knows what the employer will notice;
|
|
101
|
+
- **Would be stronger with**: up to five short questions whose answers you could add,
|
|
102
|
+
such as a missing number, or a tool they may have used and not listed.
|
|
103
|
+
|
|
104
|
+
**With a resume and no posting**, tailor to the role the person names and say the posting
|
|
105
|
+
would sharpen it; if they name no role, ask for the posting in one line. **With no resume**,
|
|
106
|
+
build one only from what the person tells you about their history, and say what is missing.
|
|
107
|
+
|
|
108
|
+
## Quality bar
|
|
109
|
+
|
|
110
|
+
- **Every employer, title, date, qualification and number matches the original exactly.**
|
|
111
|
+
- **Nothing is in the result that is not in the original or the person's own words.**
|
|
112
|
+
- **The posting's required items are answered in the top half**, wherever the resume can.
|
|
113
|
+
- **The file can be sent as it is**: no placeholders, notes or brackets.
|
|
114
|
+
- **What the resume cannot claim is reported to the person, not papered over.**
|
|
115
|
+
- **Nothing is cut silently and nothing from outside the resume is added silently.**
|
|
116
|
+
- **The original file and its project are untouched.**
|
|
117
|
+
|
|
118
|
+
## When to use this skill
|
|
119
|
+
|
|
120
|
+
- ✅ Adapting a resume or CV to a specific posting, in any field
|
|
121
|
+
- ✅ Producing versions of one resume for several different roles
|
|
122
|
+
- ✅ A career change, where the same history must answer a different job's needs
|
|
123
|
+
|
|
124
|
+
## When NOT to use this skill
|
|
125
|
+
|
|
126
|
+
- ❌ Deciding whether to apply at all. Use `job-fit-analysis`.
|
|
127
|
+
- ❌ Writing the covering letter. Use `cover-letter`.
|
|
128
|
+
- ❌ Reviewing a resume's quality with no job in mind. Use `doc-critique`.
|
|
129
|
+
|
|
130
|
+
## Anti-patterns to avoid
|
|
131
|
+
|
|
132
|
+
- ❌ **Keyword stuffing.** Listing the posting's tools in the skills line because a filter
|
|
133
|
+
looks for them. It reads as a lie at interview.
|
|
134
|
+
- ❌ **Inventing a metric.** "Improved efficiency by 30%" where the resume gave no figure.
|
|
135
|
+
- ❌ **Promoting the title** to match the posting.
|
|
136
|
+
- ❌ **Placeholders in the file**: "[X%]", "[add metric]". Questions go in the reply.
|
|
137
|
+
- ❌ **Smoothing over a gap** by changing dates or dropping months.
|
|
138
|
+
- ❌ **Rewriting everything.** A recruiter should still recognise the person's own career.
|
|
139
|
+
- ❌ **A longer resume than the original.** Tailoring cuts.
|
|
140
|
+
- ❌ **A silent cut.** The person finds out at interview that their favourite line is gone.
|
|
141
|
+
- ❌ **Converting the format.** A Typst or Word resume handed back as Markdown loses the
|
|
142
|
+
design the person chose and cannot be sent.
|
|
143
|
+
- ❌ **Claiming a build.** "The PDF is two pages" when no PDF was produced.
|
|
144
|
+
- ❌ **Showing the machinery.** No mention of the check, this skill, or how the file was made.
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
[
|
|
2
|
+
{
|
|
3
|
+
"query": "Tailor my resume for this job posting",
|
|
4
|
+
"should_trigger": true
|
|
5
|
+
},
|
|
6
|
+
{
|
|
7
|
+
"query": "Adapt my CV to this job description",
|
|
8
|
+
"should_trigger": true
|
|
9
|
+
},
|
|
10
|
+
{
|
|
11
|
+
"query": "Rewrite my resume so it fits this product manager role",
|
|
12
|
+
"should_trigger": true
|
|
13
|
+
},
|
|
14
|
+
{
|
|
15
|
+
"query": "I'm changing careers, can you rework my CV for this posting?",
|
|
16
|
+
"should_trigger": true
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"query": "Am I a good fit for this job?",
|
|
20
|
+
"should_trigger": false
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"query": "Write a cover letter to go with my application",
|
|
24
|
+
"should_trigger": false
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"query": "Give my resume a general critique",
|
|
28
|
+
"should_trigger": false
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"query": "Convert my resume from Markdown to Word",
|
|
32
|
+
"should_trigger": false
|
|
33
|
+
}
|
|
34
|
+
]
|
|
@@ -0,0 +1,133 @@
|
|
|
1
|
+
{
|
|
2
|
+
"skill_name": "resume-tailor",
|
|
3
|
+
"evals": [
|
|
4
|
+
{
|
|
5
|
+
"id": 1,
|
|
6
|
+
"prompt": "Tailor my resume (resume.md) for this staff engineer role (posting.md).",
|
|
7
|
+
"assertions": [
|
|
8
|
+
"Kubernetes is not claimed as experience or listed as a skill; AWS ECS is still named",
|
|
9
|
+
"The team he led stays at 4 engineers; the resume does not say 8, 20 or 'teams of' engineers",
|
|
10
|
+
"The latency result stays as 800 ms to 300 ms, and no percentage or other figure is added that the original does not contain (for example for failed renewals or availability)",
|
|
11
|
+
"Rust, PCI DSS and ledger design are not listed as his skills or experience",
|
|
12
|
+
"All three jobs keep their original employer, title and dates (Senior Backend Engineer 2021 to present, Backend Engineer 2018 to 2021, Junior Developer 2016 to 2018), and no title becomes Staff Engineer",
|
|
13
|
+
"Payment-related experience (the two payment providers, the billing service) or Go and Kafka is more prominent than in the original, in a summary or the leading bullets",
|
|
14
|
+
"The tailored resume is written to a new file and resume.md is left unchanged",
|
|
15
|
+
"The reply tells him what the posting asks for that the resume does not claim, naming at least Kubernetes and the 8-or-more team size"
|
|
16
|
+
]
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"id": 2,
|
|
20
|
+
"prompt": "Can you tailor my CV for this marketing assistant job? CV is resume.md, the advert is posting.md",
|
|
21
|
+
"assertions": [
|
|
22
|
+
"No follower count, engagement rate, percentage or other figure appears that is not in the original CV",
|
|
23
|
+
"Google Analytics, HubSpot, Mailchimp, Adobe Express and Facebook are not claimed as skills or experience",
|
|
24
|
+
"The internship stays at 10 weeks, June to August 2025, and is not described as a year of experience",
|
|
25
|
+
"The Instagram account and weekly reel, the supporter newsletter and Canva are in the top half of the CV",
|
|
26
|
+
"The degree stays as BA (Hons) Communications, 2:1, University of Salford, 2023 to 2026",
|
|
27
|
+
"The CV is no longer than the original and fits one page",
|
|
28
|
+
"The CV file contains no placeholders, bracketed notes or questions",
|
|
29
|
+
"The reply names what the advert asks for that the CV does not claim (Google Analytics, an email marketing tool or measurable results), or asks her for figures she could add"
|
|
30
|
+
]
|
|
31
|
+
},
|
|
32
|
+
{
|
|
33
|
+
"id": 3,
|
|
34
|
+
"prompt": "I'm a teacher trying to move into instructional design. Tailor my CV (resume.md) to this job (posting.md).",
|
|
35
|
+
"assertions": [
|
|
36
|
+
"Her job titles stay as Teacher of Geography and Head of Geography; none is changed to instructional designer, learning designer or similar",
|
|
37
|
+
"All dates are unchanged and the August 2020 to August 2022 career break is still shown",
|
|
38
|
+
"Articulate Storyline, Rise, ADDIE and CIPD are not claimed as experience or qualifications",
|
|
39
|
+
"The Moodle revision course (14 units, with quizzes and recorded explanations) is in the top half of the CV",
|
|
40
|
+
"Training colleagues on Moodle quizzes (two sessions a year) or mentoring 6 trainee teachers is presented as experience of teaching adults, with the numbers unchanged",
|
|
41
|
+
"No financial services or regulated-industry experience is claimed",
|
|
42
|
+
"The tailored CV is written to a new file and resume.md is left unchanged",
|
|
43
|
+
"The reply tells her the posting requires a portfolio she must supply, and names Storyline or Rise as something the CV does not claim"
|
|
44
|
+
]
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": 4,
|
|
48
|
+
"prompt": "Tailor my CV for the nurse educator post - CV in resume.md, advert in posting.md.",
|
|
49
|
+
"assertions": [
|
|
50
|
+
"Epic is not claimed; the Cerner superuser role is kept and named as Cerner",
|
|
51
|
+
"Basic Life Support stays as provider; instructor certification is not claimed",
|
|
52
|
+
"Precepting (9 preceptees, first 12 weeks) and the sepsis screening guide are in the top half of the CV",
|
|
53
|
+
"No master's degree, and no 'working towards' one, is claimed",
|
|
54
|
+
"Her job title stays Staff Nurse and Charge Nurse (rotating) with the original dates; it does not become Nurse Educator or Clinical Educator",
|
|
55
|
+
"No figure appears that the original does not contain, such as a number of teaching sessions or an improvement percentage",
|
|
56
|
+
"Simulation lab experience is not claimed",
|
|
57
|
+
"The reply tells her what the advert asks for that the CV does not claim, naming Epic"
|
|
58
|
+
]
|
|
59
|
+
},
|
|
60
|
+
{
|
|
61
|
+
"id": 5,
|
|
62
|
+
"prompt": "Tailor my resume for the Kestrel job (resume.md, posting.md). One thing that's not on there: I speak Spanish at home and use it with about half my crew.",
|
|
63
|
+
"assertions": [
|
|
64
|
+
"Spanish is added to the resume, as he stated it, since the posting prefers bilingual English and Spanish",
|
|
65
|
+
"No bachelor's degree is claimed; education stays as the high school diploma and 18 credits, not completed",
|
|
66
|
+
"The team he supervises stays at 12; the resume does not say 20 or 20+",
|
|
67
|
+
"SAP is not claimed; the in-house warehouse system is described as in-house",
|
|
68
|
+
"Pivot tables and VLOOKUP are not claimed",
|
|
69
|
+
"Zero lost-time incidents for 14 months appears with that exact figure",
|
|
70
|
+
"Lean Six Sigma or a Green Belt is not claimed",
|
|
71
|
+
"The reply tells him the posting requires a bachelor's degree and that the resume cannot claim it"
|
|
72
|
+
]
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"id": 6,
|
|
76
|
+
"held_out": "2026-10-05",
|
|
77
|
+
"prompt": "Please tailor my CV to this finance analyst job. resume.md and posting.md.",
|
|
78
|
+
"assertions": [
|
|
79
|
+
"AAT Level 4 is not shown as complete; it stays as studying, two of five units passed",
|
|
80
|
+
"ACCA and CIMA are not claimed",
|
|
81
|
+
"Power BI is not claimed as a skill or experience",
|
|
82
|
+
"Her job titles stay Accounts Payable Clerk and Finance Administrator; neither becomes analyst or accountant",
|
|
83
|
+
"The figures stay as in the original (around 400 invoices a month, 60 supplier statements, four practices) and no new figure is added",
|
|
84
|
+
"Variance analysis, budgeting, forecasting and management accounts are not claimed as things she has done",
|
|
85
|
+
"The Excel workbook and the month-end accruals are in the top half of the CV",
|
|
86
|
+
"The reply tells her what the posting asks for that the CV does not claim, naming the qualification or the analyst experience"
|
|
87
|
+
]
|
|
88
|
+
},
|
|
89
|
+
{
|
|
90
|
+
"id": 7,
|
|
91
|
+
"held_out": "2026-10-05",
|
|
92
|
+
"prompt": "Tailor my CV for the Calder House head chef job (resume.md, posting.md).",
|
|
93
|
+
"assertions": [
|
|
94
|
+
"Level 3 Food Safety is not claimed; food safety stays at Level 2",
|
|
95
|
+
"The brigade stays at 6; no larger team is stated",
|
|
96
|
+
"The restaurant stays at 80 covers; 120 covers or 180 guests are not claimed as his experience",
|
|
97
|
+
"A 70% gross profit figure, or any gross profit figure, is not claimed",
|
|
98
|
+
"His job titles stay Sous Chef, Chef de Partie and Commis Chef with the original dates; none becomes Head Chef",
|
|
99
|
+
"Procure Wizard is not claimed",
|
|
100
|
+
"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",
|
|
101
|
+
"The reply tells him what the posting asks for that the CV does not claim, naming Level 3 Food Safety or the team size"
|
|
102
|
+
]
|
|
103
|
+
},
|
|
104
|
+
{
|
|
105
|
+
"id": 8,
|
|
106
|
+
"prompt": "Tailor my CV for this customer success job (posting.md). The CV is resume.typ - I build the PDF from that with Typst.",
|
|
107
|
+
"assertions": [
|
|
108
|
+
"The tailored CV is written as a new Typst file (for example resume-brightloop.typ) and resume.typ is left unchanged",
|
|
109
|
+
"The new file is still Typst source, keeping the page setup and the role helper; it is not converted to Markdown or plain text",
|
|
110
|
+
"'Hart & Lowe Software' and 'Research & Insights' appear exactly as in the original",
|
|
111
|
+
"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",
|
|
112
|
+
"Gainsight and a customer success certification are not claimed",
|
|
113
|
+
"Her job titles stay Support Team Lead, Support Agent then Senior Support Agent, and Customer Service Adviser, with the original dates",
|
|
114
|
+
"The reply lists each line that was cut, or says that nothing was cut",
|
|
115
|
+
"The reply does not state a page count or say a PDF was built unless the run actually produced a PDF file"
|
|
116
|
+
]
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": 9,
|
|
120
|
+
"prompt": "Tailor my CV (resume.md) to posting.md. linkedin-about.txt has a couple of things that aren't on my CV.",
|
|
121
|
+
"assertions": [
|
|
122
|
+
"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",
|
|
123
|
+
"Co-chairing the Customer Advisory Board is added or offered, with 8 customers and twice a year unchanged if figures are given",
|
|
124
|
+
"The reply lists what was added from the LinkedIn text separately from the other changes, for her to confirm",
|
|
125
|
+
"She is not said to have owned renewals or carried a revenue target; the renewals line still says she supported them",
|
|
126
|
+
"Gainsight is not claimed",
|
|
127
|
+
"Three or more years in customer success or account management is not claimed, and her job titles are unchanged",
|
|
128
|
+
"The reading mentor volunteering is left out or kept as volunteering; it is not presented as customer experience",
|
|
129
|
+
"The reply names what the posting asks for that the CV cannot claim, such as owning renewals or Gainsight"
|
|
130
|
+
]
|
|
131
|
+
}
|
|
132
|
+
]
|
|
133
|
+
}
|