Skip to content
Back to skills

Effort Trial

ASecurity

Measure whether council roles find more at a higher effort than at a lower one, per unit of cost, and suggest each role's effort preset. Use when the user asks to tune council effort or model costs, or invokes /agent-arena-mode:effort-trial.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
ai-agentspython

Security analysis

A100/100

Scanned November 11, 2026

npx -y skills add ahmadhammoud56/MOAA --skill effort-trial --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Effort Trial?

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

Security grade badge for Effort Trial
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ahmadhammoud56-effort-trial/badge)](https://www.skillsdirectory.com/skills/ahmadhammoud56-effort-trial)

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: effort-trial
description: Measure whether council roles find more at a higher effort than at a lower one, per unit of cost, and suggest each role's effort preset. Use when the user asks to tune council effort or model costs, or invokes /agent-arena-mode:effort-trial.
argument-hint: "--roles r1,r2 [--efforts medium,high] [--repeats N] -- TASKS or a tasks.json path"
---

# Agent Arena: effort trial

Request: `$ARGUMENTS`. Plugin root: `${CLAUDE_PLUGIN_ROOT}`. Use the substituted absolute path in commands.

Effort is a cost lever, and lowering it can lose real findings, so measure instead of guessing.

1. **Tasks.** Use tasks with checkable findings: planted bugs, known errors, a reference answer. Write
   `tasks.json` as `[{"id", "brief", "rubric", "expected_findings"}]` in a fresh folder under the session
   scratchpad. Two to four tasks per role give a first signal; say how small the sample is.
2. **Plan.** `python "${CLAUDE_PLUGIN_ROOT}/scripts/effort.py" plan --roles ROLES --efforts medium,high --tasks
   <tasks.json> --out <folder>`. It prints every cell (role, effort, task) in shuffled order with a blind label.
3. **Run.** For each cell, dispatch `specialist-council:council-<role>` with the task's brief, byte-identical across
   cells of that task, and the cell's effort in the Agent tool's per-call `effort` field. Launch independent cells
   together. Note the tokens each run reports.
4. **Judge blind.** Give `agent-arena-mode:agent-arena-judge` the task, rubric and the answers under their blind
   labels only, never role or effort. Get a 0 to 100 score and the count of correct findings per answer.
5. **Record.** `python ".../effort.py" record --dir <folder> --cell ID --score S --findings N --tokens T`.
6. **Summarize.** `python ".../effort.py" summary --dir <folder>`. It keeps the cheaper effort unless the dearer one
   adds at least 5 points of score or 25% more findings. Report the table and the suggestion. Change a role's preset
   in `specialist-council/profile.json` (then `scripts/models_doc.py`) only after the user agrees.

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.

View all in ai-agents →

Comments

Loading comments…

Newsletter

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