grix-connector/dist/default-skills/grix-task-status/SKILL.md

Connect local AI coding agents (Claude, Codex, Gemini, Qwen, DeepSeek, Cursor, OpenCode, Pi, OpenHuman, Reasonix) to the Grix scheduling platform. Also serves as an OpenClaw plugin for Grix channel transport.

---
name: grix-task-status
description: Observe state — query the task state of all the owner's sessions (`grix_task_query`), and check the current MCP connection status (`grix_status`). Trigger when the user asks which tasks are running/done/waiting, or to verify the Grix connection is healthy.
trigger: 当用户问哪些任务在跑/已完成/在等待审批,或要确认 Grix 连接是否正常时
---

# Grix Task & Status

Read-only observation of task and connection state.

## Owner task states — `grix_task_query`

Query the session-level task state across all the owner's sessions. Takes no
parameters — owner and agent are resolved from the authenticated connection.
Returns one entry per session with a single mutually-exclusive state:

- `running` — working
- `waiting_approval` — blocked on the owner to approve/deny
- `waiting_question` — asked the owner a question, awaiting reply
- `completed` / `failed` — finished
- `idle` — no task / stopped

Use it to see at a glance which tasks are done, still running, or waiting on the
owner.

## Connection status — `grix_status`

Query the Grix connection status of the current MCP session. Takes no
parameters. Use it to confirm the agent is connected before relying on other
grix tools.

## Rules

1. Both tools are read-only — safe to call any time to orient yourself.
2. `grix_task_query` reports per-session state, not per-message; pair it with
   `grix_query` (`message_history`) when you need the actual content.