Agent skill · software engineering · aiskillstore
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).
Why this skill is useful
Adds specific commands and workflows for fulfilling git escrow bounties that the AI wouldn't reliably generate on its own.
What it needs
Requires git, git-escrows installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Fulfill Git Escrow 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: Mode A (Write + Submit): You write the solution code, commit it, and submit. This is the default when no --solution-repo is provided by the user. Mode B (Submit Existing): The user already has a solution repo and commit. You just submit the fulfillment. Determine the mode from the user's input: If they provide --solution-repo, use Mode B. Otherwise, use Mode A. The escrow UID is always required. Step 1: Check CLI availability 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. Step 2: Check .env configuration Check if a .env file exists in the current directory. If not, tell the user they need one and suggest running: Step 3: Validate the escrow Run git-escrows list --verbose --format json and find the escrow matching the provided UID. Confirm: The escrow exists and is open Note the test repo URL, test commit hash, reward amount, and oracle address If no escrow UID was provided, ask the user for one. You can help them browse with git-escrows list --status open. Mode A: Write Solution + Submit A1: Understand the tests Clone or read the test repository to understand what the tests expect: 1. Identify the test repo URL and commit from the escrow details 2. Clone it to a temporary location: git clone <url> /tmp/escrow-tests-<uid> && cd /tmp/escrow-tests-<uid> && git checkout <commit> 3. Read the test files to understand: What functions/modules/APIs the tests import What behavior they assert What test framework is used The project structure expected A2: Write the solution In the current working directory (or a subdirectory the user specifies): 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/fulfill-git-escrow