fulfill-git-escrow

Fulfill a git escrow bounty by writing a solution or submitting an existing one. Use when the user wants to solve a test suite challenge, write code to pass tests, and claim a token reward. Requires the git-escrows CLI (npm i -g git-escrows).

Quality

81%

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

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.

A highly actionable, well-structured workflow with copy-paste commands and clear sequencing. The main gap is the missing local test-validation checkpoint before submitting to the escrow oracle, which weakens workflow clarity for a financially consequential operation.

Suggestions

Add a validation step in Mode A between A2 and A3 to run the test suite locally and confirm it passes before committing and submitting (e.g., 'Run the tests in the cloned repo against your solution; only proceed when they pass').

Insert an explicit feedback loop earlier than Step 4 — if local tests fail, iterate on the solution before committing rather than relying on post-submission oracle failure.

Consider a brief pre-submit checklist (escrow open, tests green, commit pushed, remote URL set) to make the validation checkpoints scannable.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven, assuming Claude's competence; only minor instances of restating context ('This means submitting code that passes a failing test suite...') that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (git-escrows list/fulfill/collect, git clone/commit/rev-parse) covering the common Mode A and Mode B cases with complete flags.	5 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1-4, A1-A4, B1-B2) with some checkpoints (CLI, .env, escrow-open validation), but the critical verification of running tests locally before submitting a financial claim is absent, and the feedback loop only appears at the end after failure.	3 / 5
Progressive Disclosure	Single-file skill with no bundle files present; content is well-organized under clear section headers (Steps, Mode A, Mode B) and appropriately kept inline since no external references are needed, with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

87%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 description that clearly answers both what the skill does and when to use it, with concrete actions and a distinct, low-conflict niche. Trigger-term coverage is good but could include a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'writing a solution or submitting an existing one', 'write code to pass tests', 'claim a token reward' — with only minor gaps (no mention of oracle testing or the collect step).	4 / 5
Completeness	Explicitly states both what ('Fulfill a git escrow bounty by writing a solution or submitting an existing one') and when ('Use when the user wants to solve a test suite challenge...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ('solve a test suite challenge', 'write code to pass tests', 'claim a token reward', 'git escrow bounty') with a few synonyms, though it lacks the broader variation a 5 would require.	4 / 5
Distinctiveness Conflict Risk	The 'git escrow bounty' / 'token reward' niche is highly specific with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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/fulfill-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.