メニュー
State variables the Sentinel must keep across ticks (last order sent, freeze flag, FATAL streak, per-state counters, emergency history, cooldowns). Use this skill on every tick to update memory and decide if a new order is required (edge-triggered).
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 | memory-state |
| description | State variables the Sentinel must keep across ticks (last order sent, freeze flag, FATAL streak, per-state counters, emergency history, cooldowns). Use this skill on every tick to update memory and decide if a new order is required (edge-triggered). |
Mantieni queste variabili nella tua memoria conversazionale. Le usi per decidere se notificare il Capitano (edge-triggered).
last_ordine = {
tipo: "ACCELERA | RALLENTARE | EMERGENZA | RIENTRO | RESET |
MANTIENI | SCALA_UP | PUSH_GSPOT | RECOVERY | STAGNAZIONE |
PEGGIORAMENTO | None",
throttle: 0..4,
usage: int,
proj: float,
ts: "HH:MM:SS",
}
freeze_active = bool # True dopo freeze_team.py
fatal_streak = int # 0/1/2: cicli FATAL consecutivi
tick_steady_count = int # tick consecutivi proj 90-95%
# (per MANTIENI dopo 3)
tick_below_gspot_count = int # tick consecutivi proj 70-90%
# (per PUSH G-SPOT dopo 2)
tick_sotto_count = int # tick consecutivi proj<70 + vel<ideale×0.7
# (per SCALA UP dopo 2)
emergency_proj_history = list # ultimi 5 proj durante zona >100%
# (per RECOVERY TRACKING / STAGNAZIONE)
emergency_proj_min = float # minima proj raggiunta nell'episodio
# (per PEGGIORAMENTO POST-FREEZE)
push_gspot_cooldown = int # cooldown PUSH G-SPOT (0/1/2/3 tick)
scala_up_cooldown = int # cooldown SCALA UP (0/1/2 tick)
recovery_tracking_cooldown = int # cooldown RECOVERY TRACKING (0/1/2/3)
# Pseudocode da eseguire ad ogni [BRIDGE TICK]:
# 1. Cooldown decrement
push_gspot_cooldown = max(0, push_gspot_cooldown - 1)
scala_up_cooldown = max(0, scala_up_cooldown - 1)
recovery_tracking_cooldown = max(0, recovery_tracking_cooldown - 1)
# 2. Counter stato
if status == "STEADY": tick_steady_count += 1
else: tick_steady_count = 0
if 70 <= proj < 90: tick_below_gspot_count += 1
else: tick_below_gspot_count = 0
if proj < 70 and vel < ideale * 0.7:
tick_sotto_count += 1
else: tick_sotto_count = 0
# 3. Memoria emergenza (zona proj > 100%)
if proj > 100:
emergency_proj_history.append(proj)
emergency_proj_history = emergency_proj_history[-5:]
emergency_proj_min = min(emergency_proj_min or float('inf'), proj)
else:
# Uscita zona emergenza: reset
emergency_proj_history = []
emergency_proj_min = None
# 4. Reset event
if last_sample.usage - usage > 30:
reset_session() # azzera storico, manda RESET SESSIONE
last_ordineAggiorna solo dopo aver inviato un ordine al Capitano:
last_ordine = {
tipo: "<tipo dell'ordine inviato>",
throttle: <throttle del messaggio>,
usage: <usage al momento>,
proj: <proj al momento>,
ts: "<HH:MM:SS>",
}
Se decidi SILENZIO (no notifica), last_ordine resta invariato.
Se usage cala di > 30 punti rispetto al sample precedente:
last_ordine = None
freeze_active = False
tick_steady_count = 0
tick_below_gspot_count = 0
tick_sotto_count = 0
emergency_proj_history = []
emergency_proj_min = None
*_cooldown = 0
fatal_streak = 0
Poi manda ORDINE: RESET SESSIONE al Capitano (vedi skill order-formats).