targets
Skill136 starsChanged 3 days agoMITView on GitHub
Active direct sourcing. Registers and creates standout profiles on the 40 target companies' career sites, then applies to matching positions.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acp-connectorSkill
- applySkill
- browser-automationSkill
- dailySkill
- dashboardSkill
- dbSkill
- memorySkill
- newsSkill
- onboardingSkill
- polishSkill
- profileSkill
- radarSkill
- referralsSkill
- strategySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
36 rules. About 0 are common, 21 are distinctive, and 15 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
Before applying to any job, verify against Must-haves from users.data.job_preferences.
- Very specific: line 53
Not in user's accepted locations (per location and timezones preferences)
- Distinctive: line 64
Detect ATS: if not already identified.
- Very specific: line 83
If no account creation possible → mark registration_status = 'manual_login_needed', notify user (Gold Rule 5)
- Distinctive: line 100
Subscribe to job alerts: if the ATS or career site supports it.
- Distinctive: line 101
Greenhouse: look for "Subscribe to alerts" or "Email me new jobs" link on the job board.
- Distinctive: line 102
Lever: look for "Subscribe" or "Alerts" button.
- Distinctive: line 103
Ashby: look for "Subscribe to alerts" link.
- Distinctive: line 104
Workable: look for "Subscribe" or "Job Alerts" link.
- Distinctive: line 105
SmartRecruiters: look for "Job Alerts" or "Subscribe" link.
- Distinctive: line 106
Teamtailor: look for "Subscribe" or "Alerts" link.
- Very specific: line 109
Custom ATS: look for any "Subscribe", "Alerts", "Notify me", or RSS feed icon.
- Very specific: line 112
Email: use the user's email (from users.data.profile.email) so alerts route through the Gmail filter
- Distinctive: line 113
Update DB with alert status:
- Distinctive: line 117
If alerts not available on the platform, note it:
- Very specific: line 140
Check dedup against applications table
- Distinctive: line 141
If already applied → skip
- Very specific: line 143
Gate: only run if referrals is in strategy.sources_active.
- Very specific: line 145
If internal contact/alumni/ex-colleague found: stage referral request in messages and set card status to discovered (Strategy #1).
- Very specific: line 146
If NO internal contact found: if strategy.cold_outreach = true, extract recruiter info and stage recruiter outreach DM in messages …
- Very specific: line 210
If automation fails after 3 attempts → mark company as manual_apply_needed, notify user
- Distinctive: line 211
Create account first, then search and apply
- Distinctive: line 235
Look for "Apply" or "Postulate" or "Send CV" button
- Distinctive: line 236
If it redirects to LinkedIn → apply via LinkedIn flow instead
- Distinctive: line 237
If it's an email submission → draft email with CV attached, show to user (Gold Rule 6)
- Very specific: line 238
If no apply button → mark as no_application_system in notes
- Distinctive: line 242
Wait 3-5 seconds between actions (don't spam clicks)
- Distinctive: line 243
Don't apply to more than 5 jobs per company per session
- Distinctive: line 244
If a captcha or block appears → pause and notify user
- Distinctive: line 257
If the session is interrupted, the next run picks up where it left off by querying:
- Very specific: line 309
Browser: always use node .agents/skills/browser-automation/scripts/browser.js for open/close/goto.
- Very specific: line 310
Resumable: Every action updates company_registrations.
- Very specific: line 311
Must-haves are non-negotiable: Don't register or apply to companies that don't match the user's job_preferences (remote, location, AI …
- Distinctive: line 313
Gold Rule 5: If manual login needed → open headed browser, notify user, wait
- Distinctive: line 314
Gold Rule 6: If applying via email (not ATS form) → show draft to user before sending
- Very specific: line 316
Dedup: Check applications table before applying.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Targets — Active direct sourcing
Trigger
Keyword: targets
The user says targets (or variants: "register on companies", "apply to target companies", "company direct", "direct sourcing") and the full registration + application flow is triggered.
Purpose
The third sourcing pillar alongside radar (passive alerts) and apply (LinkedIn Easy Apply). This flow goes directly to the career sites of the target companies (loaded from users.data.target_companies in DB), registers the user, creates a standout profile, and applies to matching positions.
Pre-flight
- Browser: always use
node .agents/skills/browser-automation/scripts/browser.jsfor open/close/goto. See AGENTS.md "Browser session" and "Parallel execution" for details. Never callagent-browser opendirectly - Parallel execution: if running alongside other flows (e.g:
applyornews), attach a session withnode .agents/skills/browser-automation/scripts/browser.js attach --session targets-1and pass--session targets-1to all browser commands and scripts. Usedetachwhen done (neverclose— it's ref-counted) - Load active preferences (see
memoryskill):node scripts/db.js "SELECT category, key, value, confidence, source FROM preferences WHERE user_id = <user_id> AND status = 'active' ORDER BY category, key" - Load strategy (see AGENTS.md "Strategy levels"):
Respect:node scripts/db.js "SELECT data->'strategy' AS strategy FROM users WHERE id = <user_id>"targets_batch_size(max companies per session, 0 = don't run, "all" = no limit),match_threshold,relax_must_haves. Iftargetsis not insources_active, skip this flow entirely - Load profile, job preferences, CV and photo paths:
node scripts/db.js "SELECT data->'profile' AS profile, data->'job_preferences' AS prefs, data->'cv_path' AS cv_path, data->'photo_path' AS photo_path, data->'style_profile' AS style_profile FROM users WHERE id = <user_id>" - Load company registrations to see current state:
node scripts/db.js "SELECT id, company, region, sector, careers_url, ats_platform, registration_status, profile_completed, applied_jobs_count, notes FROM company_registrations WHERE user_id = <user_id> ORDER BY registration_status, region, company" - Load existing applications for dedup:
node scripts/db.js "SELECT company, url FROM applications WHERE user_id = <user_id>"
Must-haves filter (from job_preferences)
Before applying to any job, verify against Must-haves from users.data.job_preferences. The filter is dynamic, not hardcoded. For each Must-weighted preference, discard if the job doesn't match. Common examples:
- Work mode mismatch (if
work_mode.weight = Must, role must match the user's preferred mode. Ifrelax_must_havesresolves to includework_mode, accept partial matches) - Sector/specialization mismatch (if
sector.weight = Must, role must be in the user's preferred sector) - Role level in
deal_breakers(the user defines their own deal-breakers, never hardcoded. If the user listed "junior" as a deal-breaker, discard junior roles. If they didn't, don't) - In
industries_avoidlist (perindustries_avoid.weight) - Salary below
job_preferences.salary.value.min(if mentioned andsalary.weight = Must) - Not in user's accepted locations (per
locationandtimezonespreferences)
Gold Rule 4: The user's career goal and what's sacrificable live in users.data.profile.career_goal and users.data.job_preferences. Read them from DB. Don't discard roles based on hardcoded assumptions about role type or seniority. Check relax_must_haves (resolved from users.data.job_preferences) to know which Must-haves are relaxed for the current strategy level.
Flow
Phase 1 — Registration & profile creation
For each company with registration_status = 'pending' (or profile_completed = false):
- Navigate to careers URL using
node .agents/skills/browser-automation/scripts/browser.js goto <url>(oropenif no session) - Detect ATS if not already identified. Common signals:
- URL contains
greenhouse.io→ Greenhouse - URL contains
lever.co→ Lever - URL contains
ashbyhq.com→ Ashby - URL contains
workday→ Workday - URL contains
smartrecruiters.com→ SmartRecruiters - URL contains
teamtailor.com→ Teamtailor - URL contains
eightfold.ai→ Eightfold - URL contains
successfactors→ SAP SuccessFactors - URL contains
workable.com→ Workable - URL contains
phenom→ Phenom - URL contains
attrax→ Attrax - URL contains
gupy→ Gupy - None of the above → Custom (manual inspection needed)
- URL contains
- Find the registration / sign up / create account page
- Login method priority:
- Google login (preferred, reuses Gmail session from onboarding)
- LinkedIn login (reuses LinkedIn session from onboarding)
- Email + password (create account, save credentials to
company_registrations.dataas{email, password}) - If no account creation possible → mark
registration_status = 'manual_login_needed', notify user (Gold Rule 5)
- Complete profile to make it stand out:
- Full name (from
users.data.profile.full_name) - Title/headline: use
profile.title+ top skills (e.g: "<Title>|<Top Skills>") - Summary/bio: use
profile.summary, adapted to the platform's character limit - Location: from
users.data.personal_info(city, country) orform_answers.location - Upload CV: use
profile.cv_pathorpersonal_info.cv_pdf_path(from DB, never hardcoded) - Upload photo: use
users.data.photo_pathif the platform accepts it - Skills: add all from
profile.skills - Experience: fill from
profile.experienceif the platform has structured fields - Languages: from
profile.languages - Work preferences: from
job_preferences.modalities,job_preferences.role_types - Salary expectation: from
job_preferences.salary.value(only if field is required)
- Full name (from
- Update DB after each company:
node scripts/db.js "UPDATE company_registrations SET registration_status = 'registered', profile_completed = true, ats_platform = '<ats>', login_method = '<google|linkedin|email>', profile_url = '<url if available>', last_visit_at = NOW(), updated_at = NOW(), data = '<json with credentials if email login>'::jsonb WHERE id = <id>" --write - Subscribe to job alerts if the ATS or career site supports it. This is critical for passive monitoring of new openings:
- Greenhouse: look for "Subscribe to alerts" or "Email me new jobs" link on the job board. Enter email, select job categories or keywords (AI, Engineering, Remote)
- Lever: look for "Subscribe" or "Alerts" button. Enter email, select departments or locations
- Ashby: look for "Subscribe to alerts" link. Enter email, select teams or locations
- Workable: look for "Subscribe" or "Job Alerts" link. Enter email, select job categories
- SmartRecruiters: look for "Job Alerts" or "Subscribe" link. Enter email, select filters
- Teamtailor: look for "Subscribe" or "Alerts" link. Enter email, select categories
- Eightfold: AI matching may auto-suggest relevant jobs. Look for "Save search" or "Alerts" option
- Workday: often has " Save Search" or "Job Alerts" after searching. Set up with filters
- Custom ATS: look for any "Subscribe", "Alerts", "Notify me", or RSS feed icon. If none exists, skip this step and note it in
company_registrations.notes - Keywords for alerts: derived from
profile.skills,profile.title, andjob_preferences(e.g: AI, the user's primary role, seniority level, key tech skills) - Frequency: daily if available, weekly otherwise
- Email: use the user's email (from
users.data.profile.email) so alerts route through the Gmail filter - Update DB with alert status:
node scripts/db.js "UPDATE company_registrations SET data = jsonb_set(COALESCE(data, '{}'::jsonb), '{alerts_subscribed}', 'true'::jsonb), notes = COALESCE(notes, '') || ' | Alerts subscribed' WHERE id = <id>" --write - If alerts not available on the platform, note it:
node scripts/db.js "UPDATE company_registrations SET notes = COALESCE(notes, '') || ' | No native alerts' WHERE id = <id>" --write
If a company has no matching roles or no remote options:
- Mark
registration_status = 'no_fit'with reason innotes - Do not register
If a company requires manual login (no Google/LinkedIn, no email signup):
- Mark
registration_status = 'manual_login_needed' - Open headed browser (Gold Rule 5), notify user, wait for confirmation
Phase 2 — Search & apply
For each company with registration_status = 'registered' and applied_jobs_count = 0 (or user requests more):
- Navigate to the company's job board
- Search with filters:
- Keywords: derived from
profile.title,profile.skills, andjob_preferences(the user's primary role + key skills + seniority level) - Location: from
job_preferences.locationandjob_preferences.timezones - Seniority: from
job_preferences.seniority
- Keywords: derived from
- Filter by Must-haves (see above). For each matching job:
- Check dedup against
applicationstable - If already applied → skip
- Check dedup against
- Warm Sourcing & Referral Pre-Check (Strategy #1 & #4):
- Gate: only run if
referralsis instrategy.sources_active. If not, skip to step 5. - Run
node scripts/linkedin-warm-sourcing.js --company "<Company>" --role "<Role>" --json - If internal contact/alumni/ex-colleague found: stage referral request in
messagesand set card status todiscovered(Strategy #1). - If NO internal contact found: if
strategy.cold_outreach = true, extract recruiter info and stage recruiter outreach DM inmessages(Strategy #4). Ifcold_outreach = false, skip outreach. Either way, micro-align CV keywords to JD viascripts/generate-cv.jsand proceed to ATS application.
- Gate: only run if
- Apply following the ATS-specific flow (see ATS guide below)
- Register each application in DB:
node scripts/db.js "INSERT INTO applications (user_id, platform, company, role, url, status, data) VALUES (<user_id>, '<company_lowercase>', '<company>', '<role>', '<url>', 'applied', '<json with match_reason, ats_type, location, salary_if_known>'::jsonb)" --write - Update company registration:
node scripts/db.js "UPDATE company_registrations SET applied_jobs_count = applied_jobs_count + <N>, last_applied_at = NOW(), updated_at = NOW() WHERE id = <id>" --write
Phase 3 — Report
Present to user:
## Targets report
### Registration summary
- Registered: X/40 companies
- Profile completed: X/40
- No fit (no remote/<country>/tech): X
- Manual login needed: X
### Applications summary
- Total applications via targets: X
- By company:
| Company | Applied | Roles |
|---|---|---|
| Mercado Libre | 3 | Sr EM AI, AI Architect, Platform Eng |
| Bitso | 2 | Sr EM, AI Engineer |
...
### Pending (need attention)
- [manual_login_needed] Santander Tecnología — requires manual login
- [no_fit] Nubank — all roles hybrid, no 100% remoteATS-specific application guide
Greenhouse
- URL pattern:
job-boards.greenhouse.io/<company>orboards.greenhouse.io/<company> - "Apply" button → form with personal info, resume upload, custom questions
- Resume: upload CV file directly
- Questions: answer based on profile (years of experience, salary, location, work authorization)
- Submit → confirmation page
Lever
- URL pattern:
jobs.lever.co/<company> - "Apply for this job" → form with name, email, phone, resume, links (GitHub, LinkedIn, portfolio)
- Resume: upload CV file
- Custom questions: answer from profile
- Submit → email confirmation
Ashby
- URL pattern:
jobs.ashbyhq.com/<company> - "Apply" → multi-step form (personal info, experience, resume, questions)
- Resume: upload CV file
- May require cover letter — use a brief, tailored version from profile summary
- Submit → confirmation
Workday
- URL pattern:
mywd.<company>.comor<company>.wd1.myworkdayjobs.com - Notoriously difficult to automate. Dynamic forms, anti-bot measures
- If automation fails after 3 attempts → mark company as
manual_apply_needed, notify user - Create account first, then search and apply
SmartRecruiters
- URL pattern:
careers.smartrecruiters.com/<company> - "Apply now" → form with personal info, resume, questions
- Resume: upload CV file
- May offer Google/LinkedIn prefill
- Submit → confirmation
Teamtailor
- URL pattern:
<company>.teamtailor.comor<company>.na.teamtailor.com - "Apply" → form with personal info, CV, cover letter (optional)
- Resume: upload CV file
- Submit → confirmation
Eightfold
- URL pattern:
<company>.eightfold.ai/careers - AI-powered matching. May suggest roles based on profile
- "Apply" → form, may offer LinkedIn import
- Resume: upload CV file
- Submit → confirmation
Custom / Unknown ATS
- Navigate to the careers page
- Look for "Apply" or "Postulate" or "Send CV" button
- If it redirects to LinkedIn → apply via LinkedIn flow instead
- If it's an email submission → draft email with CV attached, show to user (Gold Rule 6)
- If no apply button → mark as
no_application_systemin notes
Anti-ban
- Wait 3-5 seconds between actions (don't spam clicks)
- Don't apply to more than 5 jobs per company per session
- If a captcha or block appears → pause and notify user
- Vary navigation order when browsing job lists
- Take snapshots before interacting (LinkedIn-style tiptap editors are not the only ones with dynamic refs)
Resumability
The flow is fully resumable. The company_registrations table tracks state per company:
pending→ not yet visitedregistered→ account created, profile completedno_fit→ no matching roles (with reason in notes)manual_login_needed→ requires user interventionmanual_apply_needed→ Workday or similar that can't be automated
If the session is interrupted, the next run picks up where it left off by querying:
node scripts/db.js "SELECT * FROM company_registrations WHERE user_id = <user_id> AND registration_status = 'pending' ORDER BY region, company"DB access
All DB access via scripts/db.js (see db skill). Read-only by default, --write for inserts/updates.
company_registrations table
| Column | Type | Purpose |
id | SERIAL PK | |
user_id | INTEGER FK → users | Always 1 |
company | TEXT | Company name (unique per user) |
region | TEXT | latam or argentina |
sector | TEXT | Industry sector |
careers_url | TEXT | Direct URL to careers page |
ats_platform | TEXT | Detected ATS type |
registration_status | TEXT | pending, registered, no_fit, manual_login_needed, manual_apply_needed |
profile_completed | BOOLEAN | Whether profile was fully filled |
profile_url | TEXT | URL to user's profile on the platform (if available) |
login_method | TEXT | google, linkedin, email |
applied_jobs_count | INTEGER | How many jobs applied to via this flow |
last_visit_at | TIMESTAMPTZ | Last time the careers page was visited |
last_applied_at | TIMESTAMPTZ | Last time an application was submitted |
notes | TEXT | Free-form notes (ATS details, role observations, no_fit reasons) |
data | JSONB | Credentials (if email login), extra metadata |
created_at | TIMESTAMPTZ | |
updated_at | TIMESTAMPTZ |
Typical queries:
# Pending companies
node scripts/db.js "SELECT id, company, region, careers_url, ats_platform, notes FROM company_registrations WHERE user_id = <user_id> AND registration_status = 'pending' ORDER BY region, company"
# Registered but no applications yet
node scripts/db.js "SELECT id, company, careers_url, ats_platform FROM company_registrations WHERE user_id = <user_id> AND registration_status = 'registered' AND applied_jobs_count = 0 ORDER BY company"
# Update after registration
node scripts/db.js "UPDATE company_registrations SET registration_status = 'registered', profile_completed = true, ats_platform = '<ats>', login_method = '<method>', profile_url = '<url>', last_visit_at = NOW(), updated_at = NOW() WHERE id = <id>" --write
# Mark as no_fit
node scripts/db.js "UPDATE company_registrations SET registration_status = 'no_fit', notes = '<reason>', last_visit_at = NOW(), updated_at = NOW() WHERE id = <id>" --write
# Increment applied count
node scripts/db.js "UPDATE company_registrations SET applied_jobs_count = applied_jobs_count + <N>, last_applied_at = NOW(), updated_at = NOW() WHERE id = <id>" --writeRules
- Browser: always use
node .agents/skills/browser-automation/scripts/browser.jsfor open/close/goto. Neveragent-browser opendirectly - Resumable. Every action updates
company_registrations. If interrupted, next run continues from where it left off - Must-haves are non-negotiable. Don't register or apply to companies that don't match the user's
job_preferences(remote, location, AI focus, salary, industries_avoid) - Gold Rule 4. Manager is preferred but sacrificable for interesting IC roles with AI focus and good compensation
- Gold Rule 5. If manual login needed → open headed browser, notify user, wait
- Gold Rule 6. If applying via email (not ATS form) → show draft to user before sending
- Anti-ban. 3-5 second delays, max 5 applications per company per session
- Dedup. Check
applicationstable before applying. Don't apply to the same job twice - Persist everything. Registration status, profile completion, applications, credentials (in
dataJSONB) - CV and photo paths come from
users.data.cv_pathandusers.data.photo_path. Never hardcode paths - Single user (repo owner)
Dependencies
- Depends on
onboarding(DB, browser profile, Gmail + LinkedIn sessions) - Depends on
profile(Must-haves to filter, profile data to fill forms) - Consume by
daily(can be added as a third pillar alongsidenews+apply)
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.

