Skip to content
Back to skills

Eval Recipes Runner

FSecurity

Run Microsoft's eval-recipes benchmarks to validate amplihack improvements against baseline agents. Auto-activates when testing improvements, running evals, or benchmarking changes.

  • 666 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 8, 2026
toolsbashdockertestinggitapidocumentation

Works with

  • cli
  • api

Security analysis

F38/100
  • criticalPipes output to a shell interpreter
  • mediumUses curl or wget to download content
  • criticalDownloads and executes remote scripts — classic supply chain attack
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill eval-recipes-runner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Eval Recipes Runner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Eval Recipes Runner
[![Security: F — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-eval-recipes-runner/badge)](https://www.skillsdirectory.com/skills/majiayu000-eval-recipes-runner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: eval-recipes-runner
version: 1.0.0
description: |
  Run Microsoft's eval-recipes benchmarks to validate amplihack improvements against baseline agents.
  Auto-activates when testing improvements, running evals, or benchmarking changes.
---

# eval-recipes Runner Skill

## Purpose

Run Microsoft's eval-recipes benchmarks to validate amplihack improvements against baseline agents.

## When to Use

- User asks to "test with eval-recipes"
- User says "run the evals" or "benchmark this change"
- User wants to validate improvements against codex/claude_code
- Testing a PR branch to prove it improves scores

## Capabilities

I can run eval-recipes benchmarks to:

1. Test specific amplihack branches
2. Compare against baseline agents (codex, claude_code)
3. Run specific tasks (linkedin_drafting, email_drafting, etc.)
4. Compare before/after scores for PRs
5. Generate reports with score improvements

## How It Works

### Setup (One-Time)

```bash
# Clone eval-recipes from Microsoft
git clone https://github.com/microsoft/eval-recipes.git ~/eval-recipes
cd ~/eval-recipes

# Copy our agent configs
cp -r $(pwd)/.claude/agents/eval-recipes/* data/agents/

# Install dependencies
uv sync
```

### Running Benchmarks

**Test a specific branch:**

```bash
# Update install.dockerfile to use specific branch
# Then run benchmark
cd ~/eval-recipes
uv run eval_recipes/main.py --agent amplihack --task linkedin_drafting --trials 3
```

**Compare before/after:**

```bash
# Test baseline (main)
uv run eval_recipes/main.py --agent amplihack --task linkedin_drafting

# Test PR branch (edit install.dockerfile to checkout PR branch)
uv run eval_recipes/main.py --agent amplihack_pr1443 --task linkedin_drafting

# Compare scores
```

### Available Tasks

Common tasks from eval-recipes:

- `linkedin_drafting` - Create tool for LinkedIn posts (scored 6.5/100 before PR #1443)
- `email_drafting` - Create CLI tool for emails (scored 26/100 before)
- `arxiv_paper_summarizer` - Research tool
- `github_docs_extractor` - Documentation tool
- Many more in `~/eval-recipes/data/tasks/`

### Typical Workflow

When user says "test this change with eval-recipes":

1. **Identify the branch/PR** to test
2. **Update agent config** to use that branch:
   ```dockerfile
   # In .claude/agents/eval-recipes/amplihack/install.dockerfile
   RUN git clone https://github.com/rysweet/...git /tmp/amplihack && \
       cd /tmp/amplihack && \
       git checkout BRANCH_NAME && \
       pip install -e .
   ```
3. **Copy to eval-recipes:**
   ```bash
   cp -r .claude/agents/eval-recipes/* ~/eval-recipes/data/agents/
   ```
4. **Run benchmark:**
   ```bash
   cd ~/eval-recipes
   uv run eval_recipes/main.py --agent amplihack --task TASK_NAME --trials 3
   ```
5. **Report scores** and compare with baseline

### Expected Scores

**Baseline (main branch):**

- Overall: 40.6/100
- LinkedIn: 6.5/100
- Email: 26/100

**With PR #1443 (task classification):**

- Expected: 55-60/100 (+15-20 points)
- LinkedIn: 30-40/100 (creates actual tool)
- Email: 45/100 (consistent execution)

## Example Usage

**User says:** "Test PR #1443 with eval-recipes on the LinkedIn task"

**I do:**

1. Update install.dockerfile to checkout `feat/issue-1435-task-classification`
2. Copy to eval-recipes: `cp -r .claude/agents/eval-recipes/* ~/eval-recipes/data/agents/`
3. Run: `cd ~/eval-recipes && uv run eval_recipes/main.py --agent amplihack --task linkedin_drafting --trials 3`
4. Report results: "Score: 35.2/100 (up from 6.5 baseline)"

## Prerequisites

- eval-recipes cloned to `~/eval-recipes`
- API key in environment: `export ANTHROPIC_API_KEY=sk-ant-...`
- Docker installed (for containerized runs)
- uv installed: `curl -LsSf https://astral.sh/uv/install.sh | sh`

## Notes

- Benchmarks take 2-15 minutes per task depending on complexity
- Multiple trials (3-5) give more reliable averages
- Docker builds can be cached for speed
- Results saved to `.benchmark_results/` in eval-recipes repo

## Automation

For fully autonomous testing:

```bash
# Test suite for a PR
tasks="linkedin_drafting email_drafting arxiv_paper_summarizer"
for task in $tasks; do
  uv run eval_recipes/main.py --agent amplihack --task $task --trials 3
done

# Compare results
cat .benchmark_results/*/amplihack/*/score.txt
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.