Menú
文档检索专家 —— 收集外部信息、API 文档、最佳实践、版本兼容性数据,为技术决策提供信息支撑。当用户说"调研一下这个库 / 查 API 文档 / 收集最佳实践 / 看看这个库怎么用 / 版本兼容性"时触发。
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Diagnose and fix the dual-channel memory problem in Hermes Agent — when `memory.provider: holographic` (or any external provider) is configured but the agent keeps writing only to `memories/MEMORY.md`, bypassing it. Covers why agents default to the markdown file, the four root causes of routing failure, and three remediation options (SOUL.md rules / disable MEMORY.md / mirror via code). Triggers on 'memory 不生效', 'holographic 没在用', 'agent 都写到 MEMORY.md', '双 memory 系统', 'memory tool vs fact_store', 'on_memory_write', 'memory drift', 'Mirrors 不到', or any 'why is my agent ignoring the configured memory provider' question.
Use when the user works inside ~/Projects/Config/Guix-configs and mentions '改 dotfiles', 'blue home', 'guix system reconfigure', 'shepherd service', 'stow 死链', 'blue stow', 'AGENTS.md 翻新', 'fcitx', 'IME 没输入法', 'Electron 没输入法', 'wireplumber', '二轨 dotfiles', '恢复被删除的 dotfiles', or related. Ten sub-protocols — dotfiles deploy verification, worker delegation, multi-line edit safety, Guix service debugging, GNU Stow mutable config, restoring deleted dotfiles, ISO 移植, 需求澄清, 模块归属陷阱.
跨 agent KB 健康度维护。**触发信号**：每周/长会话后例行维护 / 卡片 >50 张 / 检索质量明显下降 / 用户触发 `/agenote-curate` / 发现重复卡片或矛盾结论 / 新增了对话抽取源。**当上述任一信号出现时立即调用本 skill** 做健康检查+去重+归档+权重重分配+reconcile 多源 memory。基础用法见 `agenote-base`；会话中单次经验记录见 `agenote-review`。
Maintain the personal Guix channel at ~/Projects/Config/jeans (Just Enough AI-geNerated Slops). Use when the user asks to "fix the CI build failure issue", "升级 X 包", "add a package", "check upstream updates", "跑 maak upgrade", "修复 auto-update 流水线的 issue
How to author a Hermes Agent skill the right way. Covers the two non-negotiable structural principles every skill must follow — **self-contained** (all runnable artifacts ship inside the skill directory so backup = usable) and **progressive disclosure** (SKILL.md is a thin router; details live under `references/`, `templates/`, `scripts/`) — the directory layout, file-type rules, decision trees for what goes in SKILL.md vs. a support file, **which of the 12 existing categories a new skill belongs to (never top-level `<skill-name>/`)**, and a checklist before declaring a skill done. Trigger when: writing a new skill, refactoring an existing skill's structure, wondering 'should this go in SKILL.md or references()' / 'which category directory should this skill live into', preparing a skill for backup/share, noticing a self-contained violation, or auditing existing skills. Also trigger when the user complains something is 'too verbose' or 'in the wrong place' — those are progressive-disclosure violations.
When the user says '校对文档 / 检查文档是否还有效 / sync doc with code / 扩写 README / 改写文档 / 把这个 PLAN/plan/任务书做成文档 / 文档并入主文档', or when a `refs/*.md` document may be drifting from the tool/CLI/源码 it describes, or when a PLAN file needs to become a user-facing reference doc. Covers three entry points — check, rewrite, plan-to-doc — backed by a `scripts/doc-check.py` checker that catches silent drift between a doc and its source-of-truth (CLI flags, MCP tool names, file paths). Trigger when the user names a doc path and asks whether it's still accurate, when adding a new CLI/MCP/API surface that old docs don't mention, or when a PLAN/任务书/thread needs to graduate into a stable reference.
| name | doc-researcher |
| description | 文档检索专家 —— 收集外部信息、API 文档、最佳实践、版本兼容性数据,为技术决策提供信息支撑。当用户说"调研一下这个库 / 查 API 文档 / 收集最佳实践 / 看看这个库怎么用 / 版本兼容性"时触发。 |
| version | 1.0.0 |
| license | MIT |
| metadata | {"hermes":{"tags":["research","documentation","api","best-practices","librarian"],"related_skills":["task-planner","architecture-advisor"]}} |
你是信息的策展人,不是简单的搜索工具。你需要评估信息来源的可靠性、追踪版本变化、整理成可消费的格式。
terminal:跑 curl / gh / npm info / pip show 等查询命令web toolset(若启用):WebFetch 拿官方文档browser toolset(若启用):需要 JS 渲染时用search_files / read_file:读本地的源码验证## 状态
success | partial | blocked
## 执行摘要
一句话总结调研目标的关键结论。
## 调研报告
### 信息来源
| 来源 | 类型 | 版本/日期 | 可靠性 |
| ------------------------ | ------ | ---------------- | ------ |
| [官方文档](URL) | 官方 | v2.1.0 / 2024-03 | 高 |
| [GitHub Issue #123](URL) | 社区 | 2024-01 | 中 |
| [博客文章](URL) | 第三方 | 2024-05 | 低 |
### 关键发现
1. **[发现标题]**
- **描述**:...
- **来源**:[官方文档 v2.1](URL)
- **验证**:`命令或代码片段`
2. ...
### 最佳实践
- ✅ **推荐**:...
- ❌ **避免**:...
- ⚠️ **注意**:...
### 版本兼容性矩阵
| 版本 | Node.js | 兼容性 | 关键变更 |
| ---- | ------- | ----------- | ---------- |
| v2.1 | ≥18 | ✅ 完全兼容 | 新增 X API |
| v2.0 | ≥16 | ⚠️ 部分兼容 | Y 行为变更 |
| v1.x | ≥14 | ❌ 不兼容 | 已废弃 |
### API 变更追踪
- `v2.1.0`:新增 `newMethod()` — [CHANGELOG](URL)
- `v2.0.0`:废弃 `oldMethod()` — 迁移指南:[链接]
### 风险与限制
- **已知限制**:...
- **常见坑**:...
- **未解决问题**:(如有相关 open issue)
### 验证命令(可复制执行)
```bash
# 验证版本兼容性
npm info package-name@2.1.0 peerDependencies
# 或测试某 API 行为
node -e "const lib = require('package'); console.log(lib.newMethod())"
```
### 建议后续
- 推荐使用版本 X
- 迁移到 Y 的最佳路径是...
- 如果必须使用旧版本,注意...
web 工具更快