application-tracker
Skill0 starsChanged 7 months agoMITView on GitHub
Track and manage job applications: check status of all applications, identify follow-up opportunities (7+ days no response), cross-reference networking contacts, generate action lists, and draft follow-up messages. Use for application dashboard, follow-up checks, and weekly application reviews.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- ZoolCoder/scoutjobstheir own version, first seen Nov 1, 2026
- FynePool/job-hunter-templatetheir own version, first seen Oct 25, 2026
- kevinmmiddleton/recruiter-bfftheir own version, first seen Oct 17, 2026
- bydeng01/phd-application-skilltheir own version, first seen Jun 17, 2026
- wexxwuther/job-huntertheir own version, first seen May 21, 2026
- xiding-code/job-application-skillstheir own version, first seen Apr 1, 2026
Used with
Projects with it also use interview-prep.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 4 projects that use this
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- wexxwuther/job-hunter★ 4same name
- xiding-code/job-application-skills★ 4same name
- ZoolCoder/scoutjobs★ 4same name
- FynePool/job-hunter-template★ 3same name
- kevinmmiddleton/recruiter-bff★ 3same name
- bydeng01/phd-application-skill★ 1same 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- applySkill
- cold-outreachSkill
- company-deep-diveSkill
- contact-populationSkill
- job-searchSkill
- meeting-prepSkill
- onboard-userSkill
- resume-tailorSkill
- session-checkpointSkill
- session-endSkill
- session-startSkill
- warm-followupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
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
- Very specific: line 23
All queries filtered by (user_id,eq,${ACTIVE_USER_ID})
- Very specific: line 68
Check if the company has networking contacts in target_contacts.
- Very specific: line 69
Check if sales_pipeline entries exist.
- Distinctive: line 70
If warm: recommend following up through the contact instead of cold follow-up.
- Distinctive: line 71
If the contact recently responded: leverage the warm connection.
- Distinctive: line 154
Update the database: after each follow-up action.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Application Tracker
Application status monitoring, follow-up scheduling, and cross-workstream intelligence.
What This Skill Does
- Status dashboard — overview of all applications by status
- Follow-up detection — identify applications needing follow-up (7+ days)
- Cross-workstream intelligence — link applications to networking contacts
- Action list generation — prioritised next actions across all applications
- Follow-up drafting — draft follow-up messages for stale applications
- Weekly review — comprehensive weekly application status report
Prerequisites
- Database access via configured MCP (
mcp__nocodb__*,${NOCODB_BASE_ID}) applicationstable populated- All queries filtered by
(user_id,eq,${ACTIVE_USER_ID})
Quick Start
"Check my applications" / "Application dashboard"
"Which applications need follow-up?"
"Run weekly application review"Workflow
Dashboard view
Query the applications table and display:
| Company | Job Title | Applied | Status | Days | Follow-Up? | Contact? |
|---------|-----------|---------|--------|------|------------|----------|
| Acme | Sr PM | Jan 15 | Submitted | 20 | OVERDUE | Yes (3) |
| Globex | AI PM | Jan 28 | Acknowledged | 7 | Due today | No |
| Initech | Product | Feb 1 | Preparing | 3 | N/A | Yes (1) |Follow-up detection
mcp__nocodb__list_records({
base_id: "${NOCODB_BASE_ID}",
table_name: "applications",
where: "(application_status,eq,Submitted)~and(user_id,eq,${ACTIVE_USER_ID})",
sort: "application_date",
limit: 100
})
// Filter in post-processing for date math (>= 7 days since application_date).Categorise:
- First follow-up (7-13 days): professional check-in
- Second follow-up (14-20 days): value-add follow-up with new insight
- Past due (21+ days): final follow-up or mark as no-response
Cross-workstream check
For each application needing follow-up:
- Check if the company has networking contacts in
target_contacts. - Check if
sales_pipelineentries exist. - If warm: recommend following up through the contact instead of cold follow-up.
- If the contact recently responded: leverage the warm connection.
Action list generation
## Priority Actions (Today)
1. Follow up on Acme Sr PM (20 days, warm — contact: Jane Smith)
2. Follow up on Globex AI PM (7 days, cold)
## This Week
3. Prepare application for Initech Product Manager (score: 8)
4. Check Acme career page for new postings
## Monitoring
5. Globex — acknowledged 3 days ago, check again in 4 days
6. Initech — interview scheduledFollow-up message drafting
Cold follow-up (no networking contact):
Subject: Re: [Job Title] Application — [New Value Add]
[Name],
Quick follow-up on my application for [Job Title]. Since applying,
[new relevant development — company news, industry insight, or
personal achievement].
[Brief value reminder — 1-2 sentences about fit].
Happy to discuss at your convenience.
Best,
[user full name]Warm follow-up (via networking contact):
Recommend reaching out to [Contact Name] instead:
"Hi [Contact], I applied for the [Job Title] role on your team
[X days ago]. Any insight into the timeline? Happy to provide
additional context if helpful."Weekly review report
# Application Weekly Review — Week of [Date]
## Summary
- Total active applications: X
- New applications this week: Y
- Responses received: Z
- Follow-ups sent: W
## By Status
- Preparing: X
- Submitted (awaiting): Y
- Acknowledged: Z
- Screening: W
- Interview Scheduled: V
- Rejected: R
## Actions Taken This Week
1. ...
## Priority Actions Next Week
1. ...
## Pipeline Health
- Average response time: X days
- Response rate: Y%
- Warm application rate: Z%Rules
- ALWAYS check cross-workstream — flag warm-application opportunities.
- Follow-up timing: 7 days first, 14 days second, then close.
- Never follow up more than twice on cold applications.
- Warm follow-ups through contacts are preferred over cold follow-ups.
- Update the database after each follow-up action.
- Create Interaction records for all follow-up activities.
Integration with other skills
job-search: feeds new Job Postings → triggers application prepapply: creates Application records → tracked hereresume-tailor: generates resume versions → linked to applicationscold-outreach: networking contacts → warm-application opportunitieswarm-followup: handles warm follow-ups at networked companies
Reference Documentation
operating-procedures/DIRECT-APPLICATION-PROCEDURE-v1.md
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.

