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

polish

Optimizes the user's LinkedIn profile and CV to align with their declared professional goals. Audits, redacts improvements, applies with per-section approval, and exports a polished CV to PDF.

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 polish

About this skill


name: polish description: Optimizes the user's LinkedIn profile and CV to align with their declared professional goals. Audits, redacts improvements, applies with per-section approval, and exports a polished CV to PDF. trigger: polish

Polish — LinkedIn profile + CV optimization

Trigger

Keyword: polish (or variants: "mejorar mi linkedin", "pulir perfil", "alinear cv", "optimizar perfil")

Purpose

Takes the user's captured profile (users.data.profile) and job preferences (users.data.job_preferences) and uses them to optimize the two artifacts that recruiters see: the LinkedIn profile and the CV. This is an output flow, not an input flow — profile captures data, polish applies it externally.

Dependencies

  • onboarding (DB, browser profile, LinkedIn session)
  • profile (requires users.data.profile and users.data.job_preferences with Must/Strong/Nice weights)

Parallel execution

polish can run alongside other flows (e.g: apply, news, targets) by using an attached session:

node scripts/browser.js attach --session polish-1
node scripts/browser.js goto <url> --session polish-1
node scripts/browser.js exec eval '<code>' --session polish-1
node scripts/generate-cv.js --session polish-1
node scripts/browser.js detach --session polish-1

All browser commands and generate-cv.js accept --session. Use detach when done (never close — it's ref-counted and would refuse or kill the browser for other agents). See AGENTS.md "Parallel execution".

Gate de validacion (pre-flight obligatorio)

Before executing any phase, verify that dependencies are satisfied. If any check fails, do not proceed — tell the user what is missing and how to resolve it:

# 1. Verify onboarding completed: DB exists and has user
node scripts/db.js "SELECT id, name, email, data FROM users WHERE id = <user_id>"
# If no row → "Necesitas ejecutar `onboarding` primero. No hay DB configurada."

# 2. Verify profile exists with minimum data
node scripts/db.js "SELECT data->'profile' AS profile, data->'job_preferences' AS prefs FROM users WHERE id = <user_id>"
# If profile is null/empty → "Necesitas ejecutar `profile` primero. No hay perfil capturado."
# If job_preferences is null/empty → "Necesitas completar el cuestionario de `profile`. No hay preferencias declaradas."

# 3. Verify minimum fields within profile
# Required for Phase 1 (LinkedIn): profile.title, profile.experience[], profile.skills[]
# Required for Phase 2 (CV): profile.full_name, profile.email, profile.experience[], profile.education[]
# If any required field missing → "Tu perfil esta incompleto. Falta: <fields>. Ejecuta `profile` para completarlo."

# 4. Verify LinkedIn session is active
node scripts/browser.js ensure
# If fails → "Necesitas iniciar sesion en LinkedIn. Ejecuta `onboarding` o abre el browser headed para login."

# 5. Verify linkedin_profile URL exists in DB
node scripts/db.js "SELECT data->'linkedin_profile' AS url FROM users WHERE id = <user_id>"
# If null → "No tengo tu URL de LinkedIn. Ejecuta `onboarding` para guardarla."

Only if all 5 checks pass, continue to Phase 1.

Phase 1 — LinkedIn profile optimization

1a. Audit (read-only)

  1. Load from DB: profile, job_preferences, linkedin_profile, style_profile, strategy (for strategy_level)
  2. Navigate to the user's LinkedIn profile: node scripts/browser.js goto <linkedin_profile_url>
  3. Take a snapshot to understand the current page structure: node scripts/browser.js exec snapshot
  4. Extract current state of each section using eval (adapt selectors to what you see in the snapshot):
    node scripts/browser.js exec eval '(function(){
      // Adapt selectors based on current LinkedIn DOM.
      // LinkedIn changes their UI frequently, so read the snapshot first
      // and adjust these selectors as needed.
      var headline = document.querySelector("h1")?.textContent?.trim() || "";
      var about = document.querySelector("#about ~ * .display-text, #about + * .inline-show-more-text")?.textContent?.trim() || "";
      // Experience: iterate over section entries
      var expNodes = document.querySelectorAll("#experience ~ * .pvs-entity, [data-view-name*='experience'] .pvs-entity");
      var experience = Array.from(expNodes).map(function(n) {
        return {
          title: n.querySelector(".t-14 .t-bold span")?.textContent?.trim() || "",
          company: n.querySelector(".t-14:not(.t-bold) span")?.textContent?.trim() || "",
          description: n.querySelector(".t-14.t-normal.t-black--light span")?.textContent?.trim() || ""
        };
      });
      // Skills
      var skillNodes = document.querySelectorAll("#skills ~ * .pvs-entity, [data-view-name*='skill'] .pvs-entity");
      var skills = Array.from(skillNodes).map(function(n) {
        return n.querySelector(".t-14 .t-bold span")?.textContent?.trim() || "";
      }).filter(Boolean);
      return JSON.stringify({ headline: headline, about: about, experience: experience, skills: skills });
    })()'
    
    • The eval code above is a starting point. Always take a snapshot first and adapt selectors to the current DOM. LinkedIn changes their class names frequently.
    • Extract: headline, about, experience (each role: title, company, period, description), education, skills (list + top 3 pinned), featured, open to work (if active, which roles), languages, certifications
  5. Save snapshot to DB: users.data.linkedin_snapshot
  6. Gap analysis: compare current state vs objectives:
    • Does headline reflect target role + AI focus?
    • Does About have a clear pitch aligned to job_preferences.role_types and ai_focus?
    • Does Experience have quantified achievements or just task descriptions?
    • Do Skills include those from job_preferences.stack and AI-related skills?
    • Is Open to Work active with the correct roles (if strategy is active/aggressive)?
  7. Present gap report to user with specific recommendations

1b

Read the complete source ↗