fulfill-git-escrow
Fulfill Git Escrow Bounties
Git escrow bounties require careful test review, git handling, and blockchain CLI submission. This skill guides validation, solution preparation, fulfillment submission, and follow-up status checks.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "fulfill-git-escrow" from https://skillstore.io/skills/internet-court-fulfill-git-escrow.md and its manifest at https://skillstore.io/api/skills/internet-court-fulfill-git-escrow/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "fulfill-git-escrow". Inspect an open escrow before I start solving it.
Expected outcome:
- A short escrow summary with status, reward, oracle, test source, and required next inputs.
- A clear warning if wallet configuration or network access is missing.
- A proposed next step before any transaction is submitted.
Using "fulfill-git-escrow". Submit my existing solution repository and commit.
Expected outcome:
- A confirmation summary for the escrow UID, repository, and commit.
- A fulfillment result that highlights the fulfillment UID when submission succeeds.
- Follow-up guidance for checking status and collecting after approval.
Using "fulfill-git-escrow". Help me fix a failed escrow fulfillment.
Expected outcome:
- A diagnosis of likely causes such as closed escrow, wrong network, inaccessible repository, or unregistered key.
- A prioritized list of checks to run before retrying.
- A concise explanation of what changed and what still needs user confirmation.
Security Audit
High RiskThe skill legitimately automates Git escrow fulfillment, but it invokes third-party CLI commands, handles a blockchain private key, and clones external repositories. Several scanner hits are Markdown or metadata false positives. Publication requires safeguards for credential handling, repository trust, broad staging, and financial actions.
Confirmed security concerns (4)
Capability review items (9)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (22)
๐ Network access (1)
๐ Filesystem access (1)
๐ Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/internet-court-fulfill-git-escrow/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/internet-court-fulfill-git-escrow?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/internet-court-fulfill-git-escrow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-fulfill-git-escrow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/internet-court-fulfill-git-escrow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
internet-court. (2026). fulfill-git-escrow security audit report (audit version 2) [Author version 1.0]. Skillstore. https://skillstore.io/skills/internet-court-fulfill-git-escrow/audits/2BibTeX citation
@techreport{internet-court-internet-court-fulfill-git-escrow-2026,
author = {internet-court},
title = {fulfill-git-escrow security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/internet-court-fulfill-git-escrow/audits/2},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "fulfill-git-escrow security audit report (audit version 2)"
version: "1.0"
type: report
authors:
- name: "internet-court"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/internet-court-fulfill-git-escrow/audits/2"
identifiers:
- type: other
value: "skillstore:internet-court-fulfill-git-escrow:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Solve a new escrow challenge
Implement code from test expectations and submit the resulting commit.
Submit an existing solution
Collect required repository and commit details, then submit them to an escrow.
Track fulfillment next steps
Report fulfillment identifiers and prepare status or collection follow-up.
Try These Prompts
Use fulfill-git-escrow to inspect escrow UID <uid>. Summarize its status, test repository, reward, oracle, and missing information before running any submission step.
Use fulfill-git-escrow in write mode for escrow UID <uid>. Review the test repository, identify expected files, and propose a solution plan before editing files.
Use fulfill-git-escrow with escrow UID <uid>, solution repository <repo>, and solution commit <commit>. Confirm the details with me before submitting.
Use fulfill-git-escrow to analyze this failed fulfillment for escrow UID <uid>. Check status, network assumptions, key registration, repository accessibility, and next remediation steps.
Best Practices
- Confirm escrow UID, network, repository URL, and commit hash before submission.
- Keep private keys outside chat and review environment file handling manually.
- Review git status and staged changes before committing or submitting a solution.
Avoid
- Submitting fulfill or collect actions without explicit user approval.
- Using broad git staging without checking which files will be committed.
- Trusting unknown test repositories or generated commands without review.
Frequently Asked Questions
What does this skill do?
Does it require a wallet private key?
Can it submit an existing solution?
Can it write a new solution?
Does it guarantee reward collection?
What should I review before using it?
Developer Details
Author
internet-courtLicense
MIT
Author version
v1.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Repository
https://github.com/internet-court/internet-court-skill/tree/main/vendored/arkhai/fulfill-git-escrowRef
3f6e026a3363e0954ede7bef0cfe88d4475de137
Maintenance freshness
7/22/2026
Usage
1 downloads ยท 0 views
File structure
๐ SKILL.md