Extract machine-agnostic settings into portable template files while keeping machine-specific hooks and plugins separate
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill portable-config-baseline-pattern --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Portable Config Baseline Pattern?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-portable-config-baseline-pattern)More formats (shields.io, HTML) on the badges page.
---
name: portable-config-baseline-pattern
description: Extract machine-agnostic settings into portable template files while keeping machine-specific hooks and plugins separate
version: 1.0.0
source: auto-extracted
extracted: 2026-04-11
metadata:
tags: ["architecture", "configuration-management", "portability"]
---
# Portable Config Baseline Pattern
When managing config files across multiple machines, separate portable baseline settings (safe everywhere) from machine-specific wiring (hooks, plugins, local paths). Use a template file (e.g., `config/agents/Codex/settings.json`) as the canonical portable baseline, then layer machine-specific overrides in the live config. Verify separation by grepping for actual execution paths—only comments and diagnostic messages should reference machine-specific tools; all real calls use portable resolution patterns like `command -v python3 || command -v python`.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
