agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ai-engineer-talks/run-aiewf-2024-evals/SKILL.md

run-aiewf-2024-evals

Skill1 starsChanged 5 months agoMITView on GitHub

Runs checklists for AIEWF 2024 eval and LLM ops talks — domain eval ladders, LLM judges, enterprise deploy, Zapier+Braintrust loops, GenAI maturity before fine-tune. Use when the user says "evals", "LLM judge", "fine-tune decision", "enterprise GenAI deploy", or AIEWF eval playlist.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the decision tree below.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run AIEWF 2024 evals & LLM ops

Action playbook from six AI Engineer / World's Fair talks. Do not summarize talks — pick a workflow and execute it.

Supporting files (read when needed):

  • workflows.md — workflows A–F (steps, deliverables, stop conditions)
  • source-index.md — src-NNN → talk learnings in ingest-into-skills

Optional: {SKILL_OUTPUT_DIR}/run-aiewf-2024-evals/


Step 0 — Pick workflow

Use the decision tree below. Open the matching section in workflows.md.

What is the user trying to do?
├─ Build domain eval from zero (assertions → judges)     → A
├─ Layer task evals on routers/tools (trace-native)        → B
├─ Calibrate LLM judges / courtroom rubrics              → C
├─ PM+eng eval ops (Zapier/Braintrust regression)          → D
├─ Enterprise CX: full conversation intelligence           → E
└─ Decide fine-tune vs prompt/distill (maturity curve)     → F

Stop summarizing once a workflow is identified — run its checklist.


Install

cp -r skills/run-aiewf-2024-evals ~/.claude/skills/
cp -r skills/run-aiewf-2024-evals ~/.cursor/skills/
cp -r skills/run-aiewf-2024-evals ~/.codex/skills/

From skills-i-use or ingest-into-skills (playlists/evals-llm-ops-aie-world-s-fair-2024/).


Cross-cutting rules

RuleSource
Evals ≠ demos; log before judges[src-001 @ 6:39]
Assertions before LLM-as-judge[src-001 @ 4:41]
Layer scores on router/tools/answer[src-004 @ 4:46]
Fine-tune only after eval + teacher data[src-006 @ 5:55]

Disputed steps: see source-index.md. Name workflow A–F; save artifacts to ./skill-outputs/run-aiewf-2024-evals/ when requested; do not auto-commit.


Invocation examples

@run-aiewf-2024-evals build domain eval harness for our agent
should we fine-tune or stay on GPT-4o?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.