configure-laruche

Inspect LaRuche node configuration via local API and guide users through settings changes.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill configure-laruche-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configure-laruche
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/configure-laruche
Command: npx skills add https://github.com/infinition/LaRuche --skill configure-laruche-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up or troubleshooting a self-hosted LaRuche AI node requires knowing where each setting lives and what is actually configured right now. This Skill reads the live state of the node through its loopback API and turns it into exact click-path instructions, avoiding stale guesses and dangerous direct file edits. ## Core Features & Use Cases - Live state inspection: Queries endpoints like /api/onboarding, /api/doctor, and /api/config/provider on the local node (default port 8419) to report what is actually configured. - Guided configuration: Maps every setting (providers, channels, secrets vault, voice, MCP server, accounts) to its exact location in the web interface, since writes require the user's browser session. - Pitfall prevention: Flags known traps such as cron-only cadences, global tool disabling, the unauthenticated MCP server default, and shared memory across accounts. - Use Case: A user asks why their Telegram channel is not responding. The Skill curls /api/config/channels, reports the actual channel state, and gives the exact Settings path to fix the token, recommending a vault reference instead of a literal key. ## Quick Start Ask the assistant to check the current LaRuche setup status and walk you through configuring your LLM provider.

Frequently Asked Questions about configure-laruche

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

FAQPage Schema
How do I check my LaRuche node configuration?▼

Query the local API with curl against http://127.0.0.1:8419/api/onboarding to see each setup step with its done status and instructions. For a fuller health picture, call /api/doctor, where every check includes a detail field explaining its verdict.

How do I configure the LLM provider in LaRuche?▼

Read the current state from /api/config/provider and /api/profiles, then make changes in the web interface under Settings > Models & Providers. Writes require an authenticated browser session, so configuration cannot be changed through unauthenticated API calls.

Can I store API keys securely in LaRuche?▼

Yes, store keys as vault references like ${OPENAI_KEY} instead of literals via Settings > Secrets & Webhooks. References are expanded at call time and never written to provider-profiles.json on disk, unlike literal keys.

Why does my LaRuche cron or mission schedule get rejected?▼

mission_create and cron_create only accept five-field cron expressions such as 0 20 * * *. Natural language schedules like "every evening at 20:00" are rejected, so convert the intended time into minute hour day month weekday format.

Does disabling a tool in LaRuche affect MCP clients?▼

Yes, disabling a tool under Settings > Capabilities disables it everywhere: for the agent, for you, and for MCP clients. There is no per-surface toggle, and the MCP server is off by default but exposes every tool including shell_exec when enabled.