I'm a few months into a job search after a layoff, and I kept running into the same two problems: I was spending too long deciding whether a job listing was worth my time, and my resume was drifting out of sync with what was actually landing in interviews.
So I built two Claude Code skills, reusable, file-based instructions Claude Code follows every time I invoke a slash command, to close both gaps. This is a walkthrough of how they work, why they're structured the way they are, and what I learned building them.
If you haven't used Claude Code skills before: a skill is just a markdown file with YAML frontmatter (name and description) that lives in .claude/skills/{skill-name}/SKILL.md. The description field is what Claude uses to decide when to trigger the skill automatically, and you can always invoke it explicitly with /skill-name.
The problem
Job searching produces a lot of repetitive judgment calls:
