Request development funds from the LI.FI `lifinance/automate-wallet-dev-fees` PR-based wallet. Parses a natural-language request (amount, token, chain, optional recipient + justification), resolves chain-name → chainId via `config/networks.json` and recipient → address via `config/global.json` (defaulting to `deployerWallet`), opens a PR appending an entry to `transfers/requests.json`, and pings the current approvers in a PR comment.
SkillScore32Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/22/2026
What it changes
Passed 3 of 9 test cases with the skill, and 1 of 9 without it.
Without skill14%
With skill32%
Checks it passed that the model alone missed
States that TRON is not supported by the wallet infrastructure
Informs the user that jq must be installed to run the workflow
Reads allowed-actors from .github/workflows/process.yml via gh api
and 6 more in the full report
7 fixed0 passed either way12 still failing3 broke
Pass-rate lift
+18 pp
Tokens
+217%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/22/2026v17 of 22 cases passed with skill · 9 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Please request 10 USDC on Base for deployerWallet. We are currently in an empty folder.
What was checked, without and with the skill
Checked
Without skill
With skill
Checks for config/global.json and config/networks.json before creating a transfer entry
Missed
Passed
Instructs the user to change directory to the contracts repo if the config files are missing
Missed
Passed
case-10 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md286 linessingle file
Request Dev Funds
When to trigger
User says any of:
"request dev funds" / "request funds for the deployer" / "refill deployer"
"request 100 USDC on Base" / "I need 0.5 ETH on Arbitrum"
"top up the refund wallet" / "fund pauserWallet on Polygon"
"/request-dev-funds [free-form description]"
Any natural request that implies opening a PR against lifinance/automate-wallet-dev-fees
Skip when:
User is asking about an existing fund request (read intent — just gh pr view it).
User wants TRON, BTC, or SUI funding — those aren't supported by the wallet (see README). Tell them and stop.
Background
The funding wallet repo (lifinance/automate-wallet-dev-fees) is PR-driven:
A PR appends an entry to transfers/requests.json.
validate.yml posts a confirmation comment (chain/token/address sanity check).
process.yml runs the lifinance/automate-wallet action which executes the transfer.
If the PR author is in allowed-actors (read from process.yml at runtime) → executes immediately, no review needed.
Otherwise → waits for an allowed-actors user to approve the PR, then executes.
On success, the action commits the result + auto-merges (squash).
The wallet auto-bridges and auto-swaps via LI.FI, so the user can request any token on any supported chain even if the wallet only holds funds elsewhere.
Side effects and required permissions
This skill performs writes that are visible to the team and — once the PR is approved / auto-executed — produce irreversible on-chain transfers. Be explicit with the user about what will happen before doing it:
Local writes: clones lifinance/automate-wallet-dev-fees into /tmp, creates a branch, edits transfers/requests.json, commits.
Remote writes (require gh auth as a LI.FI member with push access to automate-wallet-dev-fees):
git push of the new branch.
gh pr create against main of the funding repo.
gh pr comment to ping approvers.
Remote reads (require gh auth as a LI.FI member): gh api …/contents/.github/workflows/process.yml to read the live allowed-actors list.