// 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
| name | Hone Administrator |
| description | 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 |
| tools | ["restart_hone"] |
Security note: This skill is available only to administrators listed in
config.yamlunderadmins. If an unauthorized user tries to trigger admin actions, politely refuse.
<PROJECT_ROOT>/ <- project root (current working directory)
├── config.yaml <- main config file (LLM, channels, admin list, and so on)
├── bins/hone-cli/ <- canonical CLI startup path (`hone-cli start --build`)
├── bins/
│ ├── hone-imessage/ <- iMessage channel entrypoint
│ ├── hone-discord/ <- Discord channel entrypoint
│ └── hone-telegram/ <- Telegram channel entrypoint
├── crates/
│ ├── hone-core/ <- core config and Agent interfaces
│ ├── hone-channels/ <- shared channel logic (`HoneBotCore`)
│ ├── hone-tools/ <- tool implementations, including `restart_hone`
│ ├── hone-llm/ <- LLM call layer
│ └── hone-memory/ <- session persistence
├── agents/
│ ├── gemini_cli/ <- Gemini CLI agent
│ ├── function_calling/ <- function-calling agent
│ └── codex_cli/ <- Codex CLI agent
├── skills/ <- built-in system skills (`.md` files)
│ └── hone_admin/SKILL.md <- this file
├── data/
│ ├── runtime/current.pid <- PID of the current `hone-cli start` supervisor
│ └── logs/restart.log <- restart log
└── Cargo.toml <- Rust workspace config
Use the gemini_cli agent (default):
Gemini CLI runs in --yolo mode and can read and write files directly. Tell the user what you are about to do, then operate on the target files.
Common edit cases:
config.yaml: adjust the LLM model, timeout, prompts, admin list, and so onskills/<name>/SKILL.md: update a skill's instructions or promptbins/, crates/): a rebuild is required before the change takes effectEdit flow:
config.yaml or skills/ changed, restart is still required because Hone loads them at startupWhen to use: after modifying Rust source or config so the change can take effect.
Restart tool: restart_hone(confirm="yes")
Flow:
restart_hone(confirm="yes")
success=true, tell the user:
Restart mechanism:
data/runtime/current.pid to get the current hone-cli start PIDdata/runtime/current.pidYou can use the following to check the current Hone state:
data/runtime/current.pid to see the process PIDdata/logs/restart.log to see recent restart logsdata/logs/hone.log to see the runtime logsconfig.yaml, Cargo.toml, or the data/ directoryrestart_hone; do not kill the process directlyRender 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.
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
为 honeclaw 仓库执行正式版本发布：补版本号、编写 `docs/releases/vX.Y.Z.md`、完成必要验证、提交变更、推送 `main`、创建并推送 `v*` tag。用户明确要求“发正式版本 / 打 tag / release / release note / 把上次 release 到现在的变更发出去”时使用；不适用于普通 push。