mj-agent-runtime-eval-baseline

Drafts read-only EVAL baseline proposals for mj-agent skills and system prompts.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-runtime-eval-baseline-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-runtime-eval-baseline
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-runtime-eval-baseline
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-runtime-eval-baseline-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes to mj-agent in-source canonical files (SKILL.md bodies and system.md prompts) risk silent failures like wrong answers, hallucinations, or business drift, and this Skill produces a reviewable EVAL baseline design draft before any evaluation framework exists. ## Core Features & Use Cases - EVAL Design Drafting: Fills the TEMPLATE_EVAL.md 8-section template with eval_kind classification (outcome/trajectory/component/integration), dataset structure, judge selection, and regression thresholds. - Reverse-Scan of Existing Evaluations: Greps target frontmatter eval_references, docs/evaluation/, and tests/eval/ fixtures to avoid duplicate EVAL designs. - Read-Only HITL Workflow: Produces a proposed EVAL document plus structured HITL questions for Domain Expert and Prompt Engineer review without writing to docs/evaluation/ or running pytest. - Use Case: After a B-flavor change to the biz-domain-context SKILL.md, invoke this Skill to draft an outcome-based EVAL with red-line cases covering R1/R2 data boundary rules, then hand the accepted draft to /mj-agent-doc-author for writing. ## Quick Start Ask the agent to propose an EVAL baseline for the biz-domain-context skill and review the drafted TEMPLATE_EVAL document with the HITL questions.

Frequently Asked Questions about mj-agent-runtime-eval-baseline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I propose an EVAL baseline for an mj-agent skill?▼

Invoke this Skill with the target skill or prompt name, and it reads the target, classifies the eval_kind, reverse-scans existing eval_references, then outputs a filled TEMPLATE_EVAL.md draft. You review the HITL questions and use /mj-agent-doc-author to write the accepted draft to docs/evaluation/.

What eval_kind should I choose for a SKILL.md change?▼

Choose outcome for end-to-end SQL or answer correctness, trajectory for tool-call sequence checks, component for single-skill behavior, or integration for multi-skill coordination. The Skill recommends one or two kinds with reasoning based on the target's nature.

Can this Skill run the actual EVAL or write to docs/evaluation/?▼

No, it is read-only by design per ADR-015. It never edits docs/evaluation/ or tests/eval/, never runs pytest, and never modifies in-source canonical files; actual EVAL execution waits for the Phase 2 EVAL framework (PR-D2-enforcement).

What regression threshold should an EVAL baseline use?▼

Default is 0.05 absolute for low-risk skill changes, 0.03 for system.md hard rule changes, and 0 for red-line cases where any regression is a data boundary incident. Red-line regressions are hard blockers that trigger mandatory HITL stops.

When should I skip creating a new EVAL baseline?▼

Skip when the change is only a frontmatter typo or markdown formatting that does not trigger substantive change rules, or when the target already has an active EVAL whose baseline_value remains within the regression_threshold.