c-thru-control

Control the c-thru proxy via natural-language intents mapped to REST endpoints.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/whichguy/c-thru --skill c-thru-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c-thru-control
Source: https://github.com/whichguy/c-thru/tree/main/skills/c-thru-control
Command: npx skills add https://github.com/whichguy/c-thru --skill c-thru-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interrogate and manage the c-thru proxy's status, models, and connectivity using natural language prompts to switch modes and monitor health.

Core Features & Use Cases

  • Inspect hardware status, active model mappings, and connectivity health.
  • Dynamically switch routing modes (connected, offline, local-only, etc.) via natural language prompts.
  • Query and adjust the proxy configuration to align with hardware and network conditions.

Quick Start

Invoke the control with a natural-language intent, e.g., '/c-thru-control how are we running?'

Frequently Asked Questions about c-thru-control

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

FAQPage Schema
How do I monitor proxy hardware status and connectivity health using natural language?

You can monitor proxy hardware status by issuing natural language intents that map to the /c-thru/status endpoint, querying active model mappings and connectivity health for runtime governance.

Can I switch routing modes between connected, offline, and local-only via natural language prompts?

Yes, you can dynamically switch routing modes using natural language prompts that map to the /c-thru/mode endpoint, toggling between connected, offline, and local-only configurations.

How do I reload proxy configuration to align with network conditions?

You can reload proxy configuration by sending a natural language intent that maps to the /c-thru/reload endpoint, refreshing settings to align with current hardware and network conditions.

Does the c-thru proxy control support deterministic behavior across online and offline backends?

Yes, the c-thru proxy control applies deterministic behavior to runtime governance scenarios, performing queries, switches, and config refreshes across both online and offline backends.

What natural language syntax works for interrogating active model mappings in a proxy?

Natural language intents like asking how the proxy is running map to REST-like control endpoints, allowing you to interrogate active model mappings without manual API syntax.

When should I use natural language routing control instead of direct REST API calls?

Use natural language routing control for runtime governance scenarios where you need to quickly interrogate status, switch modes, or refresh configs without memorizing exact REST endpoint paths.