CtrlK
BlogDocsLog inGet started
Tessl Logo

alkahest-user

Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./vendored/arkhai/alkahest-user/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

The body is highly actionable and well-structured with clean progressive disclosure, but its destructive on-chain workflows lack explicit validation/feedback-loop checkpoints, capping workflow clarity.

Suggestions

Add explicit pre-flight validation steps before irreversible actions (e.g., verify balances/allowances and the encoded demand before `escrow create --approve`).

Provide a validate→fix→retry feedback loop for at least one destructive flow (e.g., decode the demand with `arbiter decode-demand` to confirm before approving).

Add post-submission verification guidance (confirm the returned uid via `escrow get`) so failures surface before assets move.

DimensionReasoningScore

Conciseness

Mostly lean command-reference prose with copy-paste bash blocks and little padding; a few minor asides ("this is the escrow UID", frontrunning glosses) could be trimmed.

4 / 5

Actionability

Throughout, commands are concrete and copy-paste-ready with real flags and example outputs, covering the common cases (ERC20/721/native, fulfill, arbitrate, commit-reveal, payments).

5 / 5

Workflow Clarity

Buyer/Seller/Oracle workflows are clearly numbered and sequenced, but the destructive/batch on-chain operations (asset approval, escrow create, slash-bond) lack explicit validate→fix→retry feedback loops, which the rubric caps at 3.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview with three well-signaled, one-level-deep references (typescript-sdk.md, contracts.md, arbiters.md), all real files with no nesting, and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

62%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.

The description is specific and highly distinct, but it omits any explicit "Use when..." trigger guidance, which caps completeness and limits trigger-term quality.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user needs to create, fulfill, arbitrate, or reclaim Alkahest escrows via the CLI."

Replace the generic verb "Interact with" with concrete operations (create escrow, fulfill demands, arbitrate as oracle, reclaim expired escrows) to lift specificity to 5.

Include common synonyms/variations (escrow, trustless exchange, EAS attestation escrow) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the concrete domain ("Alkahest escrow contracts"), three specific roles ("buyer, seller, or oracle"), and the tool ("using the CLI"), but "Interact" is generic and stops short of enumerating the actual operations.

4 / 5

Completeness

The "what" is clear (interact with escrow contracts via CLI as the three roles) but there is no "when"/"Use when" clause at all, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ("escrow contracts", "buyer, seller, or oracle", "CLI") tied to a named protocol, but lacks common synonyms/variations and has no natural "Use when..." phrasing.

3 / 5

Distinctiveness Conflict Risk

Targets a distinct named protocol with named role triggers ("Alkahest escrow contracts", "buyer, seller, or oracle"), making conflict with other skills minimal.

5 / 5

Total

15

/

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.