Skip to content

Phase 4: auroraview-diagnostics + auroraview-devtools SKILL.md packages #368

Description

@loonghao

Part of #364.

Ship the first two SKILL.md packages that agents actually call. These exist solely to turn the adapter (Phase 2) + gateway discovery (Phase 3) into observable, useful tools without bloating the MCP context.

Skills

auroraview-diagnostics

Dcc scope: auroraview. Implicit-invocation allowed (cheap, read-only).

Tools:

  • list_windows — query FileRegistry for all dcc_type=auroraview entries; return [{pid, url, window_title, cdp_port}].
  • cdp_health — ping the CDP endpoint; return rtt_ms.
  • dump_console — connect CDP Runtime.consoleAPICalled, tail N messages.

auroraview-devtools

Dcc scope: auroraview. Implicit-invocation disabled (mutating). Agent must load_skill first — leverages dcc-mcp-core's progressive discovery to keep tools/list small.

Tools:

Delivery

Drop both under crates/auroraview-cli/skills/auroraview-cli skills install --target cursor picks them up automatically (PR #350's bundling already handles this).

Acceptance

With auroraview running + Cursor pointed at the gateway:

> @agent what auroraview windows are live?
  → calls auroraview-diagnostics/list_windows
  → returns [{ pid: 1234, url: "file:///…/index.html", cdp_port: 9222 }]

and tools/list contains only auroraview-diagnostics by defaultauroraview-devtools only appears after load_skill("auroraview-devtools"). That's the context-explosion fix landing in practice.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-dxAgent / AI developer experienceenhancementNew feature or requestintegrationCross-project integration (e.g. dcc-mcp-core)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions