yolop-config

Inspect and update settings.toml for the yolop terminal agent.

12|Updated May 27, 2026
One-click install
npx skills add https://github.com/everruns/yolop --skill yolop-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yolop-config
Source: https://github.com/everruns/yolop/tree/main/src/bundled/system-skills/yolop-config
Command: npx skills add https://github.com/everruns/yolop --skill yolop-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the complexity of manually editing configuration files, ensuring that your terminal agent settings are validated, persisted, and applied correctly without risk of syntax errors.

Core Features & Use Cases

  • Schema-Aware Configuration: Safely update providers, models, and API tokens using validated tools rather than manual file editing.
  • Capability Management: Easily inspect and override harness capabilities to customize agent behavior.
  • Use Case: When you need to switch your default LLM provider to Anthropic or store a new API key, this skill handles the update atomically to ensure your agent remains functional.

Quick Start

Ask the agent to set the default provider to anthropic and store your new api key.

Frequently Asked Questions about yolop-config

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

FAQPage Schema
How do I update terminal agent settings without causing syntax errors in the configuration file?

You can change the default LLM provider by asking the terminal agent to update your settings, which triggers a validated, atomic write to the settings.toml file to securely store your new API token and provider selection.

How do I inspect and override harness capabilities for my terminal agent?

You can inspect and override harness capabilities by using this configuration management skill, which provides a validated interface to safely adjust and apply agent behavior overrides to your settings.toml file.

What is the best way to manage API tokens and model selection for a terminal agent?

The best way to manage API tokens and model selection is through a schema-aware configuration interface that validates inputs and atomically persists your preferences, ensuring the terminal agent remains functional without manual file editing.

Does this configuration tool require manually editing the settings.toml file?

No, it does not require manually editing the settings.toml file, as the skill abstracts the complexity by providing a schema-aware interface that validates and atomically applies all provider and capability updates.