editing-config-toml

Edit System2 config.toml database connections and operational settings safely.

9|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/diegoscarabelli/system2 --skill editing-config-toml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editing-config-toml
Source: https://github.com/diegoscarabelli/system2/tree/main/src/server/agents/skills/editing-config-toml
Command: npx skills add https://github.com/diegoscarabelli/system2 --skill editing-config-toml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, safe protocol for modifying the System2 operational configuration file without corrupting critical settings or accidentally exposing sensitive credentials.

Core Features & Use Cases

  • Targeted Configuration: Enables precise editing of database connections, agent behavior overrides, and operational tunables using safe string replacement.
  • Safety Guardrails: Enforces a strict separation between operational settings and sensitive credentials, ensuring that LLM and service keys remain protected in the managed auth file.
  • Use Case: When adding a new PostgreSQL database for analytical queries, use this skill to ensure the connection block is correctly formatted and placed, preventing daemon startup errors.

Quick Start

Use the editing-config-toml skill to add a new postgres database connection block for the analytics server to the config file.

Frequently Asked Questions about editing-config-toml

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

FAQPage Schema
How do I safely edit the config.toml file for a System2 operational environment?

To safely edit the config.toml file for a System2 operational environment, apply a strict editing protocol using targeted string replacement to prevent daemon startup errors and protect credentials.

What is the safest way to add a PostgreSQL database connection to my configuration?

The safest way to add a PostgreSQL database connection is using a structured editing protocol that ensures the connection block is correctly formatted and placed within the config.toml file.

Can I store sensitive LLM and service keys directly inside the config.toml file?

No, you cannot store sensitive LLM and service keys in the config.toml file; operational settings and credentials must remain strictly separated to ensure keys stay protected in a managed auth file.

How do I configure per-agent behavior overrides in System2?

You can configure per-agent behavior overrides in System2 by applying precise string replacements to the operational tunables within the config.toml file, ensuring strict adherence to the defined editing protocol.

Why does the System2 daemon fail to start after manually updating the configuration file?

The System2 daemon may fail to start after manual config updates if the editing protocol is not followed, leading to incorrectly formatted connection blocks or corrupted critical settings in the config.toml file.