external-collection
Use when the user wants to trigger, describe, or list refresh jobs for an external collection (a collection backed by an external data source such as Vector Lake). Note this is the data-plane refresh workflow, not collection CRUD -- for create/drop/load see the collection skill.
What this skill does
## Prerequisites 1. CLI installed, logged in, and cluster context set (see setup skill). 2. The target collection must already exist as an **external collection** (created with an `externalSource` / `externalSpec` schema in the collection skill). Plain in-place collections do not have refresh jobs. 3. The cluster must be running a `kite-coordinator` build that exposes `/v2/vectordb/jobs/external_collection/*` (PR #5735 or later). On older data planes the API returns 404 -- in that case ask the user to upgrade the cluster. ## Commands Reference The `external-collection` resource has a single operation, `refresh`, with three actions: `trigger`, `describe`, and `list`. All three are data-plane calls and inherit the database from the current context unless overridden with `--database`. ### Trigger a refresh job ```bash zilliz external-collection refresh trigger --name <collection-name> # Optional: # --database <db-name> Override the context database # --external-source <src> Override the external source registered on the collection # --external-spec <spec> Override the external spec registered on the collection ``` `trigger` returns the new `jobId`. Use it with `refresh describe` to poll status. The override flags are intentionally rare -- normally the source and spec are pinned at collection-create time, and a plain `refresh trigger --name <name>` is enough. ### Describe a refresh job ```bash zilliz external-collection refresh describe --job-id <id> ``` Returns the job's state, progress, and (on failure) the error message. ### List refresh jobs ```bash zilliz external-collection refresh list # Optional: # --name <collection-name> Filter to one external collection # --database <db-name> Override the context database ``` Without filters, `list` returns recent refresh jobs scoped to the current database. Pair with `--query` to extract a single field, e.g.: ```bash zilliz external-collection refresh list --name my_external_coll \ --query 'data[?state==`Pending` || state==`Running`].jobId' ``` ## Guidance - An external collection is a collection whose rows live in an external source (e.g. a Vector Lake table). The collection's metadata, indexes, and schema are in Milvus, but the data is pulled in on demand. The `refresh` job is what synchronises that external data into the collection so subsequent queries see fresh rows. - Refresh jobs are asynchronous. After `trigger`, poll with `describe` until the job reaches a terminal state. Do not assume completion just because `trigger` returned successfully -- that only means the job was accepted. - If `trigger` fails with "collection not found" or "not an external collection", verify with `zilliz collection describe --name <name>` that the collection actually has an `externalSource` field. If it does not, this is a normal in-place collection and refresh does not apply -- nothing needs to be done. - When `describe` reports a failed job, surface the error message to the user verbatim. It usually points at a credentials, network, or schema mismatch in the external source rather than a Milvus bug. - Avoid scheduling overlapping refresh jobs against the same collection -- check `list --name <name>` for an already-running job before triggering a new one. - A `trigger` on a large external table can run for minutes. Do not hold a chat session open polling every few seconds -- give the user the `jobId` and explain how to come back and check `describe` later. - For related operations on the same collection (create, drop, load, query) defer to the `collection` skill. This skill only covers the refresh lifecycle.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.