Menu
Display all configuration options with their effective value and which config layer set them.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Backport existing plans into the Obsidian daily journal. Use when plans exist in the vault but are missing journal entries.
Estimate the scope and runtime of the frontmatter backfill — hardware specs, vault size, pending upgrades, and a calibrated time estimate. Read-only; nothing is modified.
Upgrade existing vault notes to the current frontmatter standard (type, date, duration_s, normalized model + context_window) so they appear in the managed Obsidian bases. Interruptible and resumable.
Display current session details including ID, duration, turn counts, token usage, and tool stats.
Toggle session document capture on or off. Use /session on, /session off, or /session to toggle.
Rewrite the Obsidian daily journal for a selected day from existing plan/summary notes. Use when journal entries are missing, corrupted, or need regeneration.
| name | config-print |
| description | Display all configuration options with their effective value and which config layer set them. |
Display every capture-plan config option, its current effective value, and which layer provided it.
CLAUDE_CWD="$PWD" bun ${CLAUDE_PLUGIN_ROOT}/hooks/print-config.ts
Parse the JSON output. It contains:
options — array of objects with key, value, and sourceconfigPaths — object with plugin, user, and project file paths (resolved for the current platform)warnings — optional array of { key, table, layer } entries flagging top-level scalar keys found scoped under a nested table (typically a TOML placement bug — the value is still recovered)Render a markdown table with these columns:
| Option | Value | Source |
|---|
For each entry in options:
plan.path)(not set) for null values.default, plugin, user, projectAfter the table, extract and display the resolved paths from the JSON response under configPaths:
"configPaths": {
"plugin": "...",
"user": "...",
"project": "..."
}
Display as:
configPaths.pluginconfigPaths.user (auto-resolved for the current platform)configPaths.project (or (not set) if outside a project)If warnings is present and non-empty, render a ## Warnings section after the paths. For each entry, display:
- `<key>` found under `[<table>]` in <layer> TOML — value was recovered to top level. Move the key out of the table to silence this warning.
Skip the section entirely when warnings is absent or empty.