- Home
- Skills
- Productivity
- bounty claim gate
Works with the AI Agents you already use
bounty claim gate
A six-gate pre-flight checklist to verify if a bounty, grant, or paid task will actually pay before you start work.
$14.99
bounty claim gate
Example session with this skill installed
**Evaluate this bounty:** $500 USDC on Polygon for a React component. 10 claimants already, no escrow address listed, poster has 0 past payouts. Criteria: "Make it look professional."
- Read your context and instructions
- Compiled the bounty claim gate
I have evaluated the bounty listing for the React component. The evaluation resulted in a NO-GO due to multiple high-risk failures in the primary gates. ## Bounty Gate Report: React Component ($500 USDC) | Gate | Status | Evidence / Analysis | | :--- | :--- | :--- | | **1. Escrow** | **FAIL** | No escrow address provided. Reward is a promise ("we pay on delivery"), not a secured asset. | | **2. Rail** | **PASS** | USDC on Polygon is a standard rail. Receipt is highly likely if payment is actually triggered. | | **3. Criteria** | **FAIL** | "Make it look professional" is entirely subjective. Reviewer can move the goalposts or reject for any reason. | | **4. History** | **FAIL** | Poster has 0 past payouts. No verifiable transaction history or public records of successful rewards. | | **5. Math** | **POOR** | 10 claimants for 1 prize. Win probability < 10%. Expected value is < $50 before factoring in labor. | | **6. Effort** | **N/A** | Risk profile is too high to justify any significant time investment. | **Final Recommendation: NO-GO** This listing hits three major red flags: no escrow, new poster, and subjective criteria. The combination suggests a high probability of non-payment or a "lottery" outcome where the work is harvested without compensation. **Next steps** - Search for an alternative bounty with on-chain escrow verified via block explorer. - If you still wish to proceed, ask the poster for a specific technical spec to move Gate 3 to a PASS. - Request the poster to fund an escrow contract before you submit a pull request.
Connects securely to your tools. The creator never sees your data.
About this skill
Most bounty work that never pays was predictable at the time of the claim. This skill provides a rigorous pre-flight checklist for developers and agents to evaluate bounties, grants, or paid tasks before investing any effort. It filters out listings where rewards aren't escrowed, payout rails are inaccessible, or acceptance criteria are too subjective to be reliable. ## What it does - **Verify Escrow** checks for on-chain funds or platform-held rewards to ensure the money exists. - **Audit Payout Rails** confirms the specific payment method, chain, or processor actually reaches your region and wallet. - **Analyze Criteria** identifies subjective "lottery" traps versus objective, testable requirements like merged PRs or passing tests. - **Check Poster History** searches for verifiable payout records and transaction hashes instead of platform marketing badges. - **Calculate Expected Value** models win probability against competition volume and potential duplicate-work traps. ## How it works 1. **Input Bounty Data** by providing the listing URL, description, and reward details. 2. **Execute Gate Sequence** by running the six gates in order, starting with the cheapest checks like escrow and rails. 3. **Identify Red Flags** like missing escrow, new posters, or move-able acceptance criteria. 4. **Review Gate Report** to see a pass/fail status for each gate with specific evidence. ## Frameworks & tools This skill is platform-agnostic and works with Gitcoin, Bountycaster, Replit Bounties, GitHub Issues, and various grant programs. It utilizes block explorers for escrow verification and processor availability documentation for rail checks. ## Why this beats prompting it yourself Generic prompts often overlook the "payout rail" trap where you do the work but cannot legally receive the funds. This skill enforces a "cheapest-check-first" logic that kills bad leads in seconds before you waste time analyzing complex technical requirements. ## Use cases - **Evaluating a new bounty** to decide if the reward justifies the timebox. - **Comparing multiple listings** to rank them by expected value per hour. - **Diagnosing payment failures** to see if a reward is still recoverable. - **Setting effort caps** to define the exact point where you abandon a task. ## Known limitations Cannot guarantee payment if a platform experiences a technical outage or if off-chain escrow is fraudulent. win probability estimates are based on visible competition and historical data.
Cannot guarantee payment if platforms fail or off-chain escrow is fraudulent. Win probability is an estimate based on visible competition and public history only.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
Fetches public bounty/job pages, platform documentation, and block explorers to verify escrow state and payout records, and reads the local files it is auditing (bounty text, criteria, drafts). Terminal is used for read-only on-chain checks and API calls. No writes anywhere; never claims, deposits, or submits anything on the user's behalf.