Job application tracker
Skill Faizee-Asad/job-seeker-claude-skills/.claude/skills/job-application-tracker
AI-powered Claude Skills for job seekers. Resume optimization, ATS keyword audit, cover letter generation, interview prep, recruiter outreach, and job application tracking.
npx -y skills add Faizee-Asad/job-seeker-claude-skills --skill job-application-trackerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create, update, clean, and summarize CSV job application trackers with statuses, next actions, contacts, follow-up dates, and notes.
SKILL.md
1.5 KB, as published. Nobody here has run it
Job Application Tracker
Use this skill when the user wants to create, update, organize, or summarize a job application tracker.
CSV schema
Use these columns by default:
company,role,status,source,url,applied_date,next_action,next_action_date,contact,notes,last_updated
Status values
Recommended statuses:
- Saved
- Applied
- Recruiter screen
- Interviewing
- Take-home
- Final round
- Offer
- Rejected
- Withdrawn
- Closed
Workflow
- If no tracker exists, create one with the default schema.
- Add one row per company + role.
- Update existing rows instead of duplicating when company + role match.
- Suggest a next action if missing.
- Suggest a next action date if missing.
- Preserve old notes unless the user asks to replace them.
- Summarize upcoming actions.
Output format
When creating or updating a tracker, provide:
## Tracker update
- Added/updated: [Company] — [Role]
- Status: [Status]
- Next action: [Next action]
- Next action date: [Date]
## CSV row
```csv
company,role,status,source,url,applied_date,next_action,next_action_date,contact,notes,last_updated
...
## Privacy
Do not store unnecessary sensitive data in the tracker. Avoid home addresses, IDs, private references, or personal health/family information.
Gives 0 of the 12 instructions most note taking skills give
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 35 of 686, across 11 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 10 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- create a tracker with default schema
- add one row per company and role
- update existing matching rows
- suggest missing next actions
- output the markdown tracker update
- output the CSV row
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.