make-git-escrow
/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).
- Author
- internet-court ↗
- Repository
- internet-court-skill ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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).
Original author description
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).
How it works
- Step 1: Check CLI availability
- Step 2: Check .env configuration
- Step 3: Gather parameters
- Step 4: Execute
- Step 5: Report results
SKILL.md preview
---
name: make-git-escrow
description: 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).
compatibility: Requires git-escrows CLI, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.
allowed-tools: Bash Read Glob Grep
metadata:
author: arkhai-io
version: "1.0"
openclaw:
requires:
bins:
- git-escrows
- git
config:
- .env
primaryEnv: PRIVATE_KEY
homepage: https://github.com/arkhai-io/git-commit-trading
emoji: "\U0001F512"
---
# Make Git Escrow
You are automating the creation of a git escrow bounty via the `git-escrows submit` CLI command. This locks ERC20 tokens in escrow as a bounty for someone who can make a failing test suite pass.
## 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"
```
Verify it contains at least `PRIVATE_KEY` and `NETWORK` (or defaults to anvil). For base-sepolia and sepolia networks, contract addresses are auto-configured.
## Step 3: Gather parameters
You need all of these to run the submit command:
1. **`--tests-repo`** (required): Git repository URL containing the failing test suite.
- If the user provided a URL as an argument, use that.
- Otherwise, check if the current directory is a git repo and offer to use its remote URL.
- Ask the user if neither is available.
2. **`--tests-commit`** (required): The commit hash of the test suite.
- If using the current repo, detect HEAD with `git rev-parse HEAD`.
- Otherwise ask the user.
3. **`--reward`** (required): Amount of tokens to escrow, in wei.
- Ask the user. Help them convert if they give a human-readable amount (e.g., "1 USDC" = "1000000" for 6-decimal tokens, "1 ETH worth" = "1000000000000000000" for 18-decimal tokens).
4. **`--oracle`** (required): The Ethereum address of the oracle that will arbitrate.
- Ask the user. Mention the public demo oracle on Sepolia: `0xc5c132B69f57dAAAb75d9ebA86cab504b272Ccbc`.
5. **`--arbiter`** (required): The arbiter contract address.
- Ask the user. This is typically the TrustedOracleArbiter contract on their network.
6. **`--token`** (required): The ERC20 token contract address for the reward.
- Ask the user.
Ask for any missing parameters, grouping related questions together when possible to minimize back-and-forth.
## Step 4: Execute
Run the submit command with all gathered parameters:
```
git-escrows submit \
--tests-repo "<repo-url>" \
--tests-commit "<commit-hash>" \
--reward "<amount>" \
--arbiter "<address>" \
--oracle "<address>" \
--token "<address>"
```
## Step 5: Report results
After successful execution:
- Report the **Escrow UID** prominently
- Show the full escrow details (attester, recipient, schema, reward, token, oracle)
- Provide the fulfill command that a solver would use:
```
git-escrows fulfill --escrow-uid <UID> --solution-repo "<url>" --solution-commit "<hash>"
```
- Mention they can track status with: `git-escrows list --status open`
If the command fails, help diagnose the issue (insufficient balance, wrong network, missing approval, etc.).
Files in this package (2)
- LICENSE 1 KB
- SKILL.md 4 KB
Versions
The database has no other skills named make-git-escrow.
Database snapshot: 13.11.2026 · package version 127bb4717225 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fulfill-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). - 100xrpl-smart-escrows
Build, test, and debug XRPL Smart Escrow contracts written in Rust against xrpl-wasm-stdlib (crates xrpl-common-stdlib, xrpl-escrow-stdlib, xrpl-macros), compiled to wasm32v1-none. Use when the user wants to write a smart escrow / EscrowFinish WASM contract, asks about the XRPL… - 100test-fixing
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken"), or completes implementation and wants tests passing. - 100test-fixing
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\"fix these tests\", \"make tests pass\"), reports test failures (\"tests are failing\", \"test suite is broken\"), or completes implementation and wants tests passing. - 100test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass. - 100test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.