CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable design spec with strong workflow and validation scaffolding, but it is interface-level only and duplicates reference-eligible detail inline. Tightening the overlap with the reference and offering at least one complete runnable artifact would raise the weaker dimensions.

Suggestions

Move the full GenLayerDelegationDecision/RelayEnvelope schemas and the detailed Studio Bridge flow into references/connector-patterns.md and replace them in the body with a one-line pointer, reducing duplication and token cost.

Add at least one complete, deployable artifact (e.g. a minimal RevocationController.sol implementation or a runnable relayer script) in a scripts/ bundle so the guidance is executable end-to-end, not just interface skeletons.

Trim the connector-mode prose in the body to a brief comparison table and defer the per-mode flows/tests to the reference, keeping the body as an overview that signals detail one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation fluff, but the ~200-line body duplicates the connector-mode material already present in references/connector-patterns.md and embeds full schemas/interfaces that could be trimmed.

2 / 3

Actionability

Provides concrete, copy-paste-ready TS types and a Solidity interface plus specific chain ids and contract names, but stops at interface skeletons with no runnable end-to-end contract or relayer implementation.

2 / 3

Workflow Clarity

A clear 7-step Workflow is reinforced by an 8-item Output Checklist, explicit Failure Cases with mitigations, and a defined Tests list serving as validation checkpoints for the risky revocation path.

3 / 3

Progressive Disclosure

The single one-level-deep reference is clearly signaled and exists, but the body inlines detailed schemas, interfaces, and bridge flows that overlap the reference file rather than pointing out to it.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete, and clearly niche-scoped in third-person voice. It is a strong model description with no notable gaps.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling" — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ("Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority") and when ("Use when an agent needs to design...").

3 / 3

Trigger Term Quality

Uses the natural domain terms a practitioner would say ("GenLayer Intelligent Contract", "ERC-7710", "revocation controller", "relayer/bridge") with a clear "Use when an agent needs to design..." trigger.

3 / 3

Distinctiveness Conflict Risk

The GenLayer-to-ERC-7710 connector niche is highly specific with distinct triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
internet-court/internet-court-skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.