self-evolving-agent
Skill2 starsChanged 39 days agoApache-2.0View on GitHub
Use this skill when the user wants a bounded, read-only paid preflight before planning a budgeted economic agent. It runs a fixed three-call bundle - one broad crypto KOL sentiment report, Hyperliquid market data for one explicit asset ticker, and availability and price for one explicit domain candidate - then turns the results into a budget, expense, risk, and paper-trading plan. Before payment, require both inputs, free-verify every call, disclose the live total and the sum of per-step caps, and obtain explicit approval. It does not create inboxes or wallet identities, fund wallets, buy domains or compute, or place trades. Do not use it for a single price lookup, live trading, or account setup.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- martinsbash/claude-skillstheir own version, first seen Apr 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- martinsbash/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- account-intelSkill
- comprehensive-enrichmentSkill
- email-campaignSkill
- enrich-waterfallSkill
- financial-intelSkill
- find-twitter-influencersSkill
- gtm-enrichment-deepSkill
- gtm-enrichment-smartSkill
- lead-enrichmentSkill
- perplexity-searchSkill
- person-lookupSkill
- recent-funding-roundsSkill
- sales-prospectingSkill
- scrapecreatorsSkill
- social-intelSkill
- stock-direction-signalsSkill
- twitter-researchSkill
- vc-ai-infra-scoutSkill
- wallet-desk-briefSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Use this skill when the user wants to:
- Distinctive: line 23
check broad crypto social sentiment, market data for one Hyperliquid asset, and one domain candidate's availability and price in one paid …
- Distinctive: line 29
Do not use it to:
- Distinctive: line 31
create an email inbox, wallet login, or any other identity for an agent.
- Distinctive: line 33
place, modify, or close a trade, or run a live trading loop.
- Very specific: line 34
look up a single price (use a narrower skill or one selat-pay call).
- Distinctive: line 64
After approval and with a spendable Gateway balance, arm a session budget equal to the approved amount, run the bundle once, and disarm the …
- Distinctive: line 116
Fixed pipeline: Every run pays for all three calls.
- Very specific: line 121
The KOL report is broad: Do not imply that every narrative in it is about the requested asset.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
self-evolving-agent
A fixed three-call, read-only economic-agent preflight. It gathers the minimum paid context someone needs before deciding whether a budgeted agent is worth running. The agent then turns that context into a plan.
When To Use
Use this skill when the user wants to:
- check broad crypto social sentiment, market data for one Hyperliquid asset, and one domain candidate's availability and price in one paid run, before committing a budget to an agent; and
- turn those three results into a budget, expense, runway, risk, and paper-trading or monetization plan for an autonomous or semi-autonomous agent.
Do not use it to:
- create an email inbox, wallet login, or any other identity for an agent;
- fund a wallet or Gateway balance, or buy a domain, hosting, or compute;
- place, modify, or close a trade, or run a live trading loop;
- look up a single price (use a narrower skill or one
selat-paycall); or - give personalized financial advice or promise profits.
Workflow
Install the vetted recipe:
selat skill install self-evolving-agent- Collect both required inputs. There are no defaults:
asset: one Hyperliquid ticker such asBTCorETH;domainCandidate: one full domain on a TLD the provider supports, such asagent-alpha-research.com.
Probe every payment challenge for free:
selat skill verify ~/.config/selat/skills/self-evolving-agent \ --asset BTC \ --domainCandidate agent-alpha-research.com \ --live-probe- Show the three live quotes, their expected total, and the sum of the
per-step caps. Wait for explicit approval. The domain-check price depends on
the TLD: about
$0.0105for.com,.net,.org,.coand similar, and$0.0525for.ai,.io,.xyz,.devand similar. After approval and with a spendable Gateway balance, arm a session budget equal to the approved amount, run the bundle once, and disarm the budget:
selat budget start --amount <approved-amount> selat skill run self-evolving-agent --asset <ticker> --domainCandidate <domain> selat budget stopselat skill runexecutes and pays for all three calls, in order, on every run. The session budget is a selat-pay spending tripwire. It does not select or skip steps.- Inspect the per-step results and payment history. Then write the plan from
the three responses and the user's planning inputs (mission, starting budget,
runway target, loss limits, allowed monetization paths):
- budget, expense categories, and runway;
- risk policy, loss caps, and kill switches (see
references/risk-policy.md); - paper-trading or non-trading monetization experiments, never live trades;
- what any later purchase (domain, hosting, compute) would cost, quoted separately and approved separately; and
- a stop, continue, or reinvest rule (see
references/economic-model.md).
Inputs And Outputs
| Param | Required | Default | Description |
asset | yes | none | One Hyperliquid ticker such as BTC or ETH. Research input only, not trading authorization. |
domainCandidate | yes | none | One full domain such as agent-alpha-research.com. Availability check only, not purchase authorization. |
Steps (fixed, no data passes between them):
| # | Call | Rail | Live quote (2026-10-04) | Cap |
| 1 | Otto KOL sentiment (broad, not filtered by asset) | x402 via Circle Gateway | $0.00315 | $0.004 |
| 2 | Otto Hyperliquid market for asset | x402 via Circle Gateway | $0.00105 | $0.002 |
| 3 | StableDomains availability and price for domainCandidate | MPP on Tempo | $0.0105 (.com) – $0.0525 (.ai/.io/.xyz) | $0.075 |
Expected total: $0.0147 for a .com-class domain, $0.0567 for an
.ai/.io-class domain. Sum of per-step caps: $0.081. The top-level
maxAmount is only a per-step fallback for a step without its own cap. It is
not a run cap.
Output:
- the three provider responses with retrieval time, each tagged with its
freshness fields (
dataAsOf,generatedAt,degradedwhere present); - the plan from step 6 of the Workflow; and
- per-step status plus the final settled cost.
Gotchas
- Fixed pipeline. Every run pays for all three calls. There is no step filter, no cheapest-first logic, and no stop after a useful result.
- A paid call can still fail. Each step settles independently. A provider
error after payment may still be charged. Check
selat historybefore any retry, and never re-run the whole bundle to repair one step. - The KOL report is broad. Do not imply that every narrative in it is about
the requested
asset. - Domain price depends on the TLD. A malformed or unsupported domain quotes
$0.105, which the$0.075cap refuses before payment. Validate the domain first. A check is point-in-time. It is not a reservation or a purchase. - CLI validation checks presence, not meaning. Confirm
assetis a simple supported Hyperliquid ticker before approval. - Planning is not execution. Inbox or wallet setup, Gateway funding, infrastructure purchases, and trades are outside this skill. Each needs its own quote, its own explicit approval, and a different tool.
- Profit is a hypothesis. Count only realized revenue. Backtests overfit, social sentiment can be manipulated, and data can be late or stale.
Validation
- Static:
selat skill validate ./skills/self-evolving-agent - Required-input gate:
selat skill verify ./skills/self-evolving-agent --live-probefails before any network probe, because both inputs are required. - Free live gate:
selat skill verify ./skills/self-evolving-agent --asset BTC --domainCandidate agent-alpha-research.com --live-probe - Paid check, only after fresh quotes, explicit approval, and an armed session
budget: add
--payto the free live gate. Every call may settle independently.
References
manifest.json- machine-readable three-call recipe.references/endpoints.md- request contracts, live prices, caps, and rails.references/verification.md- latest free live-probe results.references/economic-model.md- budget, P&L, and reinvestment model for the plan.references/risk-policy.md- approval gates, caps, and kill switches for the plan.references/catalogue-findings.md- historical catalogue snapshot (not executed by this skill).../../references/agent-skill-authoring-sop.md- authoring standard.
Provider and product names identify third-party services only. This skill is not affiliated with or endorsed by those providers and is not investment advice.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

