CtrlK
BlogDocsLog inGet started
Tessl Logo

config-loading-precedence

How Xberg resolves configuration — CLI-mode and server/MCP-mode precedence orders, config file auto-discovery (xberg.{toml,yaml,json}), field-level inline JSON merge (merge_json_into_config), config file formats, and apply_extraction_overrides. Load when adding a config flag or env var, changing config precedence, or debugging why a setting is or isn't taking effect.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured reference for config loading and precedence that respects token budget and gives mostly concrete guidance. The main weakness is the partial merge_json_into_config code snippet, which is not executable as written.

Suggestions

Make the merge_json_into_config snippet executable: show the actual field-level merge (e.g., iterate json object and overwrite matching keys in config_json) instead of a placeholder comment and an undefined `merged` variable.

Add a one-line concrete example of --config-json / --config-json-base64 invocation so users can see the expected input shape without inferring it.

Clarify the relationship between apply_extraction_overrides and the precedence list (e.g., note it runs after JSON merge) to make the CLI override flow fully traceable.

DimensionReasoningScore

Conciseness

Lean and efficient: numbered precedence lists, a minimal TOML example, and terse prose with no padding or explanation of concepts Claude already knows (e.g., what TOML/YAML/JSON are).

5 / 5

Actionability

Mostly executable with concrete TOML config and explicit precedence orderings, but the merge_json_into_config Rust snippet is partial — `merged` is undefined and a comment stands in for the actual merge logic, so it is not copy-paste ready.

4 / 5

Workflow Clarity

Clear numbered sequences for both CLI and server precedence plus a 'Critical Rules' checklist; not a destructive/batch workflow so no validation cap applies, though it lacks explicit checkpoints because it is reference material rather than a procedural workflow.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references, but the body is slightly over the ~50-line simple-skill threshold and inlines config-format reference material that could arguably live in a separate file.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill covers and gives concrete, natural trigger phrases for when to load it. It avoids fluff and uses appropriate third-person voice.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete elements — CLI/server precedence orders, auto-discovery of xberg.{toml,yaml,json}, field-level JSON merge (merge_json_into_config), config formats, and apply_extraction_overrides — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (how Xberg resolves configuration) and 'when' via the concrete 'Load when adding a config flag or env var, changing config precedence, or debugging...' trigger clause.

5 / 5

Trigger Term Quality

Natural trigger phrases a developer would actually say — 'adding a config flag or env var', 'changing config precedence', 'debugging why a setting is or isn't taking effect' — plus concrete file extensions.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Xberg config-loading precedence) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xberg-io/xberg
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.