agentleFS
Sign inStart free
JetXu-LLMJetXu-LLM/DocMason/skills/operator/operator-eval/SKILL.md

operator-eval

Skill152 starsChanged 4 months agoApache-2.0View on GitHub

Run the hidden operator-only evaluation loop over local runtime/eval artifacts without exposing that surface in normal first-contact workflows.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this workflow only for advanced operator-quality tasks such as replayable evaluation runs, regression review, candidate promotion, and …

    line 8
  2. Very specific:

    Do not surface it in ordinary user entry flows, and do not treat it as part of the default ask experience.

    line 11
  3. Very specific:

    Read the current operator request from runtime/eval/requests/current.json.

    line 21
  4. Very specific:

    Keep live eval truth under runtime/eval/, not under tracked repository paths.

    line 28
  5. Very specific:

    Keep review of ordinary runtime activity under runtime/logs/.

    line 29
  6. Distinctive:

    Treat tracked examples as schema guidance only.

    line 30

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

Operator Eval

Use this workflow only for advanced operator-quality tasks such as replayable evaluation runs, regression review, candidate promotion, and baseline freezing.

This workflow is intentionally open-source but non-first-contact. Do not surface it in ordinary user entry flows, and do not treat it as part of the default ask experience.

Required Capabilities

  • local file access
  • shell or command execution
  • ability to inspect structured JSON output

Procedure

  1. Read the current operator request from runtime/eval/requests/current.json.
  2. Validate the request against the tracked examples in skills/operator/operator-eval/examples/.
  3. Execute exactly one requested action through the operator-eval runtime surface:
    • run-suite
    • review-regressions
    • promote-candidate
    • freeze-baseline
  4. Keep live eval truth under runtime/eval/, not under tracked repository paths.
  5. Keep review of ordinary runtime activity under runtime/logs/.
  6. Treat tracked examples as schema guidance only. Never commit confidential runtime/eval payloads.
  7. Return the operator-facing result, written artifacts, and next corrective step to the main agent.

Notes

  • This workflow is intentionally absent from first-contact guidance.
  • Frozen baselines and promotion decisions remain human-governed even though this workflow is productized.
  • skills/operator/operator-eval/examples/ exists so fresh open-source users can understand the local-only artifact contracts without access to private corpus data.

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.

Check your setup, free