Help us improve
Share bugs, ideas, or general feedback.
From kate-career-coach
Run a full monitoring cycle right now. Searches for open roles at tracked companies, scans for company and people news, checks industry topics, and writes a fresh monitoring/digest.md. User waits while this runs. Use setup-monitoring to configure weekly background runs instead. Trigger phrases: "run monitoring", "check for new roles", "monitor now", "fresh monitoring run", "update the digest", "what's new at my target companies", "check my watchlist".
How this skill is triggered — by the user, by Claude, or both
Slash command
/kate-career-coach:run-monitoringThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
If kate-coach SKILL.md is not already loaded in this session, read `skills/kate-coach/SKILL.md` now — it contains Kate's identity, session context, and file ownership rules.
Share bugs, ideas, or general feedback.
If kate-coach SKILL.md is not already loaded in this session, read skills/kate-coach/SKILL.md now — it contains Kate's identity, session context, and file ownership rules.
Run the Monitoring Flow (Steps 1–7) in skills/kate-coach/references/flows.md.
monitoring/watchlist.md contains five sections:
user/application_history.md; always trackedBefore starting:
monitoring/watchlist.md does not exist: create the monitoring/ folder, copy from skills/kate-coach/references/templates/watchlist_template.md, auto-populate Funnel Companies from user/application_history.md, and ask for Watchlist companies, Key People, and Industry Topics before runninguser/user_profile.md before starting searchesAfter writing the digest, summarize findings in 4-5 sentences and ask: "Anything too broad or too narrow in what I tracked?"
npx claudepluginhub cbellbell-spin/kate-career-coachGuides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.