Genvm lint skills internet court internet court vendored genlayer genvm lint

Skill bg-szy/TOP-SKILLS/skills/marketplace/genvm-lint__skills-internet-court-internet-court-vendored-genlayer-genvm-lint

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill genvm-lint__skills-internet-court-internet-court-vendored-genlayer-genvm-lint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Validate GenLayer intelligent contracts with the GenVM linter.

SKILL.md

2.7 KB, 707 tokens by cl100k_base, as published. Nobody here has run it

GenVM Lint

Validate intelligent contracts for safety, correctness, and SDK compliance.

Setup

Requires genvm-linter (included in requirements.txt for boilerplate projects):

pip install genvm-linter

Workflow

Always lint before testing. Run genvm-lint check after writing or modifying a contract. Fix all errors before running tests.

genvm-lint check contracts/my_contract.py

check runs both lint (AST safety) and validate (SDK semantics) in one pass.

Commands

check (recommended)

genvm-lint check contracts/my_contract.py
genvm-lint check contracts/my_contract.py --json  # Machine-readable output

lint (fast AST checks only, ~50ms)

genvm-lint lint contracts/my_contract.py

Catches:

Forbidden imports (os, sys, subprocess, random, etc.)
Non-deterministic patterns (bare float usage)
Contract header structure issues

validate (SDK semantic checks, ~200ms)

genvm-lint validate contracts/my_contract.py

Validates:

Types exist in SDK (TreeMap, DynArray, Address, etc.)
Decorators correctly applied (@gl.public.view, @gl.public.write)
Storage fields have valid types (no dict/list)
Method signatures correct

schema (extract ABI)

genvm-lint schema contracts/my_contract.py
genvm-lint schema contracts/my_contract.py --json
genvm-lint schema contracts/my_contract.py --output abi.json

typecheck (Pyright/Pylance)

genvm-lint typecheck contracts/my_contract.py
genvm-lint typecheck contracts/my_contract.py --json
genvm-lint typecheck contracts/my_contract.py --strict

Runs Pyright with SDK paths auto-configured. Catches type mismatches, missing attributes, undefined variables.

download (pre-download GenVM artifacts)

genvm-lint download                    # Latest
genvm-lint download --version v0.2.12  # Specific
genvm-lint download --list             # Show cached

Output Formats

Human (default)

✓ Lint passed (3 checks)
✓ Validation passed
  Contract: MyContract
  Methods: 8 (5 view, 3 write)

JSON (`--json`)

{"ok":true,"lint":{"ok":true,"passed":3},"validate":{"ok":true,"contract":"MyContract","methods":8,"view_methods":5,"write_methods":3,"ctor_params":2}}

Exit Codes

0 — All checks passed
1 — Lint or validation errors found
2 — Contract file not found
3 — SDK download failed

Agent Workflow

When fixing lint errors iteratively:

Run genvm-lint check contract.py --json
Parse JSON for specific errors
Fix each error in the contract
Re-run check until "ok": true
Proceed to tests

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 707 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

Read the output and check the exit codein 54 of 1195, across 14 files
Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
Identify the verification command proving the claimin 51 of 1195, across 12 files
Run the full verification commandin 50 of 1195, across 11 files
Verify output confirms the claimin 49 of 1195, across 12 files
Check version control diff after agent delegationin 46 of 1195, across 6 files
State claim with evidencein 44 of 1195, across 4 files
Run the test suitein 33 of 1195, across 26 files
Keep state in memory by defaultin 27 of 1195, across 6 files
Make prototype runnable with one commandin 26 of 1195, across 5 files
Produce a verification reportin 25 of 1195, across 14 files
Detect the package manager from lockfilesin 24 of 1195, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.