Author eval suite for agent `azure-resource-deployer`

Open
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
azure, javascript
Domain
testing-qa

Research direction

Read .github/agents/azure-resource-deployer.agent.md and the related harness conventions, then run /agent-bench azure-resource-deployer. Create the eval.yaml, positive and negative task files, manifest entry, and suite README; verify with waza run .github/evals/agents/azure-resource-deployer/eval.yaml -v that mock execution checks refusal or confirmation without real deployment.

Written by the indexing model from the issue text.

Description

AI-evals enhancement

Agent

azure-resource-deployer — source: .github/agents/azure-resource-deployer.agent.md

Scope

Author the eval suite at .github/evals/agents/azure-resource-deployer/:

  • eval.yaml — suite config (executor, model, graders)
  • At least 2 positive tasks under tasks/positive-*.yaml
  • At least 1 negative task under tasks/negative-*.yaml
  • Entry added to .github/evals/manifest.yaml at tier: expanded

Safety note (mandatory)

This agent has destructive tools (execute / real Azure deployment). The eval MUST exploit the agent's own safety contract: tasks should grade that the agent stops without confirmation or stays plan-only. NEVER author a positive task that exercises the destructive path on a real subscription. Document this design choice in the suite README so future maintainers don't add a "real deploy" positive task.

Procedure

  1. /agent-bench azure-resource-deployer drafts the suite from the live .agent.md.
  2. waza run .github/evals/agents/azure-resource-deployer/eval.yaml -v locally.
  3. /agent-improve azure-resource-deployer to iterate on graders.
  4. Open PR.
  5. Mock CI runs automatically. A maintainer will dispatch a real-model run before merge.

Acceptance

  • Suite runs cleanly in mock executor.
  • Positive tasks verify the agent refuses or pauses for confirmation — no real deployment.
  • All negative tasks produce a refusal or out-of-scope acknowledgement.
  • manifest.yaml entry added; PR description includes the real-model run summary.
  • Suite README documents the "no real deploy" design choice.

Conventions to follow

  • Persona lock: refusal graders should accept the agent's own scope language.
  • Prompt graders need continue_session: true in their grader config.

Related

  • Umbrella: #93
  • Harness: #61
Dominant language
JavaScript
Stars
269
Forks
45
Avg merge
1d 4h
Merged PRs (30d)
15

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/git-ape

All issues in Azure/git-ape

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.