[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77GD0XYTHAEJ3Z2E5GB7SY8":3,"skill-same:01M77GD0XYTHAEJ3Z2E5GB7SY8":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M77GD0XYTHAEJ3Z2E5GB7SY8","fulfill-git-escrow",null,"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).","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Ff\u002Ffulfill-git-escrow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fulfill-git-escrow\ndescription: 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).\ncompatibility: Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.\nallowed-tools: Bash Read Write Edit Glob Grep\nmetadata:\n  author: arkhai-io\n  version: \"1.0\"\n  openclaw:\n    requires:\n      bins:\n        - git-escrows\n        - git\n      config:\n        - .env\n    primaryEnv: PRIVATE_KEY\n    homepage: https:\u002F\u002Fgithub.com\u002Farkhai-io\u002Fgit-commit-trading\n    emoji: \"\\U0001F3AF\"\n---\n\n# Fulfill Git Escrow\n\nYou 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.\n\nThere are two modes:\n- **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.\n- **Mode B (Submit Existing)**: The user already has a solution repo and commit. You just submit the fulfillment.\n\nDetermine the mode from the user's input:\n- If they provide `--solution-repo`, use **Mode B**.\n- Otherwise, use **Mode A**.\n\nThe escrow UID is always required.\n\n## Step 1: Check CLI availability\n\nRun `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`.\n\n## Step 2: Check .env configuration\n\nCheck if a `.env` file exists in the current directory. If not, tell the user they need one and suggest running:\n```\ngit-escrows new-client --privateKey \"0x...\" --network \"sepolia\"\n```\n\n## Step 3: Validate the escrow\n\nRun `git-escrows list --verbose --format json` and find the escrow matching the provided UID. Confirm:\n- The escrow exists and is **open**\n- Note the test repo URL, test commit hash, reward amount, and oracle address\n\nIf no escrow UID was provided, ask the user for one. You can help them browse with `git-escrows list --status open`.\n\n## Mode A: Write Solution + Submit\n\n### A1: Understand the tests\n\nClone or read the test repository to understand what the tests expect:\n1. Identify the test repo URL and commit from the escrow details\n2. Clone it to a temporary location: `git clone \u003Curl> \u002Ftmp\u002Fescrow-tests-\u003Cuid> && cd \u002Ftmp\u002Fescrow-tests-\u003Cuid> && git checkout \u003Ccommit>`\n3. Read the test files to understand:\n   - What functions\u002Fmodules\u002FAPIs the tests import\n   - What behavior they assert\n   - What test framework is used\n   - The project structure expected\n\n### A2: Write the solution\n\nIn the **current working directory** (or a subdirectory the user specifies):\n1. Create\u002Fmodify files to implement the code that will make the tests pass\n2. Follow the project structure the tests expect (e.g., if tests import from `src\u002Fmath.ts`, create that file)\n3. Include any necessary config files (package.json, Cargo.toml, etc.)\n4. Ensure the test framework's dependencies are accounted for\n\n### A3: Commit and get repo details\n\n1. Stage and commit the solution: `git add -A && git commit -m \"solution for escrow \u003Cuid>\"`\n2. Get the commit hash: `git rev-parse HEAD`\n3. Get the remote URL: `git remote get-url origin`\n   - If no remote exists, ask the user to push to a public git repo and provide the URL\n\n### A4: Submit the fulfillment\n\n```\ngit-escrows fulfill \\\n  --escrow-uid \"\u003Cuid>\" \\\n  --solution-repo \"\u003Crepo-url>\" \\\n  --solution-commit \"\u003Ccommit-hash>\"\n```\n\n## Mode B: Submit Existing Solution\n\n### B1: Gather parameters\n\nFrom the user's input, extract:\n- `--solution-repo`: The git repo URL with the solution\n- `--solution-commit`: The commit hash of the solution\n\nIf either is missing, ask the user.\n\n### B2: Submit the fulfillment\n\n```\ngit-escrows fulfill \\\n  --escrow-uid \"\u003Cuid>\" \\\n  --solution-repo \"\u003Crepo-url>\" \\\n  --solution-commit \"\u003Ccommit-hash>\"\n```\n\n## Step 4: Report results (both modes)\n\nAfter successful execution:\n- Report the **Fulfillment UID** prominently\n- Explain that the oracle will now automatically test the solution\n- Provide the collect command for after arbitration passes:\n  ```\n  git-escrows collect --escrow-uid \u003Cescrow-uid> --fulfillment-uid \u003Cfulfillment-uid>\n  ```\n- Suggest checking status with: `git-escrows list --verbose`\n\nIf 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`.\n","# Fulfill Git Escrow\n\nYou 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.\n\nThere are two modes:\n- **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.\n- **Mode B (Submit Existing)**: The user already has a solution repo and commit. You just submit the fulfillment.\n\nDetermine the mode from the user's input:\n- If they provide `--solution-repo`, use **Mode B**.\n- Otherwise, use **Mode A**.\n\nThe escrow UID is always required.\n\n## Step 1: Check CLI availability\n\nRun `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`.\n\n## Step 2: Check .env configuration\n\nCheck if a `.env` file exists in the current directory. If not, tell the user they need one and suggest running:\n```\ngit-escrows new-client --privateKey \"0x...\" --network \"sepolia\"\n```\n\n## Step 3: Validate the escrow\n\nRun `git-escrows list --verbose --format json` and find the escrow matching the provided UID. Confirm:\n- The escrow exists and is **open**\n- Note the test repo URL, test commit hash, reward amount, and oracle address\n\nIf no escrow UID was provided, ask the user for one. You can help them browse with `git-escrows list --status open`.\n\n## Mode A: Write Solution + Submit\n\n### A1: Understand the tests\n\nClone or read the test repository to understand what the tests expect:\n1. Identify the test repo URL and commit from the escrow details\n2. Clone it to a temporary location: `git clone \u003Curl> \u002Ftmp\u002Fescrow-tests-\u003Cuid> && cd \u002Ftmp\u002Fescrow-tests-\u003Cuid> && git checkout \u003Ccommit>`\n3. Read the test files to understand:\n   - What functions\u002Fmodules\u002FAPIs the tests import\n   - What behavior they assert\n   - What test framework is used\n   - The project structure expected\n\n### A2: Write the solution\n\nIn the **current working directory** (or a subdirectory the user specifies):\n1. Create\u002Fmodify files to implement the code that will make the tests pass\n2. Follow the project structure the tests expect (e.g., if tests import from `src\u002Fmath.ts`, create that file)\n3. Include any necessary config files (package.json, Cargo.toml, etc.)\n4. Ensure the test framework's dependencies are accounted for\n\n### A3: Commit and get repo details\n\n1. Stage and commit the solution: `git add -A && git commit -m \"solution for escrow \u003Cuid>\"`\n2. Get the commit hash: `git rev-parse HEAD`\n3. Get the remote URL: `git remote get-url origin`\n   - If no remote exists, ask the user to push to a public git repo and provide the URL\n\n### A4: Submit the fulfillment\n\n```\ngit-escrows fulfill \\\n  --escrow-uid \"\u003Cuid>\" \\\n  --solution-repo \"\u003Crepo-url>\" \\\n  --solution-commit \"\u003Ccommit-hash>\"\n```\n\n## Mode B: Submit Existing Solution\n\n### B1: Gather parameters\n\nFrom the user's input, extract:\n- `--solution-repo`: The git repo URL with the solution\n- `--solution-commit`: The commit hash of the solution\n\nIf either is missing, ask the user.\n\n### B2: Submit the fulfillment\n\n```\ngit-escrows fulfill \\\n  --escrow-uid \"\u003Cuid>\" \\\n  --solution-repo \"\u003Crepo-url>\" \\\n  --solution-commit \"\u003Ccommit-hash>\"\n```\n\n## Step 4: Report results (both modes)\n\nAfter successful execution:\n- Report the **Fulfillment UID** prominently\n- Explain that the oracle will now automatically test the solution\n- Provide the collect command for after arbitration passes:\n  ```\n  git-escrows collect --escrow-uid \u003Cescrow-uid> --fulfillment-uid \u003Cfulfillment-uid>\n  ```\n- Suggest checking status with: `git-escrows list --verbose`\n\nIf 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`.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":37,"compatibility":38},{"author":25,"version":26,"openclaw":27},"arkhai-io","1.0",{"emoji":28,"homepage":29,"requires":30,"primaryEnv":36},"🎯","https:\u002F\u002Fgithub.com\u002Farkhai-io\u002Fgit-commit-trading",{"bins":31,"config":34},[32,33],"git-escrows","git",[35],".env","PRIVATE_KEY","Bash Read Write Edit Glob Grep","Requires git-escrows CLI, git, a configured .env with PRIVATE_KEY, and network access to an Ethereum RPC endpoint.","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Ff\u002Ffulfill-git-escrow",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill fulfill-git-escrow",{"tool":54,"command":55},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill fulfill-git-escrow",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill fulfill-git-escrow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Ff\u002Ffulfill-git-escrow\u002FSKILL.md",true,[],[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]