assess

Assess a Job Posting

Shell setup: Always export JFM_DIR='<workspace path>' (single quotes) before running tracker commands. The script refuses to operate if it can't resolve a real workspace.

Read ../search/references/routing.md before processing any user message — it defines how to decompose compound messages and where to route each type of input.

Assess a specific job posting against the user's profile.

Steps

1. Read profile.yaml, archetypes.yaml, and filters.yaml

2. Fetch the URL provided by the user using WebFetch. Use Haiku for simple JD extraction from URLs if delegating to a sub-agent.

3. Extract the job description from the page

4. Run a full fit assessment using the search skill's fit assessment framework

5. Present the assessment to the user (Recommendation, Gaps, Positive Fit)

6. Ask if they want to add it to the tracker — or decline it immediately

7. If adding, add via the tracker script:

   node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js add --json '{"company":"...","role":"...","url":"...","archetype":"...","stage":"suggested","agent_summary":"..."}'
   

8. Get the file paths for the new entry and save the JD:

   Always save the JD locally — Greenhouse / Lever / Ashby postings are removed once roles close, and the user needs the JD for cover letters, prep, and a record of what they applied for. Save the JD even when declining: declined JDs feed the decline-pattern learning loop.

   node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js paths --id <id>
   

   This returns role_dir and company_dir. Save the JD to {role_dir}/jd.md. Create the directories if they don't exist (mkdir -p).

   After saving, use present_files to share the board with the user, then tell them what was created:

   Added to tracker — {Company} / {Role} JD saved — {role_dir}/jd.md Your board has been updated — refresh to see it.

9. If declining (user says "not interested", "pass", "decline", etc.):

   • If already added to tracker, decline it:

     node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js decline --id <id> --reason "reason text"
     

   • If not yet added, add it as declined so the reason is tracked:

     node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js add --json '{"company":"...","role":"...","url":"...","stage":"declined","decision":{"proceed":"no","reason":"reason text"}}'
     

   • Always run decline pattern learning (see ../search/references/decline-learning.md): check if this decline suggests a new pattern or refines an existing one. If so:

     node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js add-decline-pattern --pattern "Pattern description" --learned-from "Company Name"
     

     Tell the user what filter change was made (if any). Use present_files to share Kanban/index.html, then tell the user: "Your board has been updated."