From zai
Manually consult GLM-5.2 (Z.ai) via the `zai` CLI — fast by default, `--deep` for reasoning. The user-invoked `/zai:glm` surface; complementary to Claude, never a replacement. For autonomous cross-checks use the `ask-glm` skill instead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zai:glm [--deep] [--effort max] [--file PATH] <question>[--deep] [--effort max] [--file PATH] <question>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Self-Evolving Skill**: This skill improves through use. If the `zai` invocation drifted,
/zai:glm)Self-Evolving Skill: This skill improves through use. If the
zaiinvocation drifted, a flag changed, or the passthrough broke, fix this file immediately — don't defer. Only update for real, reproducible issues.
Run the zai CLI to consult GLM-5.2 with the user's arguments, then relay the answer
(note it's GLM's, not Claude's).
zai chat $ARGUMENTS
--deep/--effort, keep them (extended reasoning). Otherwise it runs fast.--file <path> (GLM-5.2 accepts ~1M input tokens).zai websearch "<query>" / zai read <url> instead.zai plugin's references/CAPABILITIES.md.This is the manual surface (
disable-model-invocation: true) — it fires only when the user types/zai:glm. When Claude should consult GLM on its own initiative, that's theask-glmskill, not this one.
After running this skill, reflect before closing the task:
zai call fail or a flag not behave as documented? Fix the command or the
argument-hint here immediately, and note it in the zai plugin's references/CAPABILITIES.md./zai:glm when ask-glm or zai websearch fit better? Sharpen
this skill's description so the right surface triggers next time.Do NOT defer. The next invocation inherits whatever you leave behind.
npx claudepluginhub terrylica/cc-skills --plugin zaiGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.