Skill Claude CodeCodex
Boot-time coordination protocol between multiple Scouts. Without this skill two scouts crawl the same circle (Remote EU) on the same tier (LinkedIn) and produce 100% duplicates that the dedup gate then has to drop — wasted budget and slower team. Use it as the FIRST action in your loop, before anything else. Owned by…
Skill Claude CodeCodex
Strato web-access cross-provider per gli Scout (F-2). 5 componenti coordinati — anti-bot robust scrape, LinkedIn session + search, email IMAP poll, multi-Scout workspace claim, freshness focus. Usato come stack base per ogni sweep: lo Scout sceglie il livello di accesso più leggero che funziona, e sale solo quando…
Skill Claude CodeCodex
Translate every [SENTINELLA] ... order received in the Captain's tmux into the correct action (throttle level, spawn/kill, freeze, soft-pause, resume). The Sentinel is the team's heartbeat — its orders are commands, not suggestions. Default behavior is to execute without re-checking; second-guessing the Sentinel by…
Skill Claude CodeCodex
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 +…
Skill Claude CodeCodex
Spawn a JHT team agent (Scout, Analista, Scorer, Scrittore, Critico, Assistente, Capitano-2) via the launcher, then deliver the kick-off message that actually starts its main loop. Captain-only — the Captain is the single owner of team scaling. ALWAYS use this skill: bypassing start-agent.sh with tmux new-session +…
Skill Claude CodeCodex
Spawn a fresh DOTTORE on-demand when you (Capitano/Assistente/Sentinella/Mentor) need an immediate health-check round. Use this INSTEAD of writing to the DOTTORE session when the user asks "fai partire il dottore" / "dottora" / "controlla il team", because between scheduled rounds the DOTTORE session is bash residua…
Skill Claude CodeCodex
The team-mode manual — one card per mode (search / harvest / care / calibration / saving). Open it whenever the hourly [MODALITÀ CORRENTE] banner names a mode and you do not remember what it implies operationally, at wake after a context refresh, or when the user switches mode from the game. The mode is ALWAYS the…
Skill Claude CodeCodex
Send a message to the user via Telegram (outbound). Use this on the Telegram bridge — the user is on their phone, NOT in front of the web dashboard. Wrapper jht-telegram-send resolves bot token + chatid per-agent from config (--from assistente|capitano|mentor); never call the Bot API directly.
Skill Claude CodeCodex
Sign your wake-up. ALWAYS the FIRST command of every wake-up, before anything else, whenever you receive a [RIPRENDI] message after a throttle pause. throttle-ack flips your flag from NOTIFIED to ACTIVE. Only you can do it - the engine cannot - which is exactly why a flag left on NOTIFIED is proof that an agent got…
Skill Claude CodeCodex
Decide WHO slows down and BY HOW MUCH when the team's consumption has to change. Open it when a [PACE-GUARD] advisory lands in your pane, when the Sentinella orders a Throttle: N level, or when your own check says the window is off pace. Every one of those signals is a single team-level number; the actuator is…
Skill Claude CodeCodex
The ONLY way the team's rhythms get written. Captain-only. throttle-set edits the per-agent throttle config; the engine re-reads it when it arms each timer, so the change bites on that agent's NEXT cycle by itself - no tmux message, no agent has to re-read anything, and the cycle already running is not disturbed. Use…
Skill Claude CodeCodex
Register your pause and END YOUR TURN. Time is no longer yours to keep - an engine outside your process owns the timer and wakes you over tmux when it expires. ALWAYS use this instead of sleep when you want to slow your iteration rate. One call, throttle , returns immediately; you never learn how long you wait and you…