Name interview-prep in the skills README and refer to the owner without a gendered pronoun
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3767ad1ad7
commit
7149cfd902
7 files changed
+19
-18
No files matched your search
@@ -1,13 +1,14 @@
|
||||
# Skills for claude.ai chat
|
||||
|
||||
Two skills for writing job applications in a claude.ai chat. They hold every rule; the user's own documents hold facts only.
|
||||
Three skills for job applications in a claude.ai chat. They hold every rule; the user's own documents hold facts only.
|
||||
|
||||
| Skill | What it does |
|
||||
|---|---|
|
||||
| `application-drafter` | From one posting: finds the employer's own posting, runs a fit check (eligibility and language gates, skills, experience and career scores), builds a requirement coverage table, drafts the CV and cover letter, reviews them as a hiring manager with independent company research, applies the edits, audits, and outputs the drafts with coverage, keyword and audit tables. Also drafts application form fields. Markdown by default, .docx on request. |
|
||||
| `interview-prep` | For a scheduled interview on an application already sent: verified company and interviewer research, likely questions ranked by stage, STAR answers drawn only from the career master, honest bridges for gaps, a consistency brief against the submitted CV and letter, questions to ask, a mock interview with feedback, and thank-you and follow-up notes (drafts only, at most two follow-ups). Needs the posting and the submitted CV and letter besides the two documents. |
|
||||
| `application-auditor` | Audits any application text (CV, letter, form answer, LinkedIn post): runs `scripts/check_text.py` for dashes, ASCII date ranges, banned phrases, bullets per role, bullet length and character counts, then checks every claim against the career master, every pitfalls entry, the interview backtrack test and confidentiality. Returns a findings table and never fixes silently. |
|
||||
|
||||
Both end with a "Pitfalls to add" block in the wrong / right / why format, for the user to paste into the pitfalls document. The drafter also lists "Facts to add" for facts confirmed in the chat that the career master lacks.
|
||||
All three end with a "Pitfalls to add" block in the wrong / right / why format, for the user to paste into the pitfalls document. The drafter and interview-prep also list "Facts to add" for facts confirmed in the chat that the career master lacks.
|
||||
|
||||
## The user's documents
|
||||
|
||||
@@ -22,7 +23,7 @@ Paste or attach both at the start of each chat; the skills ask for them when the
|
||||
./build.sh
|
||||
```
|
||||
|
||||
This writes `dist/application-drafter.zip` and `dist/application-auditor.zip` (`dist/` is gitignored). Each zip holds the skill folder with `SKILL.md` at the folder root; tests are left out. Upload each zip in claude.ai under Settings > Capabilities > Skills. Code execution must be on: the auditor runs its script in the sandbox and both skills count words and characters with code.
|
||||
This writes `dist/application-drafter.zip`, `dist/application-auditor.zip` and `dist/interview-prep.zip` (`dist/` is gitignored). Each zip holds the skill folder with `SKILL.md` at the folder root; tests are left out. Upload each zip in claude.ai under Settings > Capabilities > Skills. Code execution must be on: the auditor runs its script in the sandbox and both skills count words and characters with code.
|
||||
|
||||
Run the checker's tests with `python3 application-auditor/scripts/test_check_text.py`.
|
||||
|
||||
@@ -32,4 +33,4 @@ The rules are adapted from [ai-job-search](https://github.com/MadsLorentzen/ai-j
|
||||
|
||||
## Planned
|
||||
|
||||
Interview preparation and an upskilling skill follow later.
|
||||
An upskilling skill (a gap analysis and study plan for one posting) may follow.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: interview-prep
|
||||
description: Prepare for a scheduled job interview on an application already sent, from the owner's career master, pitfalls document, the posting and the CV and cover letter he submitted. Builds a stage-specific prep pack (verified company and interviewer research, likely questions, STAR answers from real facts, honest gap bridges, consistency brief, questions to ask), runs a mock interview, and drafts thank-you and follow-up notes. Use when the owner mentions an upcoming interview, screen or round, asks for interview practice, or wants a thank-you or follow-up note for an application.
|
||||
description: Prepare for a scheduled job interview on an application already sent, from the owner's career master, pitfalls document, the posting and the CV and cover letter they submitted. Builds a stage-specific prep pack (verified company and interviewer research, likely questions, STAR answers from real facts, honest gap bridges, consistency brief, questions to ask), runs a mock interview, and drafts thank-you and follow-up notes. Use when the owner mentions an upcoming interview, screen or round, asks for interview practice, or wants a thank-you or follow-up note for an application.
|
||||
---
|
||||
|
||||
# Interview prep
|
||||
@@ -41,7 +41,7 @@ Then ask, in one message, for whatever the inputs do not already state: stage (s
|
||||
|
||||
## Output
|
||||
|
||||
The pack is Markdown in the chat, in the language of the application unless the owner asks otherwise. When he asks for a file, write a .docx (or .md) with the Python sandbox and offer it for download; same content, headings as in `references/prep-pack.md`.
|
||||
The pack is Markdown in the chat, in the language of the application unless the owner asks otherwise. When they ask for a file, write a .docx (or .md) with the Python sandbox and offer it for download; same content, headings as in `references/prep-pack.md`.
|
||||
|
||||
Close every pack, mock round or note with these blocks when they have content, and omit them when empty:
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ Per named interviewer, note title, tenure, background and the likely angle of th
|
||||
| Interviewer | Probes |
|
||||
|---|---|
|
||||
| Recruiter or HR | CV timeline, motivation, notice period, salary range, logistics |
|
||||
| Hiring manager | Team fit, motivation, how the owner works, scope he has carried |
|
||||
| Hiring manager | Team fit, motivation, how the owner works, scope they have carried |
|
||||
| Senior engineer or specialist | Technical depth on the stack and on every tool the CV names |
|
||||
| Executive or founder | Judgement, values, why this company, long-term fit |
|
||||
|
||||
@@ -52,4 +52,4 @@ Pick 2-3 recent, verified specifics (a product launch, a stated priority, a talk
|
||||
|
||||
## Call before applying
|
||||
|
||||
If the posting names a contact person who invites questions and the requirements were vague, the owner may have called before applying. If he did, use what he learned in the pack and in the questions to ask. The call's purpose was gathering information, not pitching; do not suggest calls just to be remembered.
|
||||
If the posting names a contact person who invites questions and the requirements were vague, the owner may have called before applying. If they did, use what they learned in the pack and in the questions to ask. The call's purpose was gathering information, not pitching; do not suggest calls just to be remembered.
|
||||
@@ -1,6 +1,6 @@
|
||||
# Thank-you and follow-up notes
|
||||
|
||||
Drafts only. The owner sends them himself. Nothing is emailed, messaged or submitted from the chat.
|
||||
Drafts only. The owner sends them. Nothing is emailed, messaged or submitted from the chat.
|
||||
|
||||
## Shared rules
|
||||
|
||||
@@ -9,7 +9,7 @@ Drafts only. The owner sends them himself. Nothing is emailed, messaged or submi
|
||||
- Match the application's language and the register of the submitted cover letter.
|
||||
- Style: warm but direct, no em-dashes, no clichés, no pressure, no "just checking in", no apology for writing.
|
||||
- Address the named contact person if known; otherwise the team, in the application's language.
|
||||
- Iterate until the owner is happy. Then remind him of the date sent, since the chat keeps no record.
|
||||
- Iterate until the owner is happy. Then remind them of the date sent, since the chat keeps no record.
|
||||
|
||||
## Channel shape
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ After each answer, short and in this shape:
|
||||
- **Better story**: which STAR example from the pack would have served better, if any.
|
||||
- **Accuracy**: any statement that contradicts the career master, the submitted CV or letter, or a pitfall entry, with the right version. This takes priority over style.
|
||||
|
||||
Calibrate to the owner's own register: tighten his voice, do not replace it with a generic one. Do not praise by default; say when an answer is ready.
|
||||
Calibrate to the owner's own register: tighten their voice, do not replace it with a generic one. Do not praise by default; say when an answer is ready.
|
||||
|
||||
## Close
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ Derive from four sources, in this priority order, and label each question with i
|
||||
| Stage | Typical questions |
|
||||
|---|---|
|
||||
| Screen | Motivation, why this company, CV walk-through, notice period, salary expectation, location or remote |
|
||||
| Hiring manager | Scope carried, how he works with others, a conflict, a failure, priorities in the first months |
|
||||
| Hiring manager | Scope carried, how they work with others, a conflict, a failure, priorities in the first months |
|
||||
| Technical | The posting's stack, every tool the CV names, design trade-offs, debugging a past incident, live exercise |
|
||||
| Case | Structure a problem out loud, estimates, trade-offs, a recommendation and its risks |
|
||||
| Panel | Mixed; one question per panel member's angle, consistency across them |
|
||||
@@ -62,7 +62,7 @@ Prepared answers grounded in the career master, in the owner's register, each 30
|
||||
- **Where do you see yourself in five years?** Ambition that fits the role's growth path as the posting and research describe it.
|
||||
- **Biggest weakness?** A real one with the concrete mitigation the owner actually uses. Not a disguised strength.
|
||||
- **Why this company?** Uses the verified hooks. Never a generic line.
|
||||
- **Salary expectation**, when the stage calls for it: ask the owner for his number and range; do not invent market data. If he wants a benchmark, research it and cite sources like any other claim.
|
||||
- **Salary expectation**, when the stage calls for it: ask the owner for their number and range; do not invent market data. If he wants a benchmark, research it and cite sources like any other claim.
|
||||
- Any hard question the earlier-round feedback implies.
|
||||
|
||||
## 6. Questions to ask
|
||||
@@ -77,7 +77,7 @@ Cut every question the public material or the posting already answers; asking it
|
||||
|
||||
## 7. Sources
|
||||
|
||||
The claim/source table from `company-research.md`, so the owner can defend any fact he uses.
|
||||
The claim/source table from `company-research.md`, so the owner can defend any fact they use.
|
||||
|
||||
## Closing blocks
|
||||
|
||||
|
||||
@@ -4,9 +4,9 @@
|
||||
|
||||
- **Situation**: the context and the problem, in two sentences.
|
||||
- **Task**: what the owner specifically was responsible for.
|
||||
- **Action**: what he did, with methods and tools. "I", not "we", unless the point is the team.
|
||||
- **Action**: what they did, with methods and tools. "I", not "we", unless the point is the team.
|
||||
- **Result**: the outcome, measured where the career master has the number; adoption or impact otherwise.
|
||||
- **Learned**: one sentence on what he learned or would do differently.
|
||||
- **Learned**: one sentence on what they learned or would do differently.
|
||||
|
||||
Length: 1-2 minutes spoken, roughly 150-300 words written. Specific beats complete; cut setup the question does not need.
|
||||
|
||||
@@ -43,7 +43,7 @@ Example (generic):
|
||||
|
||||
> I haven't run Kubernetes in production. I have run containerised services on a managed platform for three years, including the scaling and incident work that goes with it, so the concepts are familiar. I've been working through the CKA material and set up a test cluster for a side project; in the first months I'd expect to pair with whoever owns the platform.
|
||||
|
||||
Then offer a **STAR stub** for the owner to fill, in case he has a story the career master does not record:
|
||||
Then offer a **STAR stub** for the owner to fill, in case they have a story the career master does not record:
|
||||
|
||||
```
|
||||
### [Working title] (competency: ...)
|
||||
@@ -58,4 +58,4 @@ A filled stub is a new fact: it goes into "Facts to add to the career master" be
|
||||
|
||||
## Calibration to the owner
|
||||
|
||||
Write in the owner's register as it shows in his cover letter and the answers he gives in the session: sentence length, formality, how much he hedges or quantifies. Coach toward his best version of his own voice, not a generic ideal.
|
||||
Write in the owner's register as it shows in their cover letter and the answers they give in the session: sentence length, formality, how much he hedges or quantifies. Coach toward his best version of his own voice, not a generic ideal.
|
||||
Reference in new issue
Block a user