agentleFS
Sign inStart free
jame581jame581/LogseqBrain/.claude/skills/eval/SKILL.md

eval

Skill18 starsChanged 23 days agoMITView on GitHub

Run the logseq-brain eval suite in WSL2 as the logseq-eval user — free --check by default, a paid full or single-case run only after confirmation. Invoke only when the user asks to run evals.

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docs-ci, docs-interfaces and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • +4 more from jh941213

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it only through WSL2 as the logseq-eval user: wsl -d FedoraLinux-44 -u logseq-eval sh /mnt/d/AI/logseq-brain/tools/eval/run.sh ….

    line 13
  2. Distinctive:

    Run it through PowerShell, or through Bash with single quotes.

    line 15
  3. Very specific:

    Always run --check first. Before any paid mode, state the estimated cost and wait for a yes.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “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 the eval suite

evals/README.md is the source of truth. Read it before running anything the first time in a session.

Hard rules

  • Run it only through WSL2 as the logseq-eval user: wsl -d FedoraLinux-44 -u logseq-eval sh /mnt/d/AI/logseq-brain/tools/eval/run.sh …. Never run it on native Windows, and never as the Docker-linked user.
  • It evaluates committed files only. If git status shows uncommitted changes to plugin/, say that they won't be evaluated.
  • Run it through PowerShell, or through Bash with single quotes. wsl.exe heredocs halve backslashes.

Modes

AskCommand argsCost
default / "check"--checkfree: case schema and tool grants
harness self-testrun sh tools/eval/test.sh locallyfree
one case--case <name>paid, a fraction of a full run
full(no args)paid, ≈ $4–7 of plan usage

Always run --check first. Before any paid mode, state the estimated cost and wait for a yes.

Reading the result

  • Exit 0 means every case passed and the canary is clean. A usage-limit error is not a failure; rerun after the limit resets.
  • A failed case may be rerun once with --case <name>. A pass on the rerun counts as a flake, and a second failure is a real failure.
  • Report per-case pass/fail, both canary lines, and the load-digest and save-basic tool-call figures. Reports land in evals/results/, which is gitignored.

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