Changes

diff --git a/skills/job-cover-letter/SKILL.md b/skills/job-cover-letter/SKILL.md
new file mode 100755
index 0000000..5cf804e
--- /dev/null
+++ b/skills/job-cover-letter/SKILL.md
@@ -0,0 +1,142 @@
+---
+name: job-cover-letter
+description: Draft a tailored, job-specific cover letter from a resume, a job posting, and research about the target company. Use when the user wants to write, draft, generate, or improve a cover letter for a specific job.
+---
+
+# Cover Letter
+
+Draft a one-page, tailored cover letter for a specific job. Strong
+cover letters are built from three inputs — the candidate's resume,
+the job posting, and concrete details about the company — and follow a
+small set of writing principles. Skip any of those inputs and the
+letter will read generic.
+
+## Workflow
+
+Follow these steps in order. Do not skip ahead — drafting without
+inputs or research is the single most common failure mode.
+
+### Step 1: Gather inputs
+
+Before drafting anything, you need both of these. If either is
+missing, ask the user for it.
+
+1. **Resume** — file path, pasted text, or a link. Read it fully
+   before writing.
+2. **Job posting** — file path, pasted text, or URL. If it's a URL,
+   fetch it with WebFetch. Read the full posting; do not skim.
+
+Also helpful, ask if not provided:
+- **Hiring manager's name** (if known) — beats "Dear Hiring Manager"
+- **Tone preference** — formal, conversational, or match-the-company
+  (default)
+- **Anything to emphasize or avoid** — e.g., explaining a career
+  change, downplaying a gap
+
+Do not proceed to Step 2 until you have at least the resume and job
+posting.
+
+### Step 2: Research the company
+
+Use WebSearch and WebFetch to find:
+
+1. **What the company does** — read their About page, recent product
+   launches, and mission statement.
+2. **One or two specific, recent things** — a product launch, news
+   item, public initiative, or value statement that the candidate can
+   plausibly connect to. Generic admiration ("I admire your work") is
+   worthless; one specific reference beats three vague compliments.
+3. **Tone and voice** — skim their website copy and any public-facing
+   communications. A fintech firm wants polished; a startup wants
+   energy. The letter's voice should mirror this.
+
+Search queries that work well:
+- `<company name> about` / `<company name> mission`
+- `<company name> news <current year>`
+- `<company name> blog`
+- `<company name> <relevant product or team>`
+
+If the company is obscure and search turns up little, tell the user
+and ask if they have any inside knowledge to share.
+
+### Step 3: Plan before drafting
+
+Do not start writing prose yet. First, do this analysis (briefly, in
+your head or as notes):
+
+1. **Extract the job's must-haves.** Pull 4-6 specific
+   skills/responsibilities from the posting. Mirror their exact
+   phrasing later — if they say "distributed systems," don't write
+   "large-scale infrastructure."
+2. **Find the overlap.** For each must-have, identify one specific
+   item from the resume that demonstrates it. Prefer items with
+   metrics (% improvement, $ saved, users affected, time reduced).
+3. **Pick the company hook.** Choose ONE specific thing from your
+   research that ties to the candidate's experience or motivations.
+   This goes in the opener.
+4. **Pick 2-3 stories.** Each story = situation + action +
+   result-with-a-number. These fill the body.
+
+If you can't find at least one quantified achievement in the resume
+that maps to the job's requirements, surface this to the user before
+drafting — the letter will be weak without concrete results.
+
+### Step 4: Draft
+
+Write 4-5 short paragraphs, one page total. Structure:
+
+| Section | Contents | Length |
+|---|---|---|
+| Header | Candidate name, contact info, date, addressee | 4-6 lines |
+| Intro | Who they are, what role, ONE specific company hook | 2-4 sentences |
+| Body (1-2 paragraphs) | 2-3 stories with metrics, mirroring the job's language | ~60% of the letter |
+| Conclusion | Polite, open call-to-action — never "I'll call you" | 2-3 sentences |
+| Signature | "Sincerely," + name | 2 lines |
+
+Detailed structural guidance, story formula, tone matching, banned
+phrases, and worked example comparisons are in
+[references/best-practices.md](references/best-practices.md). **Read
+it before drafting the first time** — it contains the rules that make
+the difference between a forgettable letter and a strong one.
+
+### Step 5: Self-review against the checklist
+
+Before showing the letter to the user, run through the checklist at
+the end of
+[references/best-practices.md](references/best-practices.md). Common
+things to catch:
+
+- Generic adjectives instead of evidence ("detail-oriented,"
+  "self-starter")
+- Opening with "I am writing to apply for…"
+- Body claims without numbers
+- Banned phrases ("To Whom It May Concern," "think outside the box,"
+  "game-changer")
+- A closing that oversteps ("I will call you next week")
+- Restating the resume instead of expanding on it
+
+Fix anything that fails the check, then present the draft.
+
+### Step 6: Offer to iterate
+
+After presenting the draft, briefly ask whether the user wants to:
+- Adjust the tone (more formal / more casual)
+- Swap in different stories or emphasize different skills
+- Shorten / lengthen specific paragraphs
+- Try a different opening
+
+Keep iterations focused — change one dimension at a time.
+
+## Important rules
+
+- **One page.** If the draft is running long, cut — don't shrink the
+  font.
+- **Never invent achievements, metrics, employers, or skills.** If the
+  resume doesn't support a claim, do not write it. Ask the user
+  instead.
+- **Mirror the posting's language.** This helps with both human
+  readers and ATS keyword scans.
+- **Specific > generic, every time.** A named product, a number, a
+  real story always beats an adjective.
+- **No templates, no boilerplate.** Each cover letter is written for
+  one specific job.
diff --git a/skills/job-cover-letter/references/best-practices.md b/skills/job-cover-letter/references/best-practices.md
new file mode 100755
index 0000000..1f8f2de
--- /dev/null
+++ b/skills/job-cover-letter/references/best-practices.md
@@ -0,0 +1,255 @@
+# Cover Letter Best Practices
+
+Detailed guidance for drafting. Read this when SKILL.md says to.
+
+## Table of contents
+
+1. Structure and section purpose
+2. The opening paragraph
+3. Body paragraphs: the story formula
+4. Soft skills (how to use them without sounding generic)
+5. Tone matching
+6. Honesty
+7. The closing
+8. Phrases to avoid
+9. Worked comparison: weak vs strong
+10. Final checklist
+
+---
+
+## 1. Structure and section purpose
+
+A cover letter is one page, 4-5 short paragraphs. Each section has a
+job.
+
+**Header** — candidate's name, city/state, phone, email; then date;
+then the addressee (hiring manager's name + company + address if
+known). If the hiring manager's name cannot be found, "Dear [Team]
+Hiring Team" beats "To Whom It May Concern."
+
+**Intro** — Answers two questions in 2-4 sentences:
+1. Why this role? (state the role explicitly)
+2. Why this company specifically? (this is where the company-research
+   hook goes)
+
+**Body (1-2 paragraphs)** — The bulk of the letter. This is where
+stories with metrics live. Do not restate the resume; expand on it.
+
+**Conclusion** — Restate fit in one line, offer a polite open
+invitation to continue the conversation, thank them. 2-3 sentences
+max.
+
+**Signature** — `Sincerely,` then the candidate's name.
+
+## 2. The opening paragraph
+
+**Weak:** "I am writing to apply for the X position at Y." Technically
+fine; deeply forgettable.
+
+**Strong:** Lead with one specific thing about the company tied to the
+candidate's experience or motivation. Examples of patterns that work:
+
+- "Tesla's commitment to accelerating the world's transition to
+  sustainable energy aligns with my work on …"
+- "I've been especially impressed with the app redesign XYZ recently
+  launched, and I'm interested in joining the team behind it."
+- "I've followed Animax's animal-adoption work since high school, when
+  I started volunteering at shelters."
+
+Three things the opener must do:
+1. State the role being applied for.
+2. Drop one specific, accurate detail about the company.
+3. Signal genuine interest without flattery.
+
+## 3. Body paragraphs: the story formula
+
+Every body claim should follow the **Situation → Action → Result**
+pattern, with the Result quantified whenever possible.
+
+Bad: > "My excellent attention to detail and quest for perfection
+allow me to produce quality code that requires less debugging."
+
+Unverifiable, unmeasurable, generic.
+
+Good: > "At CloudScale Systems, I led a team architecting a
+distributed microservices platform in Java and Go, which improved
+system uptime by 25% and cut latency by 30%. I also drove the adoption
+of CI/CD pipelines, decreasing deployment time by 40%."
+
+Every claim has: a context, a specific action verb, a named
+technology, and a number.
+
+**Action verbs that read strongly:** led, architected, spearheaded,
+designed, shipped, implemented, scaled, automated, reduced, increased,
+owned, migrated, mentored.
+
+**Avoid:** helped with, was involved in, participated in, contributed
+to (unless followed by a specific contribution).
+
+### Mirror the posting's language
+
+If the posting uses a specific phrase, reuse it verbatim in the body.
+This signals fit to human readers and improves ATS keyword matching.
+Don't translate "distributed systems" into "large-scale
+infrastructure" — use their words.
+
+### Don't restate the resume
+
+The reader has the resume. The cover letter expands on a few selected
+items with the context and outcome that a resume bullet can't fit.
+Pick 2-3 items max.
+
+## 4. Soft skills
+
+Soft skills matter even in technical roles, but listing them ("strong
+communicator, team player, detail-oriented") is worthless. Demonstrate
+them inside a story:
+
+Weak: "I have strong communication and leadership skills."
+
+Strong: "Onboarded 3 new hires, all of whom completed onboarding 17%
+faster than expected — feedback from my manager credited the
+structured walkthroughs I built."
+
+Soft skills worth showing when relevant: communication, mentorship,
+cross-functional collaboration, conflict resolution, fast learning,
+written communication.
+
+## 5. Tone matching
+
+Skim the company's website, blog, and recent comms before choosing a
+voice.
+
+- **Established / regulated** (banks, law firms, healthcare, defense):
+  formal, measured, polished. Full sentences. No exclamation points.
+- **Mainstream tech** (large product companies): confident and direct,
+  professional but not stiff. Some personality is fine.
+- **Startup / consumer tech / creative agency**: more energy, more
+  personality, shorter sentences. Stiff formality reads as
+  out-of-touch.
+
+When in doubt, lean slightly more formal than the company's marketing
+copy — marketing is louder than internal communication.
+
+## 6. Honesty
+
+Never claim a skill the candidate cannot demonstrate. It will surface
+in the interview or on the job and end the process. If asked to write
+something the resume doesn't support, push back and ask the user for
+the real backing experience instead.
+
+## 7. The closing
+
+Two or three sentences. Restate fit briefly, signal openness to a
+conversation, thank them.
+
+**Good:** > "I'd welcome the opportunity to discuss how my background
+fits the team's goals. Thank you for your consideration."
+
+**Bad — oversteps:** > "I'll call your office next week to schedule an
+interview."
+
+**Bad — clichéd:** > "Thank you for taking the time to review my
+resume. I believe my skill set makes me a great fit."
+
+## 8. Phrases to avoid
+
+Hiring managers see these constantly. Cut them.
+
+**Openers / closers:**
+- "To Whom It May Concern"
+- "I am writing to apply for…"
+- "Thank you for taking the time to look at my resume"
+- "I believe my skill set makes me a great fit"
+- "Please feel free to contact me"
+- "I'll call to schedule an interview"
+
+**Adjectives that say nothing:**
+- Detail-oriented
+- Self-starter
+- Forward-thinker
+- Dynamic
+- Results-driven
+- Hard-working
+- Team player
+
+**Tired metaphors:**
+- Think outside the box
+- Game-changer
+- Heavy lifting
+- Move the needle
+- Bring my A-game
+- Wear many hats
+
+**Filler:**
+- "I'm not sure if you know…"
+- "Really, truly, deeply"
+- "Significant" (as standalone — quantify instead)
+
+Also avoid generic buzzwords. Avoid using em-dashes unless absolutely
+necessary.
+
+If a phrase shows up in 80% of cover letters, it's invisible. Replace
+it with something specific.
+
+## 9. Worked comparison: weak vs strong
+
+Two openings for the same hypothetical role.
+
+**Weak:** > "I am writing to apply for the Associate Software Engineer
+position with Up and Yonder Technologies. As an engineer with more
+than 10 years of experience with coding and project development, I
+believe I can add value to your team and help your organization
+accomplish its goals."
+
+Problems: dry "I am writing to apply" opener, generic "add value to
+your team," no specific reason for *this* company, vague experience
+claim.
+
+**Strong:** > "I am applying for the Senior Software Engineer position
+at Tesla. With 8 years building distributed systems and cloud
+infrastructure, I'm eager to bring that experience to your team —
+Tesla's mission to accelerate sustainable energy is exactly the kind
+of impact-oriented work I want my next role to support."
+
+Why it works: states the role, names specific skills aligned to the
+posting, ties motivation to a specific company mission. Three
+sentences, no filler.
+
+Same logic applies to body paragraphs: a list of adjectives loses to
+one quantified story every time.
+
+## 10. Final checklist
+
+Run through this before presenting the draft.
+
+**Structure**
+- [ ] One page, 4-5 paragraphs
+- [ ] Header with contact info, date, addressee
+- [ ] Signed with `Sincerely,` + name
+
+**Targeting**
+- [ ] Addressed to a specific person (if findable)
+- [ ] Opening references something specific about *this* company
+- [ ] Job posting's key phrases appear in the letter
+- [ ] Tone matches the company's voice
+
+**Content**
+- [ ] Every body paragraph contains at least one concrete number,
+      named project, or named technology
+- [ ] No restating of the resume — each story adds context or outcome
+      the resume can't
+- [ ] Soft skills appear inside stories, not as adjective lists
+- [ ] No banned phrases or clichés, no buzzwords, no unnecessary
+      em-dashes
+- [ ] No claims unsupported by the resume
+
+**Closing**
+- [ ] Polite, open call-to-action (no "I'll call you")
+- [ ] No "thank you for taking the time to review my resume"
+
+**Polish**
+- [ ] No typos, no grammar errors
+- [ ] Reads well aloud — no tangled sentences
+
+If anything fails, fix before showing the user.