make-git-escrow

Create a new git escrow bounty for a test suite. Use when the user wants to submit a challenge with escrowed token rewards for passing a failing test suite. Requires the git-escrows CLI (npm i -g git-escrows).

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./vendored/arkhai/make-git-escrow/SKILL.md

Quality

Content

76%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 reasonably concise, with concrete executable commands and a clear step sequence. Its main gap is the lack of an explicit confirmation/validation checkpoint before the irreversible token-escrow submission, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint in Step 4: assemble the final `git-escrows submit` command, display all parameters to the user, and require confirmation before executing, since submission locks tokens irreversibly.

Add a preflight check that the configured account has sufficient token balance and the required ERC20 approval before running `submit`, so balance/approval failures surface before the attempt.

Tighten the opening paragraph and the wei-conversion aside in Step 3 to reduce tokens, pushing conciseness toward fully lean.

Dimension	Reasoning	Score
Conciseness	Lean step-by-step guidance with concrete commands and little padding; only minor instances (the intro restatement, the wei-conversion aside) could be trimmed, so efficient but not maximally lean.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (`git-escrows --help`, `new-client`, the complete `submit` template with all flags, `fulfill`, `list --status open`) covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence with prerequisite checks (CLI availability, .env) exists, but the `submit` step locks ERC20 tokens irreversibly without an explicit confirm-all-parameters checkpoint, and the rubric caps destructive/financial operations lacking validation at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single self-contained SKILL.md is well-organized into five headed steps with no nested references, but at ~70 lines it sits just over the simple-skill threshold that would allow a 5.	4 / 5
	Total	16 / 20 Passed

Description

82%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 clearly and explicitly states both what the skill does and when to use it, with concrete trigger phrasing for a well-defined niche. It is slightly light on the breadth of concrete actions listed, which keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	Names the domain plus one concrete action ('Create a new git escrow bounty for a test suite'), restated as 'submit a challenge with escrowed token rewards' rather than listing several distinct actions, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly answers both 'what' ('Create a new git escrow bounty for a test suite') and 'when' with a concrete trigger clause ('Use when the user wants to submit a challenge with escrowed token rewards for passing a failing test suite').	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('escrow bounty', 'token rewards', 'failing test suite', 'challenge') with good coverage; a few synonyms like bounty/prize/incentive are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (git escrow bounties for failing test suites) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: internet-court/internet-court-skill
Path: vendored/arkhai/make-git-escrow/SKILL.md
Commit: fa89195

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.