メニュー
Convert UTC timestamps to the user's timezone before showing them in chat, charts, Telegram, or any user-facing output. Use this helper whenever you would otherwise write a raw `strftime("%H:%M")` of a UTC datetime in something the user reads.
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 | format-time |
| description | Convert UTC timestamps to the user's timezone before showing them in chat, charts, Telegram, or any user-facing output. Use this helper whenever you would otherwise write a raw `strftime("%H:%M")` of a UTC datetime in something the user reads. |
| allowed-tools | Bash(python3 *) |
Bug #15: the container runs in UTC, the user lives in CEST/CET. Without
conversion every "reset at 03:11" in chat or charts forces the user to
do +2 in their head — and sometimes the user says "qui sono le
3:21" and the Capitano has to scramble for the conversion.
Apply it whenever you produce a timestamp the user will read:
Skip when:
messages.jsonl, sentinel-data.jsonl,
dottore-actions.jsonl) — they stay UTC ISO for cross-agent parsing.from shared.skills.format_time import fmt_user, fmt_user_with_utc
from datetime import datetime, timezone
now = datetime.now(timezone.utc)
print(fmt_user(now)) # "03:21 CEST"
print(fmt_user_with_utc(now)) # "03:21 CEST (01:21 UTC)"
Or, from bash:
python3 /app/shared/skills/format_time.py --now
python3 /app/shared/skills/format_time.py --iso 2026-05-17T01:14:00Z --with-utc
In operational charts that an oncall engineer (or you, debugging)
might read alongside the team's UTC logs, prefer fmt_user_with_utc
so both are visible:
"Now 03:21 CEST (01:21 UTC) — usage 63% — proj 92.2%"
In plain Telegram chat to the user, fmt_user alone is usually
enough:
"📅 Reset finestra 5h alle 05:11 CEST (~1h 50m)."
candidate_profile.yml::timezone (IANA name, e.g. Europe/Rome).
Default Europe/Rome if missing — covers ~95% of beta users. To
override per session: JHT_USER_TZ env var (read by the helper).
datetime.now().strftime("%H:%M") in a user-facing string —
produces the container time (UTC) without suffix → user
confusion.+2 math anywhere. Use the helper; DST flips
Europe/Rome to CET (+1) at the end of October and you will forget."CEST" as suffix — wrong for half the year and
wrong for non-Italian users.shared/skills/format_time.py — implementation.docs/examples/candidate_profile.yml.example — timezone: field docs.