Install any skill in seconds. Free to start, no credit card required.
Get Started Free →indranilbanerjee/eval-config
Configure content eval settings.
3 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
This benchmark measured an earlier version of the skill.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Update our dimension weights to: content_quality 0.10, brand_voice 0.10, hallucination_risk 0.10, claim_verification 0.10, output_structure 0.10, readability 0.10. Total sum is 0.60. Apply this set.
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the weight discrepancy where the total sum of 0.60 falls outside the allowed range | Passed | Passed |
| Refuses to save invalid weights without normalization | Missed | Passed |
The instructions your model reads when the skill loads.
Script location. If your host does not set
${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin'sscripts/folder, next toskills/. Run them with Python 3.10 or newer:python, orpython3wherepythonis not found (macOS, many Linux systems).
Configure the evaluation system for a brand. Set minimum quality thresholds per dimension, adjust scoring weights based on industry priorities and content strategy, configure auto-reject thresholds that prevent substandard content from passing evaluation, and define content-type-specific quality standards that apply different bars to different formats.
The eval config determines how strictly content is scored and what the quality bar looks like for the brand. A healthcare company may weight hallucination risk and claim verification heavily while relaxing readability thresholds for technical audiences. A consumer brand may prioritize brand voice and readability while accepting lighter claim verification for awareness content. An agency managing multiple brands can set different configs per brand. This command makes those trade-offs explicit and adjustable rather than buried in defaults.
The user must provide (or will be prompted for):
view (show current settings via get-config), set-threshold (change a minimum score for a dimension; add --content-type to scope the override to one content type), set-weights (change dimension weight distribution; add --content-type for a per-type override), set-auto-reject (change the composite score below which content automatically fails), recommend (analysis only — get industry-appropriate settings suggestions), or reset (restore all settings to defaults). There is no separate set-content-type action — content-type overrides are applied by passing --content-type to set-threshold / set-weights.content_quality, brand_voice, hallucination_risk, claim_verification, output_structure, readability, or composite{"content_quality": 0.25, "brand_voice": 0.20, "hallucination_risk": 0.20, "claim_verification": 0.15, "output_structure": 0.10, "readability": 0.10}. Weights must sum to approximately 1.0 (tolerance of +/- 0.02 for rounding)--content-type): The content type to configure overrides for, plus the overrides themselves — custom thresholds or weights that apply only to that content type~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply industry context for recommendation generation — different industries have different quality priorities. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, note any quality requirements defined in guidelines that should inform threshold recommendations. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.python "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action get-config to retrieve all current settings — global thresholds, dimension weights, auto-reject threshold, and any content-type-specific overrides. Identify which settings are custom (set by the user) and which are defaults.python "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action set-threshold --dimension {dimension} --threshold {value} (add --content-type {type} to scope it to one content type). Show before/after comparison with the impact on scoring strictnesspython "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action set-weights --weights '{weights_json}'. Show before/after comparison with an example of how the same content would score differently under old vs. new weightspython "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action set-auto-reject --threshold {score}. Show the impact — how many of the brand's recent evaluations would have been auto-rejected under the new threshold vs. the old one--content-type {content_type} to set-threshold or set-weights — e.g. python "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action set-threshold --dimension hallucination_risk --threshold 80 --content-type ad_copy. Show how this content type's effective config now differs from the global configskills/context-engine/eval-framework-guide.md for industry-specific recommendations. Present suggestions with rationale — e.g., "Healthcare brands should weight hallucination risk at 0.25+ because unverified health claims carry regulatory risk"python "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" --brand {slug} --action reset. Show what changes from the current custom config back to defaults and confirm before executingtest cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.