메뉴
Deliver a message to another agent's tmux session atomically. ALWAYS use this to communicate with SCOUT/ANALISTA/SCORER/SCRITTORE/CRITICO/SENTINELLA/CAPITANO. NEVER call `tmux send-keys` by hand — Ink-based TUIs (Codex, Kimi) lose the Enter character.
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 | tmux-send |
| description | Deliver a message to another agent's tmux session atomically. ALWAYS use this to communicate with SCOUT/ANALISTA/SCORER/SCRITTORE/CRITICO/SENTINELLA/CAPITANO. NEVER call `tmux send-keys` by hand — Ink-based TUIs (Codex, Kimi) lose the Enter character. |
| allowed-tools | Bash(jht-tmux-send *) |
Shell wrapper colocated at /app/agents/_skills/tmux-send/jht-tmux-send (also on PATH via /usr/local/bin symlink, populated at image build).
Ink-based TUIs (Codex, Kimi Code) drop the Enter if it arrives in the same tmux send-keys call as the text body. Text is sent character-by-character; Ink must finish rendering before accepting another keystroke. If you call tmux send-keys "msg" Enter, the message stays in the peer's input buffer without being submitted → silent inter-agent deadlock.
The wrapper handles it atomically: text → sleep 0.3 → Enter → sleep 0.5 → Enter (the second Enter is idempotent for robustness).
jht-tmux-send <SESSION> "<message>"
# Captain → Scout (INFO, generic operational message)
jht-tmux-send SCOUT-1 "[@capitano -> @scout-1] [INFO] Start the main loop. Begin from CIRCLE 1 (Remote EU); ping after each batch of 3-5 positions."
# Captain → Writer (URG, real-time order)
jht-tmux-send SCRITTORE-1 "[@capitano -> @scrittore-1] [URG] FREEZE — finish the current Critic round, then sleep until throttle returns to T0/T1."
# Analyst → Scout (FEEDBACK, rejection-pattern coaching)
jht-tmux-send SCOUT-2 "[@analista-1 -> @scout-2] [FEEDBACK] [SENIORITY] 4 of last 5 inserts from greenhouse.io require senior+ — switch source or query for the next batch."
# Sentinel → Captain (URG, state change)
jht-tmux-send CAPITANO "[@sentinella -> @capitano] [URG] Usage 94%, projection 102% — recommend throttle T2 + freeze Writers."
# Writer → Captain (REPORT, final result)
jht-tmux-send CAPITANO "[@scrittore-1 -> @capitano] [REPORT] Position 42 — verdict PASS, score 7.5/10. PDF: /jht_user/.../CV.pdf"
# Worker → Captain (ACK, confirming URG)
jht-tmux-send CAPITANO "[@scrittore-1 -> @capitano] [ACK] freeze applied, sleeping."
Always keep the structured prefix:
[@<from> -> @<to>] [<TYPE>] <text>
Standard types (see agents/_manual/communication-rules.md for full taxonomy and per-role expectations):
INFO — status update / generic operational message (no reply expected)URG — real-time order requiring immediate action (FREEZE, throttle, kill)FEEDBACK — coaching upstream with a rejection tag ([SENIORITY] · [STACK] · [GEO] · [LINGUA])REQ / RES — synchronous request/response between agentsACK — acknowledge an URG or REQ you can't service yetREPORT — final outcome of a unit of work💬
[CHAT]is reserved for user → agent messages from the web UI (see Captain's prompt protocol). Don't use it for inter-agent traffic.
A tmux message is a push: it burns the peer's turn. Send one ONLY if it passes the bar:
[FEEDBACK] shaping the next query; Captain → worker spawn / throttle / kill; Writer ↔ Critic CV loop.Everything else is pull: DB (Tier 1) → capture-pane (Tier 2) → message (Tier 3). What is CUT:
recent-activity.tmux capture-pane, never burn a peer's turn.Pipeline hand-offs (Scout→Analyst→Scorer→Writer) are status flips, not messages. Full rules: agents/_manual/communication-rules.md.
0 — message delivered1 — missing arguments2 — target session does not exist (check the name with tmux ls)tmux send-keys directly to communicate with another agent. Always go through jht-tmux-send.tmux ls shows the target session doesn't exist, do not create it — ask the Captain (or use start-agent.sh if you are the Captain).agents/_manual/communication-rules.md.