application-tracker
/application-tracker
Track job applications - statuses, follow-ups, interviews, and reminders - in a structured pipeline. Use to keep a job search organized.
- Author
- Navinspire-ia ↗
- Repository
- navin ↗
- Licence
- AGPL-3.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
Track job applications - statuses, follow-ups, interviews, and reminders - in a structured pipeline. Use to keep a job search organized.
Original author description
Track job applications - statuses, follow-ups, interviews, and reminders - in a structured pipeline. Use to keep a job search organized.
How it works
- Overview
- Pipeline stages
- Tracker format
- Workflow
- Metrics that matter
- Rules
SKILL.md preview
---
name: application-tracker
description: Track job applications - statuses, follow-ups, interviews, and reminders - in a structured pipeline. Use to keep a job search organized.
metadata: {"navin":{"emoji":"🗂️","category":"careers","default_for":"career"}}
---
# Application Tracker
## Overview
A job search is a pipeline. The live book is the Career store (`career` tool + `#/career`). Optional markdown notes are a backup, never a second source of truth.
## Pipeline stages
`discovered → matched → ready → applied → replied → interview → offer → won / rejected`
## Tracker format
Prefer `career action=status` and `career action=stage`. The desk already writes `applications.md` next to the store on every save; read it with `career action=read file=applications.md`. Shape:
```markdown
| Company | Role | Applied | Stage | Last contact | Next action | Due | Notes |
```
Per-application notes file for serious processes: contacts, interview notes, questions asked, salary discussed.
## Workflow
1. Prepare a factual CV and cover for the selected job (`career action=prepare`).
2. `career action=apply` opens the manual employer submission flow and leaves the application ready. Mark stage=applied only after the user confirms a completed portal submission.
3. For professional email, configure and test the account using `mail_config` and `mail_test`. `mail_draft` previews the existing CV and cover attachments; `send_email` requires that draft's revision. Report an email application sent only when its receipt has status=accepted and a Message-ID. SMTP acceptance is not a delivery or read confirmation.
4. Automatic email and reply sync have separate persistent opt-ins. Auto-send uses the scheduled Career loop, an explicit published application address, a match threshold and daily limit. Never enable either opt-in from a legacy autopilot setting alone. `sync_mail` attaches actual replies to recorded applications; do not invent responses or send follow-ups automatically.
5. Follow-up policy: `followup-writer` + `career action=followup` wave=j3 then j7. Update the final outcome from the recruiter's response or the user's decision.
6. Schedule reminders with `cron` when requested: follow-ups due, interview prep (trigger `interview-coach` 2 days before), offer deadlines.
7. Weekly review: pipeline stats (applied/response/interview rates), what's stuck, this week's actions.
8. Post-decision: log the outcome and learnings (which channel/CV version converts best).
## Metrics that matter
- Response rate < 10% → fix targeting/CV (`ats-analyzer`)
- Interviews but no offers → fix prep (`interview-coach`)
## Rules
- Every live application has a "next action + date" - no passive rows.
- Keep interview notes verbatim where possible; they're gold for negotiation later.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Navinspire-ia/navin | 100 | AGPL-3.0 |
| joshdengxd/job-search-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version da627fe65137 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95job-hunt-tracker
When user asks to track job applications, manage job search, log interview, applied for job, job application status, track where I applied, job search organizer, application follow up, offer comparison, job pipeline, application stats, track rejection, track offer, job board,… - 86job-tracker
Go through the user's TakeMeUp job tracker — what's waiting for a reply, which follow-ups are due, what to update — and keep it current (add jobs, change status, set follow-up dates and notes). Use when the user asks about their applications, follow-ups, or job-search progress. - 90jobhunt-tracker
Keeps the user's job applications in jobhunt/applications.csv with tracker.py: add and update applications, list them by stage, and report the response rate, the stage funnel and stale applications that need a follow-up. The CSV opens in any spreadsheet app and never leaves the… - 98job-tracker
Tracks the user's job applications with the job-tracker MCP server. Adds new applications, lists them by status, updates a status (applied, replied, interview, rejected, offer) and finds applications that need a follow-up. Use when the user mentions applying to a job or sending… - 100job-application-manager
Runs the job-search pipeline. Adds jobs from a link or pasted posting, keeps stages and dates accurate, sets follow-ups, runs a weekly review (stale applications, next actions, funnel stats), records the exact resume version sent, and drafts networking, LinkedIn, referral,… - 86apply-pilot
Run a job or internship search with the apply-pilot CLI. Covers scanning postings, deduplicating and scoring them against the user's rubric, tracking applications, finding follow-ups that are due, linting letters, and showing the live dashboard. Use whenever the user mentions…