跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 agent-pulse

Agent Pulse

使用 Agent Pulse 来检查赫耳墨斯,克洛德代码, Codex, DeepSeek, OpenClaw, Copilot, Aider, Quen, OpenCode, Goose, Cursor, Antigravity, 和 Amp 日志的本地AI代理活动. 当用户询问AI代理会话,信使,工具/搜索呼叫,模型使用,估计成本,预算,预测,健康检查,报告,设置诊断,网络/API/计量输出,或MCP整合时使用.

47552 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

使用 Agent Pulse 检查 Hermes 、 Claude Code 、 Codex 、 DeepSeek 、 OpenClaw 、 副驾驶 、 Ader 、 Quen 、 OpenCode 、 Goose 、 Cursor 、 Antigravity 和 Amp 日志的本地AI 代理活动

何时用

用户询问AI代理会话、信使、工具/搜索呼叫、模型使用、估计费用、预算、预测、健康检查、报告、设置诊断、网络/API/度量衡出口或MCP整合

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Agent Pulse、Purpose、Source Keys、Choose Commands、Workflow、Interpreting Results。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/run_agent_pulse_snapshot.py,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.

Agent PulsePurposeSource KeysChoose CommandsWorkflowInterpreting ResultsReportsIntegrationsMCPLocal Helper

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
agent-pulse
description
Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • scripts/run_agent_pulse_snapshot.py

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「agent-pulse」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-ff228046039b2ee3-%E4%BB%A3%E7%90%86%E8%84%89%E5%86%B2.html
请存为 .cursor/skills/agent-pulse/SKILL.md 或 .claude/skills/agent-pulse/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/jane-o-o-o-o/agent-pulse-skill 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/jane-o-o-o-o/agent-pulse-skill' --list

npx skills add 'https://github.com/jane-o-o-o-o/agent-pulse-skill' --skill 'agent-pulse'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: agent-pulse description: Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration. --- # Agent Pulse ## Purpose Use the installed `agent-pulse` CLI as the source of truth for local AI-agent activity. The PyPI package is `agentpulse-cli`, while the command remains `agent-pulse`. Prefer running commands and summarizing their output over reading the Agent Pulse source code. Always enable UTF-8 on Windows before running commands because Agent Pulse output contains emoji and box drawing: ```powershell $env:PYTHONUTF8='1' $env:PYTHONIOENCODING='utf-8' ``` If `agent-pulse` is not on PATH, ask before installing dependencies. If the user approves, install the PyPI package or try running from a local project checkout: ```powershell pip install agentpulse-cli ``` ```powershell python -m agent_pulse.cli --version ``` ## Source Keys Use `-P/--platform` when the user asks about one agent tool instead of all local data: ```text hermes, claude, codex, deepseek, openclaw, copilot, aider, qwen, opencode, goose, cursor, antigravity, amp ``` ## Choose Commands Use this command selection table first: | User wants | Run | |---|---| | Current status | `agent-pulse status --json` | | Full dashboard | `agent-pulse --json` or `agent-pulse --no-banner` | | Demo data | `agent-pulse demo --json` | | Setup diagnosis | `agent-pulse doctor --json` | | Recent sessions | `agent-pulse --json --hours 24 --limit 20` | | Top sessions | `agent-pulse top --sort tokens --json` | | Top expensive sessions | `agent-pulse top --sort cost --json --hours 168` | | Model cost analysis | `agent-pulse models --json` | | Model ranking | `agent-pulse leaderboard --json --rank-by efficiency` | | Cost savings | `agent-pulse optimize --json` | | Budget status | `agent-pulse budget --json` | | Cost forecast | `agent-pulse forecast --json` | | Cost anomaly check | `agent-pulse anomaly --json` | | Health/CI check | `agent-pulse health --json` | | Composite score | `agent-pulse score --json` | | Search sessions | `agent-pulse search "" --json` | | Compare periods | `agent-pulse compare --json` | | Compare projects | `agent-pulse compare-projects --json` | | Activity calendar | `agent-pulse heatmap --json` | | Smart recommendations | `agent-pulse insights --json` | | Prometheus metrics | `agent-pulse metrics --format prometheus` | | Export report | `agent-pulse export -f markdown` or `agent-pulse export-html` | | Web dashboard | `agent-pulse web --port 8765` | | REST API | `agent-pulse api --port 8766` | | MCP tools | `agent-pulse mcp --list-tools` | If the installed command lacks an option, run `agent-pulse --help` and adapt. ## Workflow 1. Start with `agent-pulse doctor --json` only when the user asks why data is missing, asks for setup help, or a normal data command returns no sessions. 2. Use JSON output whenever possible. Summarize the fields that matter: sessions, tokens, tools, search calls, model breakdown, source breakdown, estimated cost, warnings. 3. Use time filters for scoped questions. Default to 24 hours for "recent" and 168 hours for "this week": ```powershell agent-pulse status --json --hours 24 agent-pulse --json --hours 168 --limit 50 ``` 4. Use platform filters when the user asks about a specific agent system: ```powershell agent-pulse --json -P codex --hours 24 agent-pulse --json -P claude --hours 24 agent-pulse top --json -P aider --sort cost agent-pulse status --json -P cursor ``` 5. For cost questions, pair summary, model, and top-session views: ```powershell agent-pulse status --json --hours 24 agent-pulse models --json --hours 24 agent-pulse top --sort cost --json --hours 24 agent-pulse optimize --json --hours 168 ``` 6. For trend and risk questions, use forecast/history/compare/anomaly: ```powershell agent-pulse forecast --json agent-pulse history --json agent-pulse compare --json agent-pulse anomaly --json ``` 7. For setup, use the discovery commands before guessing paths: ```powershell agent-pulse doctor --json agent-pulse scan --json --details agent-pulse config show ``` ## Interpreting Results - Treat `total_cost_usd` as an estimate based on Agent Pulse's local model pricing table. - Report both cost and token volume; low-cost models can still have very high token usage. - Distinguish sources such as `codex`, `claude`, `hermes`, `deepseek`, `openclaw`, `aider`, `cursor`, `opencode`, and `goose`. - Mention if `doctor` reports missing optional sources, missing `dev_root`, or optional web dependencies. - If no sessions appear, check `doctor`, then try a wider time window such as `--hours 168`. - Check whether the user asked for a source (`-P`) filter, a model filter, or a project comparison before giving overall totals. - If a command emits plain text instead of JSON or fails because an installed version is older, run `agent-pulse --help` and use the closest supported option. ## Reports For a short human-readable answer, run JSON commands and summarize. For artifacts, prefer: ```powershell agent-pulse report --period daily agent-pulse export -f markdown agent-pulse export-html ``` Do not invent exact savings or costs. Use the CLI output. ## Integrations Use the web and API extras only when the user asks for a browser dashboard or programmatic server. Ask before installing missing extras: ```powershell pip install "agentpulse-cli[web]" agent-pulse web --port 8765 agent-pulse api --port 8766 ``` For monitoring pipelines: ```powershell agent-pulse metrics --format prometheus agent-pulse health --cost-limit 100 --token-limit 1000000 --json ``` ## MCP Use MCP mode when the user wants other AI clients to query Agent Pulse: ```powershell agent-pulse mcp --list-tools agent-pulse mcp ``` When explaining MCP, mention that it exposes tools such as status, forecast, top sessions, model analytics, optimization, health, search, and leaderboard. ## Local Helper This skill includes `scripts/run_agent_pulse_snapshot.py`, which runs a compact set of JSON-friendly Agent Pulse checks and prints a combined summary: ```powershell python scripts/run_agent_pulse_snapshot.py --hours 24 --days 7 ```

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…