Install any skill in seconds. Free to start, no credit card required.
Get Started Free →internet-court/fulfill-git-escrow
Fulfill a git escrow bounty by writing a solution or submitting an existing one.
Passed 12 of 21 test cases with the skill, and 3 of 21 without it.
and 12 more in the full report
11 fixed2 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
What are the exact parameter flags passed to the git-escrows CLI when calling the fulfillment submit subcommand for UID `escrow-7700`, repo `https://github.com/sol/repo.git`, and commit `c0mm1t`?
| Checked | Without skill | With skill |
|---|---|---|
| The command uses --escrow-uid escrow-7700. | Missed | Passed |
| The command uses --solution-repo https://github.com/sol/repo.git. | Missed | Passed |
| The command uses --solution-commit c0mm1t. | Missed | Passed |
The instructions your model reads when the skill loads.
You are helping the user fulfill a git escrow bounty. This means submitting code that passes a failing test suite to claim the escrowed token reward.
There are two modes:
--solution-repo is provided by the user.Determine the mode from the user's input:
--solution-repo, use Mode B.The escrow UID is always required.
Run git-escrows --help to verify the CLI is installed. If it fails, try npx git-escrows --help or bunx git-escrows --help. Use whichever works for all subsequent commands. If none work, tell the user to install with npm i -g git-escrows.
Check if a .env file exists in the current directory. If not, tell the user they need one and suggest running:
git-escrows new-client --privateKey "0x..." --network "sepolia"
Run git-escrows list --verbose --format json and find the escrow matching the provided UID. Confirm:
If no escrow UID was provided, ask the user for one. You can help them browse with git-escrows list --status open.
Clone or read the test repository to understand what the tests expect:
git clone <url> /tmp/escrow-tests-<uid> && cd /tmp/escrow-tests-<uid> && git checkout <commit>test cases passed, vs 3 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.