Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

targets

Active direct sourcing. Registers and creates standout profiles on the 40 target companies' career sites, then applies to matching positions.

galiprandi · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add galiprandi/job-seeker --skill targets

About this skill


name: targets description: Active direct sourcing. Registers and creates standout profiles on the 40 target companies' career sites, then applies to matching positions. trigger: targets

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 scripts/browser.js for open/close/goto. See AGENTS.md "Browser session" and "Parallel execution" for details. Never call playwright-cli open directly
  • Parallel execution: if running alongside other flows (e.g: apply or news), attach a session with node scripts/browser.js attach --session targets-1 and pass --session targets-1 to all browser commands and scripts. Use detach when done (never close — it's ref-counted)
  • Load active preferences (see memory skill):
    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"):
    node scripts/db.js "SELECT data->'strategy' AS strategy FROM users WHERE id = <user_id>"
    
    Respect: targets_batch_size (max companies per session, 0 = don't run, "all" = no limit), match_threshold, relax_must_haves. If targets is not in sources_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. If relax_must_haves resolves to include work_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_avoid list (per industries_avoid.weight)
  • Salary below job_preferences.salary.value.min (if mentioned and salary.weight = Must)
  • Not in user's accepted locations (per location and timezones preferences)

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):

  1. Navigate to careers URL using node scripts/browser.js goto <url> (or open if no session)
  2. 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)
  3. Find the registration / sign up / create account page
  4. 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.data as {email, password})
    • If no account creation possible → mark registration_status = 'manual_login_needed', notify user (Gold Rule 5)
  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: " | ")
    • Summary/bio: use profile.summary, adapted to the platform's character limit
    • Location: from users.data.personal_info (city, country) or form_answers.location
    • Upload CV: use profile.cv_path or personal_info.cv_pdf_path (from DB, never hardcoded)
    • Upload photo: use users.data.photo_path if the platform accepts it
    • Skills: add all from profile.skills
    • Experience: fill from profile.experience if the platform has structured fields
    • Lan
Read the complete source ↗