Agent skill · product strategy · aiskillstore
genlayer-intelligent-contracts
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Why this skill is useful
Defines specific performance review rubrics and evidence schemas for GenLayer Intelligent Contracts that the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
GenLayer Intelligent Contracts Use this adapter when GenLayer is the judgment layer for agent behavior. It should define what the supervisor contract must review and emit: the user's mandate, the agent's action log, transaction receipts, rationales, artifacts, outputs, and the decision about whether authority should continue, be warned, be constrained, or be revoked. This skill is not the Intelligent Oracle skill. Intelligent Oracle is for binary public web evidence markets. Use this skill for open-ended review of performance, relevance, quality, safety, and mandate compliance. This skill is also not the GenLayer deployment skill. For writing, deploying, testing, and interacting with GenLayer Intelligent Contracts, use the official GenLayer skills at https://skills.genlayer.com/ or the GenLayer docs. If those skills are available in the environment, load them for implementation. If not, tell the user to install/enable them and keep this skill focused on Internet Court interfaces. Core Model GenLayer can judge qualitative criteria. It does not automatically revoke an EVM delegation unless the system includes a concrete cross-chain message, relayer, controller, or account module that consumes the GenLayer decision. Workflow 1. Extract the review target: Objective, allowed authority, prohibited behavior, expected outputs, review cadence, evidence sources, and revocation triggers. 2. Draft a rubric: Include relevance, mandate compliance, transaction safety, budget discipline, artifact quality, evidence completeness, and user-value criteria. 3. Define evidence schema: Use structured action receipts, transaction hashes, deployed addresses, agent rationales, output artifacts, costs, and prior warnings. 4. Define decisions: continue, warn, constrain, revoke, and optionally escalate. 5. Define effect path: For ERC-7710, load ../genlayer-erc7710-connector/SKILL.md to specify how a revoke or constrain decision reaches the EVM revocation controller or delegation manager. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/genlayer-intelligent-contracts