القائمة
Estrae deadline dal JD (helper deadline_extract) e produce alert utente quando una candidatura READY sta per scadere (helper expiration_alerts, idempotente). F-4 task
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Extract the company logo for a company in the companies table and store it as a small base64 data-URI (max ~35KB, min 32px). Primary path is fully automated via logo_fetch.py against the official website (apple-touch-icon → icon → og:image → favicon); when the site blocks bots or has no usable icon, find a direct logo image URL via web search and pass it with --from-url. Verify the website really belongs to the company BEFORE fetching. Sets companies.logo, logo_source, logo_fetched.
Lo sweep di manutenzione INFRA del Mantenitore 👷♂️ (gemello del Dottore, scope infrastruttura non agenti). Una passata giornaliera one-shot: canary di liveness dei processi salva-vita del container (bridge/daemon/watchdog) via process_health.py, smoke-test dei tool mission-critical (browser/LinkedIn) via tool_health.py, audit/consolidamento deps fuori standard, GC di script e tmp orfani, de-dup di script ricorrenti, freschezza deps, trend disco/RAM. Single-writer: il Mantenitore è l'UNICO che ripara l'infra; le azioni DISTRUTTIVE (delete/archive) le PROPONE, il Capitano decide. Esito in append su mantenitore-logbook.jsonl.
Doctor-only. Context-refresh round: for each agent session read its real context occupancy (provider client-side command, zero tokens) and refresh ONLY sessions whose context window is >50% full — do a retrospective (capture + interview + analytics), append a dense synthesis to the growing daily journal, then KILL + recreate + resume the session with continuation context, so its context window is cleared without losing where it was. Runs 2× per work window (at +30min and at mid). Skips fresh, low-context (≤50%), and Capitano-parked sessions.
Run the mandatory 3-round CV review loop with the Critico — autonomously, without going through the Capitano. For each round you spawn a FRESH `CRITICO-S<N>` session (same N as your Scrittore session: SCRITTORE-2 → CRITICO-S2), send PDF + JD, wait for the structured verdict, kill the Critic, correct the CV, regenerate the PDF, and start the next round with another fresh instance. Three rounds are non-negotiable — neither 1 nor 2. After the 3rd round, gate: `critic_score ≥ 5` → `ready`, else `excluded`. Owned by the Scrittore.
DB + filesystem contract every Scrittore follows when taking a position from `scored` (≥50) to `ready`/`excluded`. Three gates BEFORE writing a single line of CV (anti-rewriting, anti-collision, link verification), one canonical path for deliverables, one final gate after the 3rd Critic round. Skipping any of these produces duplicate work, overwrites another Writer's claim, or — worst — pushes an `excluded`-grade CV to the user as `ready`. Owned by the Scrittore.
Insert NEW records into the JHT DB (positions / scores / applications / companies / position_highlights). Use it ONLY when an agent needs to create a record — Scout for positions, Analyst for companies and highlights, Scorer for scores, Writer for applications. Never blind-overwrite — for updates use `db-update`.
| name | expiration-tracking |
| description | Estrae deadline dal JD (helper deadline_extract) e produce alert utente quando una candidatura READY sta per scadere (helper expiration_alerts, idempotente). F-4 task |
| allowed-tools | Bash(python3 /app/shared/skills/deadline_extract.py *), Bash(python3 /app/shared/skills/expiration_alerts.py *), Bash(jht-telegram-send *) |
Bug latente F-4: utente accumula 50 CV ready, dimentica di applicare
per 2 giorni, top opportunità (es. Sisal PASS 7.5) scade in silenzio.
La pipeline è user-curated apply (bug #9 declassato) → senza alert
proattivo, lo zelo del team ad addestrare top CV viene vanificato dal
silenzio dell'utente.
Quando inserisci una nuova position (Scout) o quando arricchisci la JD
(Analista), passa il testo per deadline_extract:
# Direct CLI: estrae da stdin o --jd
echo "$JD_TEXT" | python3 /app/shared/skills/deadline_extract.py
# → 2026-06-15 (ISO date) o stringa vuota
# Inline nel db_insert.py position
deadline_iso=$(echo "$JD_TEXT" | python3 /app/shared/skills/deadline_extract.py)
if [ -n "$deadline_iso" ]; then
python3 /app/shared/skills/db_insert.py position \
--title "$TITLE" --company "$COMPANY" --url "$URL" \
--jd-text "$JD_TEXT" \
--deadline "$deadline_iso" # ← nuovo, F-4
fi
Il parser è conservativo (solo ISO, dd/mm/yyyy EU, Month dd[, yyyy] EN/IT, "expires in N days"). Se non trova un match ad alta confidenza restituisce stringa vuota → meglio NULL nel DB che data inventata.
Trigger consigliato: dopo ogni [BRIDGE TICK] (Capitano) o end-of-pass
del Mentor. Idempotenza fa sì che chiamate frequenti producano alert
solo per NUOVE coppie (app_id, deadline_iso).
alerts=$(python3 /app/shared/skills/expiration_alerts.py)
if [ -n "$alerts" ]; then
# Manda all'utente via Telegram
echo "$alerts" | jht-telegram-send --from capitano --keyboard capitano
fi
Output 1 riga per application a rischio:
⏳ [ALERT scadenza] Sisal Data Analyst (PASS 7.5) — scade 2026-05-18 (DOMANI). Spedisci candidatura o perdi l'opportunità.
Lo state idempotency è in $JHT_HOME/state/expiration_alerts_sent.json
(set di (app_id, deadline_iso) già notificati). Per re-spedire un
alert già mandato: expiration_alerts.py --reset (dev-only).
Estensione futura della skill liveness-check: ogni 6h, refetch URL
delle positions in status IN ('scored', 'ready') con last_checked < NOW() - 12h. Se l'URL ritorna 404 / "no longer accepting" → flip a
status='expired' + nota. Out of scope per F-4 iniziale; il bottom-up
dei deadline catturati dal JD copre la maggior parte dei casi.
NULL che +30d arbitrario.shared/skills/deadline_extract.py — parsershared/skills/expiration_alerts.py — emitter + idempotency stateagents/_skills/db-update/SKILL.md § Positions — --deadline flag