New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Client Test

by leanEthereum in leanEthereum/leanSpec

Run leanSpec fixtures against a client implementation. An agent skill from leanEthereum/leanSpec.

MITAuto-check passedDevelopment

Install Client Test

skills CLI
$ npx skills add leanEthereum/leanSpec --skill client-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install leanEthereum/leanSpec client-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/client-test .claude/skills/client-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
client-test
GitHub stars
143
Token cost
~594 tokens
SKILL.md length
265 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Run leanSpec fixtures against a client implementation. An agent skill from leanEthereum/leanSpec.

  • Works in 4 steps: Check fixtures exist → Clone or update client → Sync fixtures → …
  • Development work in your project
  • SKILL.md covers Usage, Steps and Clients
  • Calls cmake, uv and cargo

What it does

Client Test is an agent skill from leanEthereum/leanSpec. Run leanSpec fixtures against a client implementation

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Ethereum. The repository describes itself as: Lean Ethereum protocol specifications and test vector generation framework. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/client-test”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Check fixtures exist
  2. Clone or update client
  3. Sync fixtures
  4. Run tests

What it can do on your machine

Read from SKILL.md and the folder at commit 0b7d33e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cmake
    • uv
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Client Test loads about 594 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~16
When it runs · the whole SKILL.md, loaded when a task matches
~594

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from leanEthereum/leanSpec at commit 0b7d33e, republished under its MIT licence (© leanEthereum). 265 words, ~594 tokens.

Download SKILL.mdSave it as .claude/skills/client-test/SKILL.md (or your agent's skills folder).
name
client-test
description
Run leanSpec fixtures against a client implementation

/client-test - Client Integration Testing

Run generated leanSpec test fixtures against a client implementation.

Usage

/client-test <client-name> e.g. /client-test ream

Steps

1. Check fixtures exist

Generated fixtures live at fixtures/consensus/. Verify it contains JSON files. If empty or missing, generate them:

bash
uv run fill --fork=Lstar --clean -n auto --scheme=prod

Fixtures for client testing must always use --scheme=prod (production signatures).

2. Clone or update client

Clone the client repo into clients/ (gitignored). If already cloned, pull latest.

3. Sync fixtures

Remove old fixtures at the destination, then copy the contents of fixtures/consensus/ to the destination (destination path is client-dependent).

4. Run tests

Run the test command from the client's test workdir (path is client-dependent). Show full output. Do not abort early on test failures.

If zero tests ran, warn that the client may need to update its test runner to scan the new devnet fixture path.

Clients

ream
  • Repo: https://github.com/ReamLabs/ream.git
  • Fixture destination (relative to repo root): testing/lean-spec-tests/fixtures/lstar
  • Test workdir (relative to repo root): testing/lean-spec-tests
  • Test command: cargo test --release --features lean-spec-tests
zeam
  • Repo: https://github.com/blockblaz/zeam.git
  • Fixture destination (relative to repo root): leanSpec/fixtures/consensus (leanSpec is a git submodule)
  • Test workdir (relative to repo root): . (repo root)
  • Test commands (run in order):
    1. zig build spectest:generate --summary all (generate Zig test wrappers from JSON fixtures)
    2. zig build spectest:run --summary all (run the spec tests)
qlean-mini
  • Repo: https://github.com/qdrvm/qlean-mini.git
  • Branch: spec/test-vectors (test vector infrastructure is not on master)
  • Fixture destination (relative to repo root): tests/test_vectors/fixtures/consensus
  • Test workdir (relative to repo root): . (repo root)
  • Test commands (run in order):
    1. cmake --preset default (configure)
    2. cmake --build build -j (build)
    3. ctest --test-dir build -R test_vectors_test --output-on-failure (run spec tests)

© leanEthereum, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/client-test of leanEthereum/leanSpec.

Open the folder on GitHubat commit 0b7d33e

Compare with similar skills

Client Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Client Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Client Test this skillleanEthereum/leanSpec143—~594Automated safety check: PassMIT
Wagmi Feature Developmentwevm/wagmi6.8k—~3.8kAutomated safety check: PassMIT
Release Roundethereumjs/ethereumjs-monorepo2.8k—~2kAutomated safety check: PassNone
Update Est Fixturesethereumjs/ethereumjs-monorepo2.8k—~3.3kAutomated safety check: PassNone
Starknet JSstarknet-io/starknet.js1.3k—~1.2kAutomated safety check: PassMIT
Lean Reviewgeanlabs/gean177—~1.5kAutomated safety check: PassNone

Similar skills

  • Wagmi Feature Development

    wevm/wagmi

    Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.

    6.8k GitHub stars~3.8k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Release Round

    ethereumjs/ethereumjs-monorepo

    Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.

    2.8k GitHub stars~2k tokensUpdated 19 days ago
    DevelopmentAuto-check passed

  • Update Est Fixtures

    ethereumjs/ethereumjs-monorepo

    Updates EthereumJS execution-spec test fixtures from an ethereum/execution-specs release, then (after a human merge) points the monorepo submodule, updates VM npm scripts, reports a first test run…

    2.8k GitHub stars~3.3k tokensUpdated 19 days ago
    DevelopmentAuto-check passed

  • Starknet JS

    starknet-io/starknet.js

    A skill your agent uses when writing or debugging JavaScript/TypeScript that interacts with Starknet through the starknet.js SDK — building Call objects or calldata, encoding/decoding Cairo types…

    1.3k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Lean Review

    geanlabs/gean

    Review a branch or PR's diff against main and report opportunities to subtract — simplify, delete, and reduce the number of concepts a reader has to hold in their head.

    177 GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Mark Task Executed

    ethereum-optimism/superchain-ops

    Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR.

    100 GitHub stars~679 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from leanEthereum/leanSpec

All 9 skills in this repo

  • Audit

    leanEthereum/leanSpec

    Read-only, multi-agent audit of the leanSpec codebase. An agent skill from leanEthereum/leanSpec.

    143 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Review

    leanEthereum/leanSpec

    Quick-reference checklist for code review conventions in leanSpec

    143 GitHub stars~468 tokensUpdated 1 mo ago
    Auto-check passed

  • Spec Diff

    leanEthereum/leanSpec

    Show what changed in leanSpec between devnet versions or HEAD

    143 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Workflows

    leanEthereum/leanSpec

    Common developer workflows, commands, and troubleshooting for leanSpec

    143 GitHub stars~496 tokensUpdated 1 mo ago
    Auto-check passed

  • Doc

    leanEthereum/leanSpec

    Document code in this repository.

    143 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Fill

    leanEthereum/leanSpec

    Generate consensus layer test fixtures

    143 GitHub stars~202 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Client Test

What does Client Test do?

Run leanSpec fixtures against a client implementation. An agent skill from leanEthereum/leanSpec. Client Test is an agent skill from leanEthereum/leanSpec.

When should I use Client Test?

Client Test fits situations like: development work in your project.

How do I install Client Test in Claude Code?

Run `npx skills add leanEthereum/leanSpec --skill client-test -a claude-code`. Or copy the skill folder (.claude/skills/client-test in leanEthereum/leanSpec) into .claude/skills/client-test in your project. Claude Code loads it when a task matches its description.

How do I install Client Test in Codex?

Run `npx skills add leanEthereum/leanSpec --skill client-test -a codex`. Or copy the skill folder (.claude/skills/client-test in leanEthereum/leanSpec) into .agents/skills/client-test in your project. Codex loads it when a task matches its description.

Can I use Client Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add leanEthereum/leanSpec --skill client-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-test, .gemini/skills/client-test, .github/skills/client-test and .opencode/skills/client-test in your project.

What does Client Test need to run?

Going by SKILL.md and its folder, Client Test needs the command-line tools its instructions call (cmake, uv and cargo).

Does Client Test access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Client Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Client Test use?

Client Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Client Test use?

About 594 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Client Test?

Skills that share tags, products or a category with Client Test: Wagmi Feature Development (wevm/wagmi, 6.8k stars), Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars), Update Est Fixtures (ethereumjs/ethereumjs-monorepo, 2.8k stars) and Starknet JS (starknet-io/starknet.js, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Client Test?

leanEthereum (a GitHub organization) maintains it in leanEthereum/leanSpec, which has 143 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 2, 2026.

Source: leanEthereum/leanSpec on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.