eval-config
starsforks
How to install eval-config?
indranilbanerjee/digital-marketing-pro/eval-config
$npx -y skills add indranilbanerjee/digital-marketing-pro --skill eval-configConfigure content eval settings. Use when: adjusting score thresholds, dimension weights, or auto-reject rules.
SKILL.md
| 1 | # /digital-marketing-pro:eval-config |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | ## Input Required |
| 10 | |
| 11 | The user must provide (or will be prompted for): |
| 12 | |
| 13 | - **Configuration action**: What to do — `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`. |
| 14 | - **Dimension name** (for set-threshold): The dimension to configure — `content_quality`, `brand_voice`, `hallucination_risk`, `claim_verification`, `output_structure`, `readability`, or `composite` |
| 15 | - **Threshold value** (for set-threshold): The minimum acceptable score (0-100) for the specified dimension. Content scoring below this threshold on any dimension is flagged as a failure on that dimension |
| 16 | - **Weights** (for set-weights): A JSON object mapping dimension names to their weights — e.g., `{"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) |
| 17 | - **Auto-reject score** (for set-auto-reject): The composite score below which content automatically fails regardless of individual dimension scores — typically 40-60 depending on brand standards |
| 18 | - **Content type** (for set-content-type): The content type to configure overrides for, plus the overrides themselves — custom thresholds or weights that apply only to that content type |
| 19 | |
| 20 | ## Process |
| 21 | |
| 22 | 1. **Load brand context**: Read `~/.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. |
| 23 | 2. **Get current configuration**: Execute `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. |
| 24 | 3. **Present current settings**: Display all configuration in a clear, readable format: |
| 25 | - **Global thresholds**: Each dimension's minimum score with its current value and whether it is custom or default |
| 26 | - **Dimension weights**: Each dimension's weight in the composite score calculation, shown as both decimal and percentage, with a visual indicator of relative importance |
| 27 | - **Auto-reject threshold**: The composite score floor with its current value |
| 28 | - **Content-type overrides**: Any content types with custom settings, showing how they differ from the global config |
| 29 | - **Effective scoring example**: Show what a hypothetical evaluation would look like under the current config — e.g., "With these weights, a piece scoring 90 on content quality but 50 on hallucination risk would get a composite of X" |
| 30 | 4. **Process configuration changes**: Based on the requested action: |
| 31 | - **set-threshold**: Validate the threshold value is between 0 and 100. Execute `python "${CLAUDE_PLUGIN_ROOT}/scripts/eval-config-manager.py" - |
People who liked this also viewed
6 picksType
- tddSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeSkillsJul 2026
- qaSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidenceSkillsJul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser lSkillsJul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, teSkillsJul 2026
