SkillAgentSearch skills...

fulfill-git-escrow

Fulfill a git escrow bounty by writing a solution or submitting an existing one

Install / Use

npx skills add internet-court/internet-court-skill --skill fulfill-git-escrow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of fulfill-git-escrow

fulfill-git-escrow scores 87/100 on our quality scale, 614th of 1,155 Content & Media skills we index.

Its SKILL.md is 4.5 KB long, well organised into 13 sections with 3 code examples: a solid amount of guidance for an agent.

With 7,124 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 21 days ago, so fulfill-git-escrow is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

fulfill-git-escrow compared with similar skills

All 4 of these similar skills score higher than fulfill-git-escrow; compare them before choosing.

SkillScoreStarsUpdatedFormat
fulfill-git-escrow (this skill)by internet-court877.1k21d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install fulfill-git-escrow?
Run npx skills add internet-court/internet-court-skill --skill fulfill-git-escrow. The install tabs above show the steps for each supported agent.
Which AI agents does fulfill-git-escrow work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is fulfill-git-escrow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is fulfill-git-escrow still maintained?
The repository was last updated 21 days ago, so fulfill-git-escrow is actively maintained.

name: fulfill-git-escrow description: 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). compatibility: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint. allowed-tools: Bash Read Write Edit 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: "\U0001F3AF"

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 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. Create/modify files to implement the code that will make the tests pass
  2. Follow the project structure the tests expect (e.g., if tests import from src/math.ts, create that file)
  3. Include any necessary config files (package.json, Cargo.toml, etc.)
  4. Ensure the test framework's dependencies are accounted for

A3: Commit and get repo details

  1. Stage and commit the solution: git add -A && git commit -m "solution for escrow <uid>"
  2. Get the commit hash: git rev-parse HEAD
  3. Get the remote URL: git remote get-url origin
    • If no remote exists, ask the user to push to a public git repo and provide the URL

A4: Submit the fulfillment

git-escrows fulfill \
  --escrow-uid "<uid>" \
  --solution-repo "<repo-url>" \
  --solution-commit "<commit-hash>"

Mode B: Submit Existing Solution

B1: Gather parameters

From the user's input, extract:

  • --solution-repo: The git repo URL with the solution
  • --solution-commit: The commit hash of the solution

If either is missing, ask the user.

B2: Submit the fulfillment

git-escrows fulfill \
  --escrow-uid "<uid>" \
  --solution-repo "<repo-url>" \
  --solution-commit "<commit-hash>"

Step 4: Report results (both modes)

After successful execution:

  • Report the Fulfillment UID prominently
  • Explain that the oracle will now automatically test the solution
  • Provide the collect command for after arbitration passes:
    git-escrows collect --escrow-uid <escrow-uid> --fulfillment-uid <fulfillment-uid>
    
  • Suggest checking status with: git-escrows list --verbose

If the command fails, help diagnose the issue (escrow already fulfilled, wrong network, key not registered, etc.). If the user's git key isn't registered, suggest git-escrows register-key.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryContent
Updated21d ago
Forks132

Languages

TypeScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
fulfill-git-escrow — Universal Skill: Install & Safety Check | SkillAgent