Render research-style PNG charts for trends, comparisons, distributions, and scatter relationships when a visual materially improves the answer
Use in the honeclaw repository when Codex needs to validate event-engine notification quality changes, run the event-engine/core/web-api regression subset, rerun the saved news classifier baseline against OpenRouter models, or add new real-news samples to the baseline fixture without overfitting.
Admin-only skill for viewing or modifying Hone source code and configuration, and for performing restarts. Available only to users listed in config.yaml admins
Use in the honeclaw repository when Codex needs to review event-engine push quality for one or more actors: what each user/channel received, whether push timing and digest grouping were reasonable, whether messages were duplicated or useless, and whether useful events were filtered, omitted, capped, cooled down, or left undelivered.
维护长期公司画像、投资主线 与事件时间线；当用户想建立公司档案、在财报/公告后更新长期判断，或希望保留结论、为什么成立、关键证据与研究路径时使用
Analyze gold, gold-linked ETFs, and gold miners through macro drivers, positioning, and event risk
| name | Notification Preferences |
| description | 管理当前用户的市场事件推送偏好,把中文自然语言映射到 notification_prefs 工具 |
| when_to_use | 当用户想调整"要收什么 / 不要收什么"类的推送开关时(静音、只看重要、不要新闻、只要财报等) |
| user-invocable | true |
| context | inline |
| allowed-tools | ["notification_prefs"] |
管理当前 actor(也只能是当前 actor——工具在构造时已绑定身份)对市场事件推送的个人偏好。
allow_kinds / block_kinds 的值必须从以下里选,其它值会被工具直接拒绝:
earnings_upcoming, earnings_released, earnings_call_transcript,
news_critical,
price_alert, weekly52_high, weekly52_low,
dividend, split,
sec_filing, analyst_grade,
macro_event, social_post
| 用户说法 | 调用 |
|---|---|
| "先别推了" / "静音" | notification_prefs(action="disable") |
| "恢复推送" / "开回来" | notification_prefs(action="enable") |
| "只看重要的" | notification_prefs(action="set_min_severity", value="high") |
| "一般的也推吧" | notification_prefs(action="set_min_severity", value="medium") |
| "只推我持仓相关的" | notification_prefs(action="set_portfolio_only", value=true) |
| "什么都推" | notification_prefs(action="set_portfolio_only", value=false) |
| "不要新闻 / 不要分析师评级" | notification_prefs(action="block_kinds", value=["news_critical","analyst_grade"]) |
| "只要财报和 SEC" | notification_prefs(action="allow_kinds", value=["earnings_released","earnings_upcoming","sec_filing"]) |
| "别再限制 kind 了" | notification_prefs(action="clear_allow") 或 clear_block |
| "看看现在是什么设置" | notification_prefs(action="get") |
| "全部恢复默认" | notification_prefs(action="reset") |
get / reset 的改动,先调一次 get 看当前状态,避免误覆盖。set_min_severity 再 block_kinds)。prefs 字段给用户复述生效后的设置,确认是否还有需要调整的。allow_kinds 的数组里需要包含 earnings_upcoming 和 earnings_released——两者是不同的 kind,只填一个会漏。block_kinds 优先级高于 allow_kinds。如果用户之前设过白名单,之后 block 一个重叠的 kind 也会生效。config.yaml 里把某个 kind 关了——那类事件无论如何都不会推给任何人,即使用户把它放进 allow_kinds。这条解释给用户,不要误以为是工具问题。