agentleFS
MahashwethaMahashwetha/Job-search-email-system-claude/.claude/skills/update-status/SKILL.md

update-status

Skill12 starsChanged 11 days agoMITView on GitHub

This skill should be used when the user wants to change the status of a job already in the tracker (List.xlsx), especially after a company responds. Triggers on phrases like "[company] called me back", "[company] replied", "got an interview with [company]", "move [company] to in progress", "set [company] to in progress", "mark [company] as done/applied again", "undo rejection for [company]".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run from the project root (claude-job-agent/):

    line 16
  2. Very specific:

    Add --dry-run to preview.

    line 21
  3. Very specific:

    If the output says AMBIGUOUS (the company has several rows), show the rows and ask which role, then re-run with --row N (or --all if the …

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Job Status

Change the status of an existing tracker row with the bundled script. For rejections the mark-rejected skill still works; this script is for everything else (and can also set Rejected on one specific row).

Status values

  • done = applied
  • In progress = ONLY when the company called back / replied / scheduled an interview
  • Rejected = rejected (adds strikethrough)

Steps

Run from the project root (claude-job-agent/):

python .claude/skills/update-status/scripts/update_status.py --company "Galadrim" --status "In progress" --note "phone screen booked"
python .claude/skills/update-status/scripts/update_status.py --row 352 --status "In progress"
  • Add --dry-run to preview.
  • If the output says AMBIGUOUS (the company has several rows), show the rows and ask which role, then re-run with --row N (or --all if the user means all of them).
  • --note is optional; it is appended to the comments column as YYYY-MM-DD: note, keeping existing comments.

The script takes the shared tracker lock, backs up List.xlsx first, adds strikethrough for Rejected and removes it for any other status.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.