config

Deep-merge common settings with tool-specific overrides from tribunal.yaml.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/jpeggdev/buildwithjpegg --skill config-jpeggdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/tribunal/skills/config
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill config-jpeggdev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies complex configuration management by providing a robust system for deep-merging layered settings, ensuring consistency and flexibility across different tools and environments.

Core Features & Use Cases

  • Layered Configuration: Merges common settings with tool-specific overrides for tribunal.yaml.
  • Deep Merging: Handles nested objects and arrays intelligently, ensuring all settings are correctly applied.
  • Use Case: When running Tribunal with the 'claude' tool, this skill ensures that common settings like timeout_seconds are used, but also applies the more specific timeout_seconds defined for 'claude' in the tribunal.yaml file.

Quick Start

Resolve the configuration for the 'claude' tool using the tribunal.yaml file in the current directory.

Frequently Asked Questions about config

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

FAQPage Schema
How do I deep-merge layered configuration overrides in YAML?

Layered configuration resolution merges common settings from tribunal.yaml with tool-specific overrides, intelligently handling nested objects and arrays so all settings apply correctly. This ensures consistency and flexibility across different tools and environments.

What is layered configuration resolution for multi-agent systems?

Layered configuration resolution is the process of deep-merging common settings with tool-specific overrides in tribunal.yaml. It dynamically manages hierarchical configuration for multi-agent system features like agent selection, debate parameters, and coverage enforcement.

How do I apply tool-specific settings overrides to common configuration?

You apply tool-specific overrides by deep-merging them with common settings in tribunal.yaml. For example, when running the 'claude' tool, common settings like timeout_seconds are used, but the specific timeout_seconds defined for 'claude' take precedence.

Can I use hierarchical configuration management for agent selection and debate parameters?

Yes, hierarchical configuration management applies to all Tribunal features requiring dynamic configuration, including agent selection, debate parameters, and coverage enforcement. It resolves settings from tribunal.yaml to satisfy flexible multi-agent system requirements.

Does deep merging handle nested objects and arrays in tribunal.yaml?

Yes, deep merging handles nested objects and arrays intelligently within tribunal.yaml. This ensures that all common and tool-specific settings are correctly applied across different tools and environments without losing hierarchical structure.