Agent skill · Testing & QA

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).

Internet Court1,389★ · +222/wk · 1 repos on radarProfile →
claude-codecodexcan modify filesNOASSERTION
Install
npx skills add internet-court/internet-court-skill --skill fulfill-git-escrow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.0
Declared author: arkhai-io
Allowed tools: BashReadWriteEditGlobGrep
Requires: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.
Path: vendored/arkhai/fulfill-git-escrow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,536 · +147 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: ``` git-escrows new-client --privateKey "0x..." --network "sepolia" ``` ## Step 3: Validate the escrow Run `git-escrows list --verbose --format json` an

What's inside
Steps it walks through
  1. Step 1: Check CLI availability
  2. Step 2: Check .env configuration
  3. Step 3: Validate the escrow
  4. Mode A: Write Solution + Submit
  5. A1: Understand the tests
  6. A2: Write the solution
  7. A3: Commit and get repo details
  8. A4: Submit the fulfillment
  9. Mode B: Submit Existing Solution
  10. B1: Gather parameters
  11. B2: Submit the fulfillment
  12. Step 4: Report results (both modes)
Ships with 1 file
  • LICENSE
More from internet-court-skill
All skills →
About this skill
What does the fulfill-git-escrow skill do?

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).

How do I install it?

Run `npx skills add internet-court/internet-court-skill --skill fulfill-git-escrow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From internet-court/internet-court-skill, a repository with 1,536 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going