CtrlK
BlogDocsLog inGet started
Tessl Logo

nla-arbitrate

Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle. Use when the user wants to review pending arbitration requests, evaluate demands against fulfillments, and submit on-chain decisions. Supports both interactive and LLM-auto modes.

72

Quality

87%

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

82%Weight 40%Scale 1-5

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

A well-structured, highly actionable CLI skill with a clear workflow and verification step. The main gaps are minor redundancy around API-key configuration and the absence of an explicit error-recovery loop for irreversible on-chain/batch decisions.

Suggestions

Consolidate LLM API-key setup into one place (e.g., Prerequisites) and reference it once from step 3 and Key details to remove the triple repetition.

Add a brief feedback loop after the step 4 status check (e.g., if a decision was rejected or skipped unexpectedly, re-run with the specific escrow UID) to satisfy the batch/destructive validation expectation.

Trim the 'Examples' section or fold it into step 2a/2b to avoid restating the same commands.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands and brief comments, but LLM API-key handling is repeated in step 3, 'Key details', and 'Prerequisites', and the 'Examples' section reiterates step 2a/2b commands.

4 / 5

Actionability

Fully executable, copy-paste-ready commands (nla wallet:show, escrow:arbitrate --escrow-uid <uid>, --auto, escrow:status) with worked examples covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence (verify oracle → arbitrate → review/decide → verify status) with a verification checkpoint, but no explicit error-recovery feedback loop for what is a batch/on-chain operation.

4 / 5

Progressive Disclosure

Single-file, single-purpose skill organized into clear sections (When to use, Steps, Key details, Prerequisites, Examples) with no nested references; slightly over 50 lines with minor duplication keeping it from a 5.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, third-person description that explicitly covers what the skill does and when to use it with concrete, domain-specific actions. Minor room for additional trigger synonyms, but it is specific and distinctive.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'review pending arbitration requests, evaluate demands against fulfillments, and submit on-chain decisions' — plus interactive/LLM-auto modes, covering the full arbitration flow comprehensively.

5 / 5

Completeness

Explicitly answers both what ('Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle') and when ('Use when the user wants to review pending arbitration requests...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural coverage with 'arbitrate', 'escrow fulfillments', 'review pending arbitration requests', and 'submit on-chain decisions', though a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (NLA escrow arbitration as the oracle) with distinct, domain-specific triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

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.