Agent skill · software engineering · aiskillstore
genlayer-erc7710-connector
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Why this skill is useful
Adds a detailed connector specification and executable workflows for integrating GenLayer decisions with ERC-7710, which are not commonly found in public documentation.
What it needs
Requires genlayer-cli installed locally. Requires genlayer account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
GenLayer ERC-7710 Connector Use this skill after the mandate, ERC-7710 policy, and GenLayer Intelligent Contract review flow exist. This skill does not teach GenLayer contract deployment. For GenLayer build, deploy, test, and CLI operations, use the official GenLayer skills at https://skills.genlayer.com/ or the GenLayer documentation. This skill specifies the connector: Design Rule Never say "GenLayer cancels ERC-7710" without defining the effect path. GenLayer produces a decision. An EVM-side controller, account module, caveat enforcer, or delegation manager integration must consume that decision. Workflow 1. Identify the permission: mandateId, permissionHash, delegator, delegate, delegation manager, target EVM chain, and current policy. 2. Identify the GenLayer decision source: supervisor contract address, method that stores/returns the decision, review window, decision enum, score, issued timestamp, and finalized transaction id. 3. Choose the connector mode: Manual demo relay, trusted relayer, GenLayer Studio bridge relay, optimistic relay with challenge window, light-client/bridge verification, or direct EVM call if supported by the target GenLayer/EVM integration. 4. Define the message: Include enough data for the EVM controller to revoke or constrain exactly one mandate/permission. 5. Define the EVM effect: Revoke, constrain, pause, require human approval, or mark pending appeal. 6. Define safety: Finality assumptions, replay protection, nonce, deadline, idempotency, emergency owner revoke, and absolute permission expiry. 7. Define tests: Continue does nothing, revoke blocks future redemption, constrain tightens policy, stale decisions fail, duplicate messages are idempotent, forged decisions fail. Connector Modes Use the simplest mode that honestly matches the demo. Manual Demo Relay Best for hackathon/prototype demos. The UI or operator reads the GenLayer decision and calls the EVM revocation controller. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/genlayer-erc7710-connector