cue-ai 0.9.2 → 0.9.3

package/resources/skills/skills/career/job-hunter/agents/offer-compare.md

@@ -0,0 +1,117 @@
+# Offer Comparison Tool
+
+## What This Does
+
+Compares two or more job offers side by side — beyond just the numbers.
+Total compensation, growth trajectory, risk profile, culture signals, and
+a recommended decision with honest reasoning.
+
+Most people compare offers on base salary alone and miss the full picture.
+
+## Instructions for Claude Code
+
+### Step 1 — Gather offer details
+
+Ask the user to provide details for each offer. Collect all at once:
+
+> For each offer provide:
+> - Company name and role title
+> - Base salary
+> - Bonus structure (target % or fixed amount)
+> - OTE if sales role
+> - Equity (options or RSUs — amount and vesting schedule if known)
+> - Signing bonus (if any)
+> - Benefits (health, 401k match, PTO)
+> - Location / remote policy
+> - Start date flexibility
+> - Stage of company (startup / growth / public / enterprise)
+> - Why you're excited about it
+> - What concerns you about it
+
+### Step 2 — Calculate total compensation
+
+For each offer calculate:
+- Year 1 total cash (base + signing bonus prorated + target bonus)
+- Year 1 total comp (cash + equity year 1 value if determinable)
+- Year 3 total cash (base assuming 5% annual raise + bonus)
+- Year 3 total comp (cash + remaining equity)
+
+Note assumptions made where data is missing.
+
+### Step 3 — Score each offer across dimensions
+
+Score each offer 1-10 on:
+
+**Compensation** — total comp vs market rate for this role/location
+**Growth trajectory** — where does this role lead in 2-3 years?
+**Stability** — how likely is this company/role to exist in 2 years?
+**Culture fit** — based on what the user shared about each company
+**Learning** — will this role build skills that compound?
+**Flexibility** — remote, hours, autonomy
+**Upside** — equity, commission, promotion velocity
+
+### Step 4 — The comparison
+
+```
+─────────────────────────────────────────────────────
+OFFER COMPARISON
+─────────────────────────────────────────────────────
+
+                        [OFFER A]       [OFFER B]
+Base                    $X              $X
+Target bonus            $X              $X
+OTE / total cash Y1     $X              $X
+Equity Y1 value         $X              $X
+Signing (prorated Y1)   $X              $X
+TOTAL COMP YEAR 1       $X              $X
+TOTAL COMP YEAR 3 est.  $X              $X
+
+Compensation score:     X/10            X/10
+Growth trajectory:      X/10            X/10
+Stability:              X/10            X/10
+Learning:               X/10            X/10
+Upside:                 X/10            X/10
+
+OVERALL SCORE:          X/10            X/10
+
+─────────────────────────────────────────────────────
+```
+
+### Step 5 — The honest recommendation
+
+Give a direct recommendation — not "it depends on your priorities."
+
+State which offer to take and why. Then explain:
+- The one thing that makes Offer A better than Offer B
+- The one thing that makes Offer B better than Offer A
+- The scenario in which the other choice would be right
+- What to negotiate on the recommended offer before accepting
+
+### Step 6 — What to negotiate before deciding
+
+For the recommended offer, identify 2-3 things worth asking for before signing:
+- What is likely moveable?
+- What is the ask and how to make it?
+
+### Step 7 — The question to sleep on
+
+End with one honest question the user should sit with before deciding:
+Something they may be glossing over or rationalizing — a real concern worth
+examining before committing.
+
+### Step 8 — Save output
+
+Write to `outputs/offer-comparison.md`.
+
+## Tone
+
+Direct. Give a recommendation. "It depends" is not useful when someone is
+deciding between two offers with a deadline. Make the call with the information
+available and explain the reasoning clearly.
+
+---
+
+## ✅ What to do next
+
+Sit with the recommendation overnight before deciding.
+The question at the end is the one worth answering honestly.

package/resources/skills/skills/career/job-hunter/agents/offer-counteroffer.md

@@ -0,0 +1,144 @@
+# Counter-Offer Builder
+
+## What This Does
+
+Builds a written counter-proposal — the actual document or email you send
+back when you want to negotiate an offer.
+
+The negotiation sim (`npm run negotiate`) is the practice conversation.
+This is the artifact. A written counter changes the dynamic — it forces
+clarity on both sides, reduces the chance of miscommunication, and signals
+you're serious and organized.
+
+Most candidates negotiate verbally and leave things vague. A written counter
+with rationale for each ask is both more professional and more effective.
+
+## Instructions for Claude Code
+
+### Step 1 — Load inputs
+
+Read `inputs/my-resume.md`.
+Read `outputs/salary-research.md` if it exists — use the comp data.
+Read `rules/writing-rules.md`.
+
+Ask the user:
+
+```
+Tell me about the offer you received:
+
+1. Base salary offered
+2. Bonus / OTE (if applicable)
+3. Equity (options, RSUs — amount and vesting schedule if known)
+4. Signing bonus
+5. PTO and remote/hybrid policy
+6. Start date
+7. Any other notable terms
+
+Then tell me:
+8. What's your target base?
+9. Is there anything non-salary that matters as much or more?
+   (start date, remote flexibility, title, equity, signing bonus)
+10. Do you have a competing offer or a current compensation anchor?
+    (having a number to reference makes every ask stronger)
+```
+
+Wait for their answers.
+
+### Step 2 — Build the counter strategy
+
+Before writing anything, assess:
+
+**LEVERAGE CHECK**
+- Do they have a competing offer? (strong leverage)
+- Are they a rare skill set for this role? (strong leverage)
+- Is the company in growth mode or tightening mode? (from company research if available)
+- How long has the role been open? (longer = more flexible)
+- Is this a replacement hire or new headcount? (new headcount = harder to flex)
+
+**WHAT TO ASK FOR vs. WHAT TO LET GO**
+Rank each potential ask:
+- Base salary (always ask — the primary number)
+- Signing bonus (easier to grant than base — companies love one-time costs)
+- Equity (depends heavily on company stage)
+- Remote flexibility (often non-negotiable but worth asking)
+- Title (sometimes easy, often meaningful for future comp)
+- Start date (usually flexible)
+- PTO (harder to flex at most companies)
+
+Recommend: ask for 2-3 things, not everything. Prioritize the ones most
+likely to be granted AND most valuable to this person.
+
+### Step 3 — Write the counter
+
+Format as a professional email:
+
+---
+
+**SUBJECT:** Re: [Role Title] Offer — [First Name]
+
+[2-sentence opener — acknowledge the offer genuinely without being effusive.
+Something specific about the opportunity. Not "I'm so excited."]
+
+I'd like to explore whether there's room to adjust a few terms before I sign.
+
+**Base Salary**
+The offer is $[X]. Based on [comp research / market data / current comp],
+I'm targeting $[Y]. I believe this reflects [1 specific reason — your
+experience level, the market for this skill set, or the scope of the role].
+
+**[Second ask if applicable]**
+[Same format — specific ask, specific rationale. One sentence.]
+
+**[Third ask if applicable — only if high confidence it's grantable]**
+[Same format.]
+
+These are my priorities. I'm not looking to nickel-and-dime — I want
+to get to yes. If the base is genuinely fixed, I'd like to discuss
+[signing bonus / additional equity / start date flexibility] as an
+alternative.
+
+[1-sentence close — reaffirm interest, give a reasonable timeline.]
+
+[Name]
+
+---
+
+### Step 4 — Write the backup
+
+Write a second version for if they come back with a partial yes:
+
+**IF THEY MEET YOU HALFWAY:**
+[Exact language for accepting a partial counter gracefully]
+
+**IF THEY SAY THE NUMBER IS FIXED:**
+[Language for pivoting to signing bonus or equity]
+
+**IF THEY RESCIND THE OFFER:**
+[This is extremely rare but worth noting — when to hold firm anyway]
+
+### Step 5 — Anchoring language
+
+Provide 3 specific phrases for the verbal conversation that follows
+the written counter:
+- One to open the negotiation call
+- One to hold firm without creating friction
+- One to close once you've reached agreement
+
+### Step 6 — Save output
+
+Write to `outputs/counteroffer.md`.
+
+Tell the user:
+> Counter-offer ready. outputs/counteroffer.md
+>
+> Send the email. Then be quiet. The next person to speak loses.
+
+## ✅ What to do next
+
+```
+npm run negotiate      ← practice the conversation before the call
+npm run compare        ← if you have multiple offers
+npm run salary         ← if you need more comp data before sending
+```
+
+Apply all rules from `rules/writing-rules.md`.

package/resources/skills/skills/career/job-hunter/agents/offer-deadline-manager.md

@@ -0,0 +1,148 @@
+# Offer Deadline Manager
+
+## What This Does
+
+Builds a playbook for the specific situation where you have an offer
+expiring and you're waiting on another company.
+
+This is one of the highest-stakes moments in a job search and most people
+handle it badly — they either accept the first offer out of fear or blow
+up the second opportunity by being too aggressive. This agent tells you
+exactly what to say, when to say it, and what each company is actually
+thinking.
+
+## Instructions for Claude Code
+
+### Step 1 — Load inputs
+
+Read `inputs/my-resume.md`.
+Read `outputs/salary-research.md` if it exists.
+Read `rules/writing-rules.md`.
+
+Ask the user:
+
+```
+Tell me your situation:
+
+1. What is Offer A? (company, role, comp, deadline)
+2. What is Company B? (company, role, stage you're at — final round, offer pending, etc.)
+3. How long until Offer A expires?
+4. How far along is Company B? (days until decision, or unknown)
+5. Which do you actually prefer? (be honest — it changes the strategy)
+6. Have you told either company about the other?
+```
+
+Wait for their full answer.
+
+### Step 2 — Assess the situation honestly
+
+Before any recommendations, state clearly:
+
+**THE REALITY**
+- How much time pressure actually exists
+- What each company is likely thinking right now
+- What the realistic outcome is in each scenario
+- Whether this is a real competition or perceived pressure
+
+**YOUR LEVERAGE**
+Rate it: Strong / Moderate / Weak — and explain why.
+- Strong: Company B is actively interested, offer expected soon
+- Moderate: Company B is moving but timeline uncertain
+- Weak: Company B is early stage or you haven't heard back recently
+
+### Step 3 — Build the playbook
+
+**MOVE 1 — Ask Company A for an extension**
+
+When: Immediately, within 24 hours of knowing you need it.
+How much to ask for: 5-7 business days is reasonable. 2 weeks is a stretch.
+The framing: You are not stalling. You are being responsible.
+
+Write the exact email:
+
+---
+Subject: Re: [Role] Offer — Extension Request
+
+[Opener that acknowledges the offer warmly without being over the top]
+
+I'm genuinely excited about this opportunity and want to make a thoughtful
+decision. I have a few final items I'm working through — [optional: briefly
+name one legitimate item, e.g. outstanding questions from legal review,
+relocation logistics] — and I'd appreciate [X] additional business days to
+confirm.
+
+I want to start this relationship on solid footing. Would that be possible?
+
+[Name]
+---
+
+**MOVE 2 — Accelerate Company B**
+
+When: Same day you request the extension from A.
+What to say: Be honest that you have an offer and a decision date.
+What NOT to say: Don't name Company A. Don't exaggerate the timeline.
+
+Write the exact message:
+
+---
+[To: Company B recruiter or hiring manager]
+
+I wanted to be transparent with you: I've received an offer from another
+company with a decision deadline of [date]. [Role] at [Company B] is my
+first choice, and I'd rather make this decision with full information
+than under artificial time pressure.
+
+Is there any way to expedite the timeline on your end, or can you give
+me a sense of where things stand?
+
+[Name]
+---
+
+**MOVE 3 — If Company B can't move fast enough**
+
+Decision framework:
+- If Offer A is strong and Company B is uncertain: take A
+- If Company B is your clear preference and timeline is close: ask A for one more extension
+- If you're genuinely torn: use the compare tool
+
+Write the decline email for whichever offer you don't take — keep the
+door open.
+
+**MOVE 4 — If Company A won't extend**
+
+You have a hard choice. Map it:
+- What happens if you accept A and Company B comes through later? (you'd have to renege — assess that risk)
+- What happens if you decline A and Company B falls through? (you're back to searching)
+- Is there a third path? (ask A if you can start earlier to demonstrate commitment)
+
+### Step 4 — Timeline map
+
+Draw the exact timeline:
+
+```
+TODAY          OFFER A DEADLINE    TARGET DECISION
+  |__________________|___________________|
+  ↑                  ↑                   ↑
+  Request extension  If no extension:    Full information
+  Accelerate B       decide here         decision
+```
+
+### Step 5 — Save output
+
+Write to `outputs/deadline-manager.md`.
+
+Tell the user:
+> Playbook ready. outputs/deadline-manager.md
+>
+> Move 1 first — ask for the extension today.
+> Move 2 the same day — don't wait to see if A grants it.
+
+## ✅ What to do next
+
+```
+npm run counter        ← if you're negotiating the offer terms too
+npm run compare        ← full side-by-side comparison of both offers
+npm run negotiate      ← practice the offer conversation
+```
+
+Apply all rules from `rules/writing-rules.md`.

package/resources/skills/skills/career/job-hunter/agents/offer-negotiate.md

@@ -0,0 +1,126 @@
+# Salary Negotiation Simulator
+
+## What This Does
+
+Simulates a real offer negotiation conversation. Claude plays the hiring manager
+or recruiter. You practice countering. It grades your moves and tells you where
+you left money on the table.
+
+Most people have never practiced this conversation before the real one. This fixes that.
+
+## Instructions for Claude Code
+
+### Step 1 — Load inputs
+
+Read `inputs/job-description.md` for role and company context.
+Read `inputs/my-resume.md` for background and experience level.
+If `outputs/salary-research.md` exists, read it — use the ranges and anchor numbers from there.
+
+### Step 2 — Set the scene
+
+Ask the user:
+> What offer did you receive? Give me:
+> - Base salary
+> - OTE or bonus structure (if applicable)
+> - Equity (if applicable)
+> - Any other components (signing bonus, PTO, remote flexibility)
+> - What number you actually want
+
+Wait for their answer before proceeding.
+
+### Step 3 — Assess the offer
+
+Silently evaluate:
+- Is this offer at, above, or below market for this role?
+- What is realistic to negotiate given the role level and company size?
+- What is the most they would likely go to on base? On OTE? On signing bonus?
+- What non-salary levers are available if base is fixed?
+
+### Step 4 — Run the simulation
+
+Open with this exactly:
+
+```
+─────────────────────────────────────────────────────
+NEGOTIATION SIMULATION
+Role: [role] at [company]
+Your offer: [what they told you]
+Your target: [what they want]
+─────────────────────────────────────────────────────
+
+I'm playing the recruiter calling to give you the offer.
+Respond as you would in the real conversation.
+I'll play it straight — not a pushover, not a villain.
+
+Ready? Here's the call.
+─────────────────────────────────────────────────────
+
+"Hey [name], I'm excited to extend you an offer for the [role] position.
+We'd like to bring you on at [offer base] base with [OTE/bonus structure].
+[Equity/signing if applicable]. What do you think?"
+```
+
+### Step 5 — Run the negotiation in real time
+
+Play the recruiter authentically:
+- If they accept immediately: tell them they left money on the table and replay
+- If they counter reasonably: push back once the way a real recruiter would ("Let me see what I can do... the best I can get you is X")
+- If they counter too high: push back harder ("That's outside what we budgeted for this role")
+- If they ask for time: grant it ("Of course, when can I expect to hear back?")
+- If they negotiate non-salary items: be flexible on some, firm on others
+
+After each exchange, grade their move:
+
+```
+MOVE GRADE: A / B / C / D
+WHAT WORKED: [specific]
+WHAT MISSED: [specific]
+MONEY LEFT: [estimate of what they could still get]
+```
+
+Continue until the negotiation resolves — either a deal is struck or it breaks down.
+
+### Step 6 — Debrief
+
+After the simulation ends:
+
+```
+─────────────────────────────────────────────────────
+NEGOTIATION DEBRIEF
+─────────────────────────────────────────────────────
+
+FINAL OUTCOME: [what was agreed]
+BEST POSSIBLE OUTCOME: [what was realistically achievable]
+MONEY LEFT ON TABLE: [delta between outcome and best possible]
+
+WHAT YOU DID WELL:
+[2-3 specific moves that worked]
+
+WHAT TO DO DIFFERENTLY:
+[2-3 specific improvements]
+
+THE ONE RULE FOR THE REAL CONVERSATION:
+[Single most important tactical note for this specific offer]
+
+─────────────────────────────────────────────────────
+Run again to practice a different approach.
+─────────────────────────────────────────────────────
+```
+
+## Tone
+
+Play the recruiter straight. Real recruiters have budgets and constraints —
+they are not trying to cheat the candidate, but they will not volunteer money
+the candidate does not ask for. The goal is to make the simulation feel real
+enough that the actual conversation feels like a repeat.
+
+---
+
+## ✅ What to do next
+
+Run the simulation again with a different approach if you scored C or D.
+
+When you're ready for the real conversation:
+```
+npm run compare       ← if you have multiple offers, compare side by side
+```

package/resources/skills/skills/career/job-hunter/agents/offer-schedule.md

@@ -0,0 +1,99 @@
+# Schedule Interview — Calendar Agent
+
+## What This Does
+
+Creates a Google Calendar event for a scheduled interview with:
+- Prep checklist in the description
+- 1-hour reminder before the interview
+- 24-hour post-interview reminder to send thank-you note
+- 5-business-day follow-up reminder if no response
+
+Requires Google Calendar MCP connected in Claude.ai settings.
+
+## Instructions for Claude Code
+
+### Step 1 — Load inputs
+
+Read `inputs/job-description.md` for role and company.
+If `outputs/interview-prep.md` exists, read it for prep context.
+
+### Step 2 — Get interview details from user
+
+Ask the user:
+> What date and time is the interview? (e.g. "Tuesday June 3rd at 2pm ET")
+> Who are you interviewing with? (name and title if known)
+> Is it phone, video, or in-person?
+> Video link or dial-in number if applicable?
+
+### Step 3 — Create main interview event
+
+Use Google Calendar MCP to create an event with:
+- Title: "Interview — [Role] at [Company]"
+- Date/time: as provided
+- Duration: 60 minutes (default)
+- Location/link: video link or phone number if provided
+- Description:
+
+```
+INTERVIEW PREP CHECKLIST
+
+Before the interview:
+☐ Review outputs/interview-prep.md
+☐ Run the mock interview: npm run mock
+☐ Research [Company] — recent news, funding, products
+☐ Prepare 3 questions to ask the interviewer
+☐ Confirm the video link / dial-in 30 minutes before
+☐ Have your resume open in front of you
+
+Key talking points from your prep:
+[Pull the top 3 stories from outputs/interview-story-bank.md if it exists]
+
+Interviewer: [name and title if provided]
+```
+
+- Reminder: 60 minutes before
+
+### Step 4 — Create thank-you note reminder
+
+Create a second calendar event:
+- Title: "Send thank-you note — [Company] interview"
+- Date/time: next day at 9am
+- Description: "Run: npm run thankyou — Send within 24 hours of the interview"
+- Reminder: at time of event
+
+### Step 5 — Create follow-up reminder
+
+Create a third calendar event:
+- Title: "Follow up on [Company] interview if no response"
+- Date/time: 5 business days after the interview at 10am
+- Description: "If you haven't heard back, send one polite follow-up email."
+- Reminder: at time of event
+
+### Step 6 — Confirm to user
+
+Tell the user:
+> 3 calendar events created:
+> - Interview: [date/time]
+> - Thank-you reminder: [date] at 9am
+> - Follow-up reminder: [date] at 10am
+>
+> Your prep guide is in outputs/interview-prep.md
+> Run `npm run mock` before the interview.
+
+## Note on Google Calendar MCP
+
+This agent requires the Google Calendar MCP to be connected in your Claude.ai
+settings (Settings → Integrations → Google Calendar). The MCP must be enabled
+for Claude Code to access it.
+
+If not connected, Claude Code will prompt you to connect it.
+
+---
+
+## ✅ What to do next
+
+```
+npm run research      ← pull the company + interviewer brief
+npm run interview     ← build your prep guide
+npm run mock          ← practice before the real thing
+```