public-demo-session

Set up a privacy-compliant public demo session for llm-cli-gateway with direct provider calls.

10|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/verivus-oss/llm-cli-gateway --skill public-demo-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-demo-session
Source: https://github.com/verivus-oss/llm-cli-gateway/tree/main/.agents/skills/public-demo-session
Command: npx skills add https://github.com/verivus-oss/llm-cli-gateway --skill public-demo-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for clean, redacted public demos of llm-cli-gateway, ensuring privacy and a controlled demo environment.

Core Features & Use Cases

  • Public Workspace Path: Provides a standardized workspace path for public demonstrations.
  • MCP Server and Workspace Skills Availability: Maintains availability of core MCP server and workspace skills.
  • Direct Provider Calls: Facilitates direct, synchronous provider calls for compact text output.
  • Avoids Validation Wrappers: Omits validation wrappers for streamlined demos.
  • Path Hygiene: Ensures that sensitive paths are not exposed in public demos.

Quick Start

Use the 'public-demo-session' skill to set up a clean public demo environment for llm-cli-gateway.

Frequently Asked Questions about public-demo-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a clean public demo session for llm-cli-gateway without exposing sensitive paths?

A clean public demo session uses a standardized workspace path to enforce path hygiene and prevent sensitive directory exposure. It maintains core MCP server and workspace skills availability while keeping the demonstration controlled and privacy-compliant.

What does a privacy-compliant public demo environment for llm-cli-gateway look like?

A privacy-compliant public demo environment provides direct, synchronous provider calls for compact text output while omitting validation wrappers. It ensures sensitive paths are redacted and avoids complex features not needed for reliable demonstrations.

Can I use direct provider calls during a public demo session to reduce latency?

Yes, the public demo session facilitates direct provider calls to ensure a short, reliable demonstration experience. By bypassing validation wrappers and minimizing processing, the session delivers compact text output efficiently.

Do I need validation wrappers for a streamlined llm-cli-gateway code demo?

No, validation wrappers are omitted in this public demo session to streamline the demonstration. Avoiding these wrappers and other complex features ensures minimal processing and a short, reliable demo experience.

Why should I avoid complex features when preparing a public code demo?

Complex features are avoided to ensure path hygiene and maintain a controlled, privacy-compliant demo environment. This minimal processing approach guarantees a short, reliable demonstration without exposing sensitive workspace configurations.