When should I use config-reader?

config-reader is useful in the following scenarios: • Case 1: Seamlessly migrating legacy plaintext settings in CLAUDE.md to structured blocks for better agent parsing and reliability. • Case 2: Automating the retrieval of environment-specific variables, such as worktree directories or preferred LLM settings, to streamline developer workflows. • Case 3: Auditing and verifying configuration integrity across project-level and global user-level settings to prevent environment conflicts during agent execution.

When & Why to Use This Skill

The Daplug Config Reader is a specialized utility designed to manage and synchronize agent configurations within CLAUDE.md files. It provides a robust framework for reading, writing, and migrating settings using structured XML blocks, ensuring that Claude agents maintain consistent environment awareness and operational context across different projects and user scopes.

Use Cases

Case 1: Seamlessly migrating legacy plaintext settings in CLAUDE.md to structured <daplug_config> blocks for better agent parsing and reliability.
Case 2: Automating the retrieval of environment-specific variables, such as worktree directories or preferred LLM settings, to streamline developer workflows.
Case 3: Auditing and verifying configuration integrity across project-level and global user-level settings to prevent environment conflicts during agent execution.

name	config-reader
description	Read and manage daplug configuration from CLAUDE.md using <daplug_config> blocks, with legacy fallback and migration support.
- Bash(python3	*)
- Bash(jq	*)

name

config-reader

description

Read and manage daplug configuration from CLAUDE.md using <daplug_config> blocks, with legacy fallback and migration support.

- Bash(python3

- Bash(jq

Daplug Config Reader

Centralized configuration reader/migrator for daplug settings stored in <daplug_config> blocks inside CLAUDE.md. Provides backwards compatibility with legacy plaintext settings and safe migrations.

When to Use This Skill

Any command/skill needs daplug settings (preferred agent, worktree dir, llms_txt dir, ai usage awareness, cli logs dir)
Before writing to CLAUDE.md for daplug settings
When a user asks to migrate or audit CLAUDE.md config

Config Format

<daplug_config>
preferred_agent: codex
worktree_dir: .worktrees/
llms_txt_dir: /storage/projects/docker/llms_txt
ai_usage_awareness: enabled
cli_logs_dir: ~/.claude/cli-logs/
</daplug_config>

Usage

PLUGIN_ROOT=$(jq -r '.plugins."daplug@cruzanstx"[0].installPath' ~/.claude/plugins/installed_plugins.json)
CONFIG_READER="$PLUGIN_ROOT/skills/config-reader/scripts/config.py"

Get Single Setting

python3 "$CONFIG_READER" get preferred_agent

Dump All Settings (JSON)

python3 "$CONFIG_READER" dump --json

Dump as ENV Vars

python3 "$CONFIG_READER" dump --env

Status / Verification

python3 "$CONFIG_READER" status
python3 "$CONFIG_READER" status --json

Check Legacy Settings

python3 "$CONFIG_READER" check-legacy

Migrate Legacy Settings

# Project and user
python3 "$CONFIG_READER" migrate --all

# Project only
python3 "$CONFIG_READER" migrate --project

# User only
python3 "$CONFIG_READER" migrate --user

Set a Setting

# Project scope
python3 "$CONFIG_READER" set worktree_dir ".worktrees/" --scope project

# User scope
python3 "$CONFIG_READER" set preferred_agent "codex" --scope user

Notes

Lookup order: project CLAUDE.md (repo root) → user ~/.claude/CLAUDE.md
Legacy plaintext settings are still supported but trigger warnings
Migrations create a timestamped backup before writing