agentleFS
gohypergiantgohypergiant/agent-skills/skills/accelint-eval-architect/AGENTS.md

agent-skills / accelint-eval-architect

AGENTS.md25 starsChanged 54 days agoApache-2.0View on GitHub

Quick-reference for the accelint-eval-architect skill. Load specific references only when the workflow step in SKILL.md names them.

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Every metric needs a regression test that proves it can fail.

    line 38
  2. Distinctive:

    Commit eval source before the first run.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md 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
AGENTS.md

Eval Architect — Agent Reference

Quick-reference for the accelint-eval-architect skill. Load specific references only when the workflow step in SKILL.md names them.

Target types

  • skill — a skill in this repo (SKILL.md at root). Assessment reads files.
  • tool-repo — a standalone tool repo, esp. a RAG/retrieval pipeline. Assessment reads what it can, then interviews the developer for stages + invocation.

Modes (one-line each)

  • ASSESS — read/interview the target → eval profile → verifiability gate (per stage for pipelines) → framework recommendation. Read-only.
  • SCAFFOLD — copy a framework starter, generate the walking skeleton, wire the build, hand off calibration.
  • AUDIT — run the decay checklist against an existing evals/ dir.
  • EXTEND — add metrics/fixtures to an existing eval; scaffold_eval.py --layer pulls in another template's non-conflicting files.

Reference table of contents

ReferenceLoad whenHolds
references/assessment.mdASSESS, target_type=skillwhat to read in a target skill; the eval-profile JSON schema
references/tool-repo-assessment.mdASSESS, target_type=tool-reporepo comprehension interview; tool-repo eval profile
references/pipeline-decomposition.mdpipeline targetsstage taxonomy; per-stage metric matrix; per-stage verifiability gate
references/gold-set.mdRAG targetsgold-set bootstrap, curation, circularity warning, corpus-hash drift
references/framework-matrix.mdASSESS step 3–4verifiability gate; decision tree; per-framework when/why; cost; worked examples; recommendation-summary format
references/test-design.mdASSESS step 5 (skill)persona×scenario derivation; output-shape→metric mapping; regression-test designs
references/calibration.mdSCAFFOLD step 12baseline→threshold workflow
references/audit.mdAUDITdecay checklist + severity ranking
references/frameworks/deepeval.mdscaffolding DeepEvalBedrock openai/ prefix; GEval 4.x kwarg forwarding; fenced-JSON extraction; EXPECTED_OUTPUT placeholder; logprobs ERROR suppression
references/frameworks/ragas.mdscaffolding a RAG answer layerRagas vs DeepEval; faithfulness/context-recall gotchas; gold-set wiring
references/frameworks/deterministic-vitest.mdscaffolding a Node deterministic harnessfixture layout; recall/precision tests; regression-test convention
references/frameworks/deterministic-pytest.mdscaffolding a Python deterministic harnessconftest fixtures; shelling to a validator CLI; regression tests
references/frameworks/human-review.mdoutput is taste-basedwhen to refuse automation; the review-checklist template

Rules (one-line; full reasoning in SKILL.md "NEVER" section)

  • Deterministic check before judge — always.
  • Generate goldens from the live schema; never hand-write them.
  • Thresholds start record-only; calibrate from a baseline before committing numbers.
  • One fixture / one metric / one pass test / one regression test — skeleton, not suite.
  • Every metric needs a regression test that proves it can fail.
  • Derive persona×scenario from the skill; flat fixtures when single-mode.
  • Commit eval source before the first run.
  • Match harness toolchain to the target (vitest for Node, pytest for Python).
  • Taste-based output → human-review checklist, not an LLM judge.
  • Detectors ship recall + false-positive-resistance as a pair — either alone rewards degenerate behavior.
  • Pipeline targets: run the verifiability gate per stage (ingest/retrieve are usually deterministic; only generate needs a judge).
  • RAG gold sets are human-curated; never trust a bootstrap draft as-is.
  • Tool-repo comprehension is interactive; confirm stages + invocation before recommending.

Scripts

  • scripts/scaffold_eval.py — copy a template; --layer add-only into an existing eval (reports conflicts); --dest alternate dirname; fails fast on missing required placeholders.
  • scripts/bootstrap_goldset.py — draft a RAG gold set (content-based corpus hash; PDFs via optional pypdf; mandatory human curation; refuses to overwrite an existing draft without --force).
  • scripts/suggest_thresholds.py — suggest calibrated thresholds from results/run-*.json with evidence.
  • scripts/audit_checks.py — mechanical audit checks (#2/#3/#4-partial/#7/#8/#11/#12/#13/#14); pairs with references/audit.md.

Scope

Scaffolds: DeepEval, deterministic-vitest, deterministic-pytest, human-review, rag (deterministic ingest+retrieve layer + gated Ragas answer layer in one template; no separate "deterministic-retrieval" key). Tool-repo support: RAG / retrieval pipelines. Recommends-but-hands-off (no scaffold yet): Promptfoo, Inspect AI, non-RAG tool types.

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.