Agent skill
get-config
Read engine configuration to get vault path. Called by all skills that need to access vault files.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/get-config
SKILL.md
Get Config
This sub-skill reads the engine configuration file to get the vault path.
Instructions
-
Read
.claude/config.mdfrom the engine root directory -
Parse the
vault_path:line to extract the path value -
Verify the vault path exists:
- If it doesn't exist, report error: "Vault not found at {path}. Run
/initto configure."
- If it doesn't exist, report error: "Vault not found at {path}. Run
-
Return the vault path for use in file operations
Output
Return structured JSON for the orchestrator to capture:
Success:
{
"success": true,
"VAULT": "/Users/me/OneDrive/vault",
"config_path": ".claude/config.md"
}
Error:
{
"success": false,
"error": "error_code",
"message": "Human-readable error message",
"suggestion": "Run `/init` to configure."
}
For backwards compatibility, also output the vault path in plain text:
$VAULT = /Users/me/OneDrive/vault
Error Cases
| Error Code | Condition | Message |
|---|---|---|
config_missing |
Config file not found | "No config.md found. Run /init fresh --vault=/path to set up." |
vault_path_missing |
vault_path not in config | "vault_path not configured. Run /init to configure." |
vault_not_found |
Directory doesn't exist | "Vault not found at {path}. Check path or run /init reconnect." |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?