# Validate GenVM Contracts Before Testing

GenLayer contract authors need fast feedback before tests reveal deeper failures. This skill guides agents to run GenVM lint, validate, schema, and typecheck workflows.

## Install

```bash
npx skillstore add internet-court/genvm-lint
```

## Metadata

- Status: approved
- Slug: internet-court-genvm-lint
- Skillstore revision: r1
- Version status: missing
- Tree hash: c658719e80de36b68db66a6a56b4b922ad0e60e3b15baf71a246c2badf95a255
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/genlayer/genvm-lint
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/internet-court-genvm-lint
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-genvm-lint/manifest

## Capabilities

- Runs the recommended GenVM check workflow before contract tests.
- Uses lint mode for fast AST safety checks on contract files.
- Uses validate mode to check SDK types, decorators, storage, and method signatures.
- Extracts contract ABI schema output when requested.
- Runs GenVM typecheck commands with Pyright-compatible options.
- Parses JSON output during iterative repair loops.

## Use Cases

- Check a new contract before tests: Run the combined GenVM lint and validation flow before executing project tests.
- Repair SDK compliance issues: Use linter feedback to fix decorators, storage fields, type names, and method signatures.
- Prepare contract interface data: Generate schema output and confirm typecheck results before sharing contract artifacts.

## Prompt Templates

### Lint my contract

```
Use genvm-lint to check my GenLayer contract file and explain any errors in plain language.
```

### Fix validation errors

```
Run the GenVM check workflow, identify each validation problem, update the contract, and rerun the check.
```

### Compare schema and typecheck results

```
Extract the contract schema, run typecheck, and summarize any interface or typing issues that remain.
```

### Automate a pre-test quality pass

```
Before running tests, lint every changed GenLayer contract, parse machine-readable results, fix failures, and provide a concise readiness report.
```

## Limitations

- Requires genvm-linter to be available in the project environment.
- Works on GenLayer intelligent contract files, not general Python projects.
- Does not replace project tests or manual security review.
- Download behavior depends on the upstream GenVM tooling and artifact sources.

## Best Practices

- Run the combined check command before project tests.
- Use machine-readable output when fixing several lint errors.
- Confirm schema and typecheck results before publishing contract artifacts.

## Anti Patterns

- Do not skip linting because tests passed earlier.
- Do not edit generated artifacts before fixing the source contract.
- Do not run artifact downloads in untrusted project environments without review.

## Security Audit

- Audited at: 2026-07-21T03:17:26.103\+00:00
- Summary: All 34 external-command findings are false positives caused by Markdown backticks and examples of fixed linter commands. The system-reconnaissance finding is also a false positive because it only describes contract storage validation. No prompt injection, credential access, data exfiltration, or malicious intent was found in the reviewed files.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 1
- Popularity score: 0