coferlandia-config-devops

Operates standardized configuration CLIs through execute or guided control-tower modes.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-config-devops-coferlandia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coferlandia-config-devops
Source: https://github.com/coferlandia/coferlandia-skills/tree/main/skills/ops/coferlandia-config-devops
Command: npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-config-devops-coferlandia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Changing configuration in a repository prepared by coferlandia-config-toolsmith requires knowing canonical field names, live environment state, and safe mutation boundaries. This Skill translates natural-language configuration goals into validated CLI operations without editing native config files directly or inventing undocumented fields. ## Core Features & Use Cases - Execute Mode: Inspects live state, prepares consolidated change plans, applies them through the standardized CLI, and validates effective state with rollback reporting. - Guide Mode (control tower): Produces exact batched commands for a human operator with platform access, marking every response as NOT EXECUTED until verifiable evidence returns. - Exhaustive fallback: Treats deterministic search as non-authoritative and reads the complete agent handbook before any negative capability conclusion. - Use Case: A user asks to rotate a database connection setting in production. The Skill inspects live effective values, prepares a state-bound plan, obtains approval, applies through the CLI, and reports changed artifacts, activation status, and rollback options. ## Quick Start Ask the agent to change a configuration value in a repository prepared by coferlandia-config-toolsmith, for example: update the log level to debug in the staging environment and verify the change.

Frequently Asked Questions about coferlandia-config-devops

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

FAQPage Schema
How do I change configuration values through a standardized CLI?▼

Use the Config Operator workflow: interpret the desired outcome, discover candidate fields, inspect live effective state, then run a consolidated prepare-change followed by apply-plan through the CLI. Post-change validation confirms effective values before completion is claimed.

What is the difference between Execute Mode and Guide Mode?▼

Execute Mode invokes the standardized CLI directly when the agent has environment access. Guide Mode acts as a control tower, producing exact batched commands for a person with platform access and marking every response as NOT EXECUTED until evidence returns.

Can I edit .env or YAML config files directly instead of using the CLI?▼

No. Direct edits to managed native stores such as .env, JSON, YAML, appsettings, databases, or secret providers are forbidden when a managed CLI operation exists. The facade owns validation, precedence awareness, and stale-state checks.

What happens when configuration search returns no matching field?▼

A search miss is inconclusive, not unsupported. The Skill reads the complete CONFIG-AGENT-HANDBOOK.md, inspects candidates, read-only entries, and unsupported adapters before concluding a field is truly not configurable.

When should I not use this configuration operator skill?▼

Do not use it when the repository lacks the generated contract, handbook, and standardized CLI from coferlandia-config-toolsmith. It also cannot promote pending candidates, write custom adapters, or invent undocumented fields.