Morning briefing
A forkable job-search operating system for Claude — cover letters, interview prep, transcript Q&A, thank-you notes, and daily pipeline briefings, all in your own voice.
npx -y skills add ldenson1120/job-search-os --skill morning-briefingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
This skill should be used when the user says "morning briefing", "brief me", "what's on my plate today", "pipeline update", "what do I have today", "give me my briefing", "what's active in my search", or any variation asking for a daily snapshot of their job search and schedule.
SKILL.md
2.5 KB, as published. Nobody here has run it
Morning Briefing
Generate a fast, useful daily snapshot of the job search. The goal is for the user to be able to read this in under two minutes and know exactly what they need to do today.
What to do
-
Load the pipeline. Read
context/TARGET_COMPANIES.md. This is the source of truth for what's active. -
Pull live data if available. If ~~calendar is connected, pull today's events. If ~~email is connected, scan for unread messages from recruiters, hiring managers, or companies in the pipeline. If ~~project tracker is connected, check for any tasks or follow-ups logged there. Work with whatever's available — the briefing is still useful without connectors.
-
Generate the briefing. Structure it as:
Today (only if calendar is connected or user mentioned specific events) List any interviews, recruiter calls, or job-search-related events today. For each: company, role, time, who you're talking to. Flag if any prep is needed.
Pipeline: Active Roles that are in motion right now (phone screen through offer). For each: company, role, current stage, last touch date (if available), and what the next action is. Keep it one line per role.
Pipeline: Needs Attention Roles that have gone quiet or where action is overdue. Flag what's stalled and what needs a nudge. Be specific: "No contact in 12 days" is more useful than "stale."
Pipeline: Watching Roles you've applied to or are researching but aren't active yet. Brief — just the company and role, so the user knows they're tracked.
Priority action today One thing. The single most important job-search action for today. If there's an interview, that's it. If not, pick the most time-sensitive follow-up or the most promising stale thread to resurrect.
-
Keep it tight. No preamble, no closing summary. The briefing starts with the first piece of information and ends with the priority action.
Tone
Treat this like a chief of staff briefing, not a status report. The user already knows their situation — remind them of what matters and what needs action. If something has been stuck for weeks, say so plainly.