setup-schedule

setup-schedule is a skill for Claude Code from tmargolis/career-navigator. It costs 72 tokens per session (3,073 once invoked), scanned A, original, Apache-2.0.

A scheduled daily job-search brief that runs at a chosen time. It summarizes your applications, checks your Gmail inbox, flags follow-ups, and adds new job recommendations.

In plain words
What is it for?
Use it to receive a recurring overview of your job-search pipeline, email status updates, follow-up alerts, and newly recommended roles.
Why use it?
It reduces the need to manually review your applications, email, reminders, and job leads every morning. It also lets you update an existing daily schedule.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/jane/career.

Part of the career-navigator plugin — 46 skills, 3 MCP servers shipped together

Good fit Use it to receive a recurring overview of your job-search pipeline, email status updates, follow-up alerts, and newly recommended roles.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add tmargolis/career-navigator
Claude Code
/plugin install career-navigator

Made for: Claude Code.

Or install career-navigator, the plugin that ships this one along with the rest of its 46 skills, 3 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for setup-schedule

README.md
[![agentmods](https://agentmods.dev/badge/skills/tmargolis/career-navigator/setup-schedule/github.svg)](https://agentmods.dev/skills/tmargolis/career-navigator/setup-schedule)
Your own site
<a href="https://agentmods.dev/skills/tmargolis/career-navigator/setup-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/setup-schedule/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for setup-schedule

Your own site · 80×15
<a href="https://agentmods.dev/skills/tmargolis/career-navigator/setup-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/setup-schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.03073
Opus 5.5 $0.00029 $0.01229
Sonnet 5.5 $0.00014 $0.00615
Haiku 4.5 $0.00007 $0.00307

Measured 29d ago against content hash e072e57b1f11, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-schedule scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/setup-schedule/SKILL.md · 305 lines

How it starts

The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create or update the Career Navigator daily brief as a Cowork scheduled task. When the task fires each morning, it delivers a full operating brief: pipeline digest, Gmail inbox scan (two-pass strategy to catch missed status emails), follow-up alerts, and top new job recommendations appended to recommendations.json.


1. Verify Career Navigator setup

Read {user_dir}/CareerNavigator/profile.md.

If the profile is missing, output:

Daily schedule not set up: run /career-navigator:launch first to initialize Career Navigator.

Then stop.


2. Check for existing scheduled tasks

Load and call mcp__scheduled-tasks__list_scheduled_tasks. Look for a task named career-navigator-daily-brief and a task named career-navigator-pipeline-refresh (or whose prompt otherwise mentions Career Navigator).

If the daily brief task is found:

  • Display its current schedule and a one-line summary of its prompt
  • Ask: "A daily brief is already scheduled. Would you like to update the time, update the prompt, or keep it as-is?"
  • If the user wants to update: follow Steps 3–5 but use mcp__scheduled-tasks__update_scheduled_task with the existing task's ID instead of creating a new one
  • If the user wants to keep it: confirm "Your daily brief is already scheduled." and continue to check the pipeline-refresh task below rather than stopping

If the pipeline-refresh task is found: display its current schedule and offer the same update/keep choice, using update_scheduled_task if the user wants a change.

If both tasks already exist and the user wants to keep both as-is, confirm "Your daily brief and pipeline refresh are already scheduled." and stop.


3. Confirm preferred schedule(s)

Ask: "What time would you like your daily brief? Default is 7:00 AM daily."

Accept natural language and convert to a cron expression:

Input Cron
"7am" / "7:00 AM" / default 0 7 * * *
"6:30am" 30 6 * * *
"8am weekdays" 0 8 * * 1-5
"6am every day" 0 6 * * *

Read the full file on GitHub · 305 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 29d ago Changed · +43 lines · +14 tokens per session e072e57b1f11
  2. 1mo ago First seen · 262 lines · 58 tokens per session scan A dbfe5ce16c39

Subscribe to this mod's changes

setup-schedule is a skill published in the GitHub repository tmargolis/career-navigator (16 stars, last pushed 27d ago), licensed Apache-2.0. It adds 72 tokens to every session and 3,073 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

gsd-ns-manage

Invoke this Pi skill with /skill:gsd-ns-manage.

open-gsd/gsd-core · 16 tokens

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

to-spec

A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.

vinvcn/mattpocock-skills-zh-CN · 29 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

triage-inbox

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…

pedrohcgs/claude-code-my-workflow · 132 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens