菜单
Prepare and drive clean public llm-cli-gateway demo sessions for recordings, README demos, screenshots, or transcripts. Use when the user needs a redacted path, compact Codex output, direct provider calls, or a demo-safe Codex environment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | public-demo-session |
| description | Prepare and drive clean public llm-cli-gateway demo sessions for recordings, README demos, screenshots, or transcripts. Use when the user needs a redacted path, compact Codex output, direct provider calls, or a demo-safe Codex environment. |
| metadata | {"author":"verivus-oss","version":"1.0"} |
Use this skill when the goal is a public recording, README demo, screenshot, or clean transcript. The priority is a short, reliable demo surface, not exhaustive orchestration.
/llm-cli-gateway.A public demo is not a review shortcut. If the user explicitly asks for a
full-access, native-MCP, evidence-backed review, leave demo mode and follow the
multi-llm-review full-access protocol. Build the exact target checkout and
launch node dist/index.js --transport=stdio from it, rather than using a demo
or globally installed gateway. Reapply the provider-native grant per new job,
send the corrective-program verification report and exact diff/file identity,
require independent code/docs/tests inspection, set no caller caps, and honor a
user-required 90-second progress cadence. Do not use direct provider calls or a
public demo home as a substitute for that review path.
Do not start Codex directly from an internal checkout path for public demos. A symlink may still leak a resolved path in some tools. Prefer a bind-mounted public path:
bwrap \
--bind "$REAL_REPO" /llm-cli-gateway \
--chdir /llm-cli-gateway \
--setenv CODEX_HOME "$DEMO_CODEX_HOME" \
codex --dangerously-bypass-approvals-and-sandbox
If the host needs Codex HTTPS/WebSocket support inside the mount namespace, bind the host CA backing store too. On this host /etc/ssl/certs depends on /var/lib/ca-certificates.
The demo CODEX_HOME should have a minimal config.toml with:
model = "gpt-5.5"
model_reasoning_effort = "high"
project_doc_max_bytes = 0
[projects."/llm-cli-gateway"]
trust_level = "trusted"
[mcp_servers.llm-gateway]
command = "node"
args = ["/llm-cli-gateway/dist/index.js"]
Keep the demo home separate from the normal Codex home. Symlink auth.json from the normal Codex home if needed, but do not copy private history or sessions.
For simple “ask the other LLMs” demo prompts, use direct provider tools:
claude_request({ prompt: "...", outputFormat: "text" });
gemini_request({ prompt: "...", outputFormat: "text" });
mistral_request({ prompt: "...", outputFormat: "text", trust: true });
Provider-specific notes:
maxTurns to claude_request unless the current schema explicitly supports it.skipTrust:true to Gemini/Antigravity: the current gateway path
rejects it. Establish the intended workspace/project trust before recording.trust:true to Mistral/Vibe for the same reason.grok_request in demos unless the user explicitly names Grok and the local Grok CLI has been checked in this environment.codex_request from inside a Codex demo unless the user explicitly asks for nested Codex.Do not use these by default for a public demo prompt:
ask_modelvalidate_with_modelscompare_answersconsensus_checksecond_opinionred_team_reviewsynthesize_validation*_request_asyncllm_job_status, llm_job_watch, llm_job_result, llm_job_cancelIf a provider fails, state that briefly and continue with useful returned outputs. Do not turn a short demo into a recovery workflow.
Before recording:
codex doctor --summary --no-color
Expected: MCP server present, WebSocket connected, provider endpoints reachable, and 0 warn · 0 fail.
Confirm the opening screen shows:
directory: /llm-cli-gateway
Manage long-running async LLM jobs across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for parallel or non-blocking execution. Covers backend-qualified durability, cache-aware `promptParts`, `cache-state://` MCP resources, and the Claude `cache_ttl_expiring_soon` warning.
Implement a change, obtain complete evidence-backed review through the local stdio gateway, fix findings, and repeat without arbitrary review limits. Use for features, bugs, or refactoring.
Orchestrate security-sensitive LLM work with the gateway's Claude-managed approval boundary, provider-native legacy controls, evidence-aware auditing, and complete no-limit review handling.
Manage gateway bookkeeping and provider-native conversation continuity across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for multi-turn work, session inspection, and safe resume decisions.
Obtain complete, evidence-backed agreement from a required roster of llm-cli-gateway providers. Use for high-stakes generation, conflict resolution, or final quality gates that require unconditional approval from every required reviewer.
Orchestrate the complete llm-cli-gateway provider surface through its local stdio MCP server. Use for parallel implementation, review, session, async-job, cache-aware prompt, and cross-LLM workflows across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor.