grix-connector/dist/default-skills/grix-query/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-query
description: Use the typed `grix_query` tool for Grix contact lookup, keyword search, session search, and session message history lookup. Trigger when users ask to find contacts, search conversations, list visible sessions, or inspect recent messages in a known session.
trigger: 当用户要查找联系人、搜索会话、列出可见会话、或查看某个已知会话的历史消息时
---

# Grix Query

Use the `grix_query` tool for read-only Grix lookup. This skill only queries
existing contacts, sessions, and raw session messages — it never sends or
changes anything.

## Tool contract

Always call the `grix_query` tool with one `action`:

- `contact_search` — find contacts. Use exactly one mode: exact lookup with
  `id`, keyword search with `keyword`, or list-all with neither.
- `session_search` — find sessions. Same three modes as `contact_search`.
- `message_history` — read recent messages in a session. Requires `sessionId`;
  page backwards with `beforeId`.
- `message_search` — keyword search inside a session. Requires `sessionId` and
  `keyword`.

Other parameters: `limit` (1–100), `offset`.

## Rules

1. Parse the request into exactly one action before calling.
2. If both `id` and `keyword` are given, the backend prioritizes `id`; do not
   send both unless you explicitly want exact-match behavior.
3. For message history or in-session search when no `sessionId` is known, first
   locate the session via `session_search`, or ask the user for a precise target.
4. When a result is paginated and `has_more` is true, keep paging only when the
   user asked for everything, the target is still unresolved, or one page is
   clearly insufficient.
5. On scope/auth/parameter errors, report the exact failure and the fix; do not
   silently retry with guessed parameters.