When to Use
User is job hunting — searching for positions, applying to companies, or preparing for interviews. Agent handles opportunity tracking, company research, application materials, and interview prep.
Architecture
Memory lives in ~/job-search/. See memory-template.md for setup.
~/job-search/
├── memory.md # HOT: preferences, target criteria
├── applications.md # Active pipeline
├── companies.md # Research on target companies
├── materials/ # CV versions, cover letters
└── archive/ # Closed applications
Quick Reference
| Topic |
File |
| Memory setup |
memory-template.md |
| Research patterns |
research.md |
| Interview prep |
interviews.md |
Core Rules
1. Quality Over Volume
- 5 targeted applications beat 50 generic ones
- Each application needs company-specific customization
- Never spray-and-pray — it burns reputation
2. Verify "Remote" Claims
Before recommending remote positions, check:
- Geographic restrictions ("US only", "EU timezone required")
- Tax/legal requirements in fine print
- Actual timezone overlap expectations
3. Detect Red Flags
| Signal |
Likely Meaning |
| Posted 3+ months |
Ghost job or high turnover |
| "Rockstar/ninja" language |
Overwork culture |
| Vague salary ("competitive") |
Below market |
| "Young dynamic team" |
Age bias risk |
| Recent mass layoffs |
Instability |
4. Preserve User Voice
- Materials must sound like the USER, not generic AI
- Ask for writing samples to match tone
- Never over-optimize with keywords at cost of authenticity
- Recruiters detect AI-written content — personalization matters
5. Track Application State
Maintain in ~/job-search/applications.md:
- Company, role, date applied
- Current status, next action
- Contacts, interview dates
- Follow-up reminders
6. Research Before Applying
For each target company, gather:
- Financial health (funding, revenue trends)
- Glassdoor sentiment (filter for recency)
- Recent news (layoffs, acquisitions)
- Hiring manager profile if findable
7. Adjust for User Context
| User Type |
Priority |
| Senior (10+ yrs) |
Network activation, discretion, salary negotiation |
| Junior/New grad |
Volume with quality, entry-level friendly companies |
| Career changer |
Transferable skills narrative, bridge roles |
| Urgent need |
Speed, temporary options, immediate income |
Common Traps
- ATS optimization kills authenticity — keyword stuffing passes filters but humans reject robotic text
- Salary data goes stale fast — verify ranges are current, not 2-year-old estimates
- "Perfect match" overconfidence — 60% requirement fit still means likely rejection
- Networking advice without context — cold outreach fails without warm introduction strategy
- Long-term advice for urgent needs — "build your brand" doesn't pay rent this month
1---2name: job-search3description: Navigate job hunting with application tracking, company research, and interview preparation.4---5
6## When to Use
7
8User is job hunting — searching for positions, applying to companies, or preparing for interviews. Agent handles opportunity tracking, company research, application materials, and interview prep.
9
10## Architecture
11
12Memory lives in `~/job-search/`. See `memory-template.md` for setup.
13
14```
15~/job-search/
16├── memory.md # HOT: preferences, target criteria
17├── applications.md # Active pipeline
18├── companies.md # Research on target companies
19├── materials/ # CV versions, cover letters
20└── archive/ # Closed applications
21```
22
23## Quick Reference
24
25| Topic | File |
26|-------|------|
27| Memory setup | `memory-template.md` |
28| Research patterns | `research.md` |
29| Interview prep | `interviews.md` |
30
31## Core Rules
32
33### 1. Quality Over Volume
34- 5 targeted applications beat 50 generic ones
35- Each application needs company-specific customization
36- Never spray-and-pray — it burns reputation
37
38### 2. Verify "Remote" Claims
39Before recommending remote positions, check:
40- Geographic restrictions ("US only", "EU timezone required")
41- Tax/legal requirements in fine print
42- Actual timezone overlap expectations
43
44### 3. Detect Red Flags
45| Signal | Likely Meaning |
46|--------|---------------|
47| Posted 3+ months | Ghost job or high turnover |
48| "Rockstar/ninja" language | Overwork culture |
49| Vague salary ("competitive") | Below market |
50| "Young dynamic team" | Age bias risk |
51| Recent mass layoffs | Instability |
52
53### 4. Preserve User Voice
54- Materials must sound like the USER, not generic AI
55- Ask for writing samples to match tone
56- Never over-optimize with keywords at cost of authenticity
57- Recruiters detect AI-written content — personalization matters
58
59### 5. Track Application State
60Maintain in ~/job-search/applications.md:
61- Company, role, date applied
62- Current status, next action
63- Contacts, interview dates
64- Follow-up reminders
65
66### 6. Research Before Applying
67For each target company, gather:
68- Financial health (funding, revenue trends)
69- Glassdoor sentiment (filter for recency)
70- Recent news (layoffs, acquisitions)
71- Hiring manager profile if findable
72
73### 7. Adjust for User Context
74| User Type | Priority |
75|-----------|----------|
76| Senior (10+ yrs) | Network activation, discretion, salary negotiation |
77| Junior/New grad | Volume with quality, entry-level friendly companies |
78| Career changer | Transferable skills narrative, bridge roles |
79| Urgent need | Speed, temporary options, immediate income |
80
81## Common Traps
82
83- **ATS optimization kills authenticity** — keyword stuffing passes filters but humans reject robotic text
84- **Salary data goes stale fast** — verify ranges are current, not 2-year-old estimates
85- **"Perfect match" overconfidence** — 60% requirement fit still means likely rejection
86- **Networking advice without context** — cold outreach fails without warm introduction strategy
87- **Long-term advice for urgent needs** — "build your brand" doesn't pay rent this month
johnalbertini14-glitch