菜单
Use when adding, migrating, reviewing, or debugging alerts and reports in this repository, especially when a producer should move onto the shared reporting-hub pipeline, use the standardized payload schema, or align with reporting health and briefing flows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | reporting-hub-maintainer |
| description | Use when adding, migrating, reviewing, or debugging alerts and reports in this repository, especially when a producer should move onto the shared reporting-hub pipeline, use the standardized payload schema, or align with reporting health and briefing flows. |
이 스킬은 이 저장소에서 알림, 리포트, 브리핑 스니펫, mainbot_queue payload, alert publisher, reporting-hub fanout을 다룰 때 사용한다.
packages/core/lib/reporting-hub.jspackages/core/REPORTING_HUB_PLAN.mdpackages/core/REPORTING_INVENTORY.mdbots/orchestrator/scripts/reporting-health.jsbots/orchestrator/lib/night-handler.js팀별 producer를 만질 때는 관련 파일을 추가로 확인한다.
bots/claude/lib/reporter.js, bots/claude/lib/alert-publisher.tsbots/investment/team/reporter.js, bots/investment/shared/alert-publisher.ts, bots/investment/shared/report.jsbots/reservation/lib/alert-client.ts, bots/reservation/lib/telegram.tsbots/blog/scripts/health-check.jsreporting-hub를 우선 사용한다.titlesummarydetailsactionlinksreporting-hub.js의 기존 helper로 흡수 가능한지 본다.buildNoticeEvent, report 성격이면 buildReportEvent, 브리핑이면 snippet 계열을 우선 검토한다.payload.title, payload.summary, payload.details를 실제로 읽는지 확인한다.REPORTING_INVENTORY.md를 갱신한다.bots/orchestrator/scripts/reporting-health.js와 /reporting-health 경로에서 바로 보여야 한다./reporting-health/reporting-health summary/reporting-health producers/orchestrator-healthdetails[]에 넣고, 액션은 action 또는 links로 분리한다.NaN, undefined가 노출되지 않게 formatter 단계에서 막는다.node --check <file>node bots/orchestrator/scripts/reporting-health.jsnode bots/orchestrator/scripts/reporting-health.js --summarynode bots/orchestrator/scripts/reporting-health.js --producersbots/orchestrator/lib/batch-formatter.jsbots/orchestrator/src/filter.jsBlog writing operations: concrete drafts, diagnosis, comment strategy, external sources, and recurring gotchas.
사용자 요청을 Blog, Luna, Darwin, Sigma, Ska, Hub/Orchestrator 등 적절한 팀과 런타임으로 라우팅할 때 사용.
Use for non-trivial production code changes that require expert challenge and consensus, test-first implementation, soft and read-only hard verification, runtime and DB consistency checks, refactoring discipline, and an independent code-review gate.
Use when diagnosing or improving Luna investment-team autonomous operation bottlenecks, especially the 30-minute Codex automation loop, live-fire watchdog issues, LLM hot-path overuse, discovery funnel stalls, marketdata connectivity, reconcile blockers, or safe fix planning.
Hub routing, resilience, alarm lifecycle, and Sigma feedback operations.
Darwin research cycle operations: cycle overview, predicate authoring, adopt review, and recurring gotchas.