agentleFS
Sign inStart free
muggl3mindmuggl3mind/career-manager/job-tracker/SKILL.md

job-tracker

Skill24 starsChanged 42 days agoMITView on GitHub

Track job applications, manage follow-ups, and generate progress reports. Use when adding applications, updating status, checking pipeline, or finding stale applications needing follow-up.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. dsdev-d/takemeup-mcp★ 0same name
    2. uttej-reddy/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Add new application. Default: status=researching, priority=2.

    line 15
  2. Distinctive:

    Add timestamped note to application.

    line 31
  3. Distinctive:

    Add or update contact info.

    line 34
  4. Very specific:

    After any command that changes data/applications.csv (add, update, notes, contact, priority), regenerate the dashboard automatically:

    line 44
  5. Distinctive:

    Do not ask the user; this keeps the dashboard in sync with the tracker.

    line 50
  6. Very specific:

    Use scripts/tracker_commands.py for all CSV operations.

    line 54
  7. Very specific:

    NEVER edit applications.csv directly: Always use scripts/tracker_commands.py functions (add_application, update_status, add_note, …

    line 74
  8. Very specific:

    After any tracker modification, sync to Todoist using scripts/todoist_sync.py (skipped automatically if integrations.todoist_enabled: false …

    line 75
  9. Distinctive:

    Read CSV before any operation

    line 76
  10. Distinctive:

    Write CSV after any modification

    line 77
  11. Distinctive:

    Use ISO date format (YYYY-MM-DD)

    line 79
  12. Very specific:

    If company is not found on update operations, return explicit "not found" and suggest list.

    line 94
  13. Distinctive:

    If priority/status is invalid, reject write and return allowed values.

    line 95
  14. Distinctive:

    If CSV is malformed, stop write operations and require repair before proceeding.

    line 96
  15. Distinctive:

    After tracker operations, suggest the next logical action:

    line 100
  16. Very specific:

    After followup shows stale applications: "Want me to draft follow-up text for these?" (compose using …

    line 102
  17. Very specific:

    After add: no suggestion needed (user just added it)

    line 103
  18. Very specific:

    After list or report: if any applications need follow-up, mention it

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Job Application Tracker

Manage the job hunt pipeline. All data in data/applications.csv.

Commands

Parse user input to determine which command to run:

add [company] [role]

Add new application. Default: status=researching, priority=2. Override with -p 1|2|3.

update [company] [status]

Change status. Valid: researching → applied → interviewing → offer | rejected | declined Auto-updates last_contact to today.

list

Show active applications grouped by priority (excludes offer/rejected/declined).

followup

Show applications needing follow-up (7+ days since last contact).

report

Weekly pipeline summary: counts, activity, what needs attention.

notes [company] [text]

Add timestamped note to application.

contact [company] [name] [email]

Add or update contact info.

priority [company] [1|2|3]

Change priority level.

archive

Show all applications including closed ones.

After Any Mutation

After any command that changes data/applications.csv (add, update, notes, contact, priority), regenerate the dashboard automatically:

uv run job-search/scripts/ops/generate_dashboard.py

Do not ask the user; this keeps the dashboard in sync with the tracker.

Implementation

Use scripts/tracker_commands.py for all CSV operations. Import and call functions directly — don't rewrite CSV logic.

CSV Schema

ColumnDescription
companyCompany name
roleJob title
job_urlLink to posting
statusCurrent status
date_addedWhen first added (YYYY-MM-DD)
date_appliedWhen formal application submitted (YYYY-MM-DD)
last_contactLast communication date
contact_nameHiring manager/recruiter
contact_emailContact email
priority1=high, 2=standard, 3=backlog
notesTimestamped notes

Rules

  • NEVER edit applications.csv directly. Always use scripts/tracker_commands.py functions (add_application, update_status, add_note, add_contact). Direct CSV edits bypass Todoist sync and validation.
  • After any tracker modification, sync to Todoist using scripts/todoist_sync.py (skipped automatically if integrations.todoist_enabled: false in config.yaml).
  • Read CSV before any operation
  • Write CSV after any modification
  • Preserve all existing data
  • Use ISO date format (YYYY-MM-DD)

Integration

  • company-research → company dossier (culture, signals, fit) that feeds tracking decisions before applying
  • cv-tailor → prepares materials before applying

Reference Files

  • data/applications.csv — Main data store
  • scripts/tracker_commands.py — Python implementation
  • scripts/add_to_tracker.py — Batch add from target companies
  • references/example-output.md — Output format examples

Error Handling

  • If company is not found on update operations, return explicit "not found" and suggest list.
  • If priority/status is invalid, reject write and return allowed values.
  • If CSV is malformed, stop write operations and require repair before proceeding.

After Completion

After tracker operations, suggest the next logical action:

  • After followup shows stale applications: "Want me to draft follow-up text for these?" (compose using job-search/templates/follow-up-email.md, user copies to their email client)
  • After add: no suggestion needed (user just added it)
  • After list or report: if any applications need follow-up, mention it

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.

Check your setup, free