做什么
解释 ADK Dev 控制台 — 每个标签显示的内容, 如何读取代理步骤、 痕迹、 多代理仪表板、代理切换、 控制台模式, 以及 adk dev 期间在 localhost: 301 显示的其他 UI 特性
技能库 智客分类:Agent 工作流 adk-dev-console
解释 ADK Dev 控制台 — 每个标签显示的内容, 如何读取代理步骤、 痕迹、 多代理仪表板、代理切换、 控制台模式, 以及 adk dev 期间在 localhost: 301 显示的其他 UI 特性
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
解释 ADK Dev 控制台 — 每个标签显示的内容, 如何读取代理步骤、 痕迹、 多代理仪表板、代理切换、 控制台模式, 以及 adk dev 期间在 localhost: 301 显示的其他 UI 特性
这个技能
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:ADK Dev Console、When to Use This Skill、Available Documentation、How to Answer、Quick Reference、Tab Groups。 其中含规范建议的小节:分步指令。
文件分析:除 SKILL.md 外,正文引用了 references/agent-steps.md、references/pages.md、references/component-registry.md、references/multi-agent-dashboard.md,属于带资源的技能包,这些文件按需再读。
Explains the ADK Dev Console — what each tab shows, how to read Agent Steps, traces, multi-agent dashboard, agent switching, console modes, and other UI features visible at localhost:3001 during adk dev
ADK Dev ConsoleWhen to Use This SkillAvailable DocumentationHow to AnswerQuick ReferenceTab GroupsAgent(0) Task DockMulti-Agent SidebarAgent Steps (Chat Page)Key URLsMulti-Agent CLI Commands
· 许可:MIT
来源分类:skills.sh agent-skill
nameadk-dev-consoledescriptionreferences/agent-steps.mdreferences/pages.mdreferences/component-registry.mdreferences/multi-agent-dashboard.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「adk-dev-console」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-9a2c07338c474922-%E9%98%BF%E5%BE%B7%E5%85%8B%C2%B7%E5%BE%B7%E5%A4%AB%E6%8E%A7%E5%88%B6%E5%8F%B0.html 请存为 .cursor/skills/adk-dev-console/SKILL.md 或 .claude/skills/adk-dev-console/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/botpress/skills 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/botpress/skills' --list
npx skills add 'https://github.com/botpress/skills' --skill 'adk-dev-console'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
The Dev Console is a local app served at port 3001 (by default, but can be customized) during adk dev. It gives developers real-time visibility into their agent's behavior — conversations, execution traces, data, integrations, and configuration.
The Dev Console is a singleton shared dashboard: one UI server per user, with multiple adk dev agents registering and deregistering dynamically. Developers can switch between running agents in the sidebar, toggle between dev and prod targets, and connect to deployed Cloud bots — all from the same browser tab.
Activate when users ask about:
adk ps show?", "How do I open the dashboard?"localhost:3001, "dev console", "Dev Console", "component registry", "agent selector", "agent picker", "agent map", "Cloud Dev Console", or specific tab names (Chat, Build, Components, Data, Test, Observe, Config)| File | Contents |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| references/agent-steps.md | Agent Steps visualization — turns, iterations, tools, messages, state mutations, cost tracking, status indicators |
| references/pages.md | Every page/tab in the Dev Console — what it shows, key features, layout |
| references/component-registry.md | Component Registry — installed vs registry tabs, component lifecycle, runtime registry internals, UI features |
| references/multi-agent-dashboard.md | Multi-agent architecture, agent selector, console modes (local/cloud), dev/prod targets, CLI commands (adk ps, adk kill, adk dashboard, adk status) |
Match depth to the question:
| Group | Pages | Purpose |
| -------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| Chat | Chat | Test the agent via webchat + see Agent Steps |
| Build | Agent Map | Interactive agent architecture graph (experimental, feature-flagged behind enable_agent_forge) |
| Components | Webchat Components, Actions, Workflows, Triggers | Browse component registry, test bot primitives |
| Test | RAG Search, Evals | Test knowledge search and run automated evals |
| Data | Knowledge, Tables, Files | Manage knowledge bases, tables, and files |
| Observe | Conversations, Traces, Logs | View conversation history, execution traces, runtime logs |
| Config | Settings, Integrations | Agent config, secrets, LLM settings, integration management |
When Agent(0) uses its todo tool, the panel shows a compact Tasks dock with completed/total count, the active task, and an expandable task list. Status icons map to pending, in progress, completed, and cancelled; priorities are shown as low/medium/high chips.
The sidebar header shows the currently selected agent with a status indicator and mode pill (dev/prod/cloud). Clicking it opens the Agent Selector dropdown:
The right panel of the Chat page shows Agent Steps — a real-time visualization of what the agent did to process each message.
Hierarchy: Turn → Iterations → Tools / Messages / State Mutations
Status indicators: ✓ green = ok, ✗ red = error, ⟳ blue spinning = running
AI metrics per iteration: model name, input/output tokens, cost (USD)
| Path | Page |
| ---------------- | --------------------------------------------------------- |
| /chat | Chat + Agent Steps |
| /agent-map | Agent Map — interactive architecture graph (experimental) |
| /components | Component registry + installed components |
| /actions | Actions browser |
| /workflows | Workflows + run history |
| /search | RAG search testing |
| /evals | Eval definitions + runs |
| /knowledge | Knowledge base management |
| /tables | Table data management |
| /traces | Full trace viewer |
| /conversations | Conversation history |
| /logs | Runtime logs |
| /settings | Agent configuration |
| /integrations | Integration management |
| Command | Purpose |
| --------------- | -------------------------------------------------------------------------------- |
| adk ps | List running agents and processes with PIDs, ports, uptime (supports --watch) |
| adk dashboard | Open the DevConsole in standalone mode (no agent required) |
| adk kill | Stop agents or the entire DevConsole (--all, --current, --pid, or by name) |
| adk status | Show project health and status info |
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…