track-applications
Skill7 starsChanged 3 days agoMITView on GitHub
Record and review the progress of Openings applications - "X replied", "I applied to Y", "I got rejected by Z", "track my applications", "what's waiting?", "close the ones that never answered". Records only what the owner reports.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- billkhiz-bit/honest-tailortheir own version, first seen Nov 16, 2026
- Himalayas-App/himalayas-plugintheir own version, first seen Nov 1, 2026
- khadinakbarlabs/vibejobs-plugintheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- billkhiz-bit/honest-tailor★ 0same name
- Himalayas-App/himalayas-plugin★ 0same name
- khadinakbarlabs/vibejobs-plugin★ 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- maintain-careerSkill
- manage-sourcesSkill
- openingsSkill
- prepare-applicationsSkill
- prepare-interviewSkill
- setup-openingsSkill
- triage-jobsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read openings first. You record what the owner tells you.
- Very specific: line 16
Search applications_list by company or title.
- Very specific: line 23
Use applications_update; the date is the one the owner gives, today otherwise.
- Very specific: line 38
Read workspace_context counts, then applications_list:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Track your applications
Read openings first. You record what the owner tells you; you never learn an outcome from silence and never contact anyone.
Find the application
Search applications_list by company or title. When more than one matches,
or the job has a Closed attempt and an open one, ask which. A job with no
application yet: start one with applications_create only when the owner
says they applied to it.
Record what happened
Use applications_update; the date is the one the owner gives, today
otherwise.
- "I applied": set Applied with the day they sent it.
- A reply (interview invitation, offer, rejection, or anything else such as a request for references): record it as a reply with a short note in the owner's words. A reply moves the stage by itself; do not set the stage too.
- A mistake in a recorded reply: correct or delete that reply.
- "I won't pursue it": close it as not pursued. An employer's rejection is a reply, not this.
- Details worth keeping (interviewer names, next steps) go in a note on the application.
What's waiting
Read workspace_context counts, then applications_list:
- Waiting on the owner: Ready applications, deadlines first; Shortlisted ones blocked by a requirement only they can resolve.
- Waiting on employers: Applied and Interview, with days since sending and the last reply.
- Overdue: Applied with no reply past the no-reply period.
Close overdue ones as no response only when the owner asks, or Working with me says to. Otherwise list them and ask. Never close an Interview or Offer as no response.
For "how is it going", stats_get gives reply and interview rates; with only
a few applications give counts, not percentages.
Report back
In chat: what you recorded, with the stage each application is now in; what waits on the owner, deadlines first; overdue applications and the question whether to close them.
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
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.

