Skip to content

feat(evaluator): surface skill evaluators (TOOL_CALL level + skill placeholders) - #1

Closed
jariy17 wants to merge 1 commit into
bug_bash_aug_18thfrom
skill-evaluators-p0
Closed

feat(evaluator): surface skill evaluators (TOOL_CALL level + skill placeholders)#1
jariy17 wants to merge 1 commit into
bug_bash_aug_18thfrom
skill-evaluators-p0

Conversation

@jariy17

@jariy17 jariy17 commented Aug 17, 2026

Copy link
Copy Markdown
Owner

Stacked on bug_bash_aug_18th (PR aws#2012). Surfaces the P0 skill evaluators in the CLI. Scope: only the pieces that work today — the two built-in skill evaluators are already ACTIVE service-side (verified). Ground-truth expectedSkills is intentionally excluded (no service field exists yet — it would no-op).

Changes

  1. Built-in level resolution (src/cli/operations/eval/run-eval.ts): map Builtin.SkillSelectionAccuracy and Builtin.SkillInstructionFollowing to TOOL_CALL. Without this they fall through to the SESSION default and get scored against the wrong spans — silently. Fixes run eval / run batch-evaluation targeting for skill evaluators.
  2. Custom-evaluator TUI placeholders (src/cli/tui/screens/evaluator/types.ts): expose {available_skills}, {invoked_skill}, {skill_content} for TOOL_CALL LLM-judge evaluators, matching the service prompt-template contract. Shown in the wizard's instructions step and accepted by validateInstructionPlaceholders.
  3. Tests for both.

Verification

  • npm run typecheck — clean
  • affected unit tests — 67 passed (incl. new resolves Builtin skill evaluators to TOOL_CALL level)
  • eslint + prettier + secretlint (pre-commit) — clean

Explicitly out of scope

  • expectedSkills ground-truth (batch + on-demand): net-new across the AgentCore Evaluation model, not merged / not in review. Ship behind a flag once the service adds the field + a GT skill-selection evaluator.

Follow-up (not here)

Replace the static BUILTIN_EVALUATOR_LEVELS map with a cached listEvaluators() lookup so future built-ins self-resolve (the map already omits Harmfulness/Stereotyping/ToolParameterAccuracy/trajectory matchers).

…aceholders)

- run-eval: map Builtin.SkillSelectionAccuracy / Builtin.SkillInstructionFollowing
  to TOOL_CALL so they target skill-invocation spans instead of falling through to
  the SESSION default (which scores the wrong spans, silently).
- evaluator TUI: expose {available_skills} / {invoked_skill} / {skill_content}
  placeholders for TOOL_CALL custom LLM-judge evaluators, matching the service
  prompt-template contract.
- tests for both.

Follow-up (not in this PR): replace the static BUILTIN_EVALUATOR_LEVELS map with a
cached listEvaluators() lookup so future built-ins self-resolve.
@jariy17

jariy17 commented Aug 17, 2026

Copy link
Copy Markdown
Owner Author

Superseded: reopened from aws/agentcore-cli:skill-evaluators-p0 into bug_bash_aug_18th (no fork).

@jariy17 jariy17 closed this Aug 17, 2026
@jariy17
jariy17 deleted the skill-evaluators-p0 branch August 17, 2026 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant