agentleFS
nic095laysonnic095layson/claude/.claude/skills/validation-and-evals/SKILL.md

validation-and-evals

Skill1 starsChanged 4 months agoNo licenceView on GitHub

How to prove a skill in this repo actually behaves correctly — what counts as evidence, the evals.json schema, the three claude-council eval cases with concrete pass criteria, the manual run protocol, how to add a case, and the before/after acceptance rule for SKILL.md edits. Load this when you are about to run the evals, grade a run pass/fail against a case's criteria, add a new eval case, or someone asks "did this change work?", "run the evals", "how do we test this skill?". Do NOT load for mechanical file/packaging checks (use diagnostics-and-tooling), for building an automated harness (use eval-harness-campaign), for deciding whether a change is allowed at all (use change-control), or for deciding how much evidence a wording experiment needs and whether its outcome counts (use research-methodology).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.