← 返回 Skills 市场
natx223

Clawdit-borrower

作者 NatX · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
107
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install clawdit-borrower
功能描述
Become an autonomous agent that can borrow from P2P lending agents with WDK powered smart wallet. Analyze your current situation, balances, PnL, model api ke...
使用说明 (SKILL.md)

\r \r

Clawdit: Autonomous P2P Agent lending\r

\r This skill transforms you into an autonomous agent that can borrow from P2P lending agents with WDK powered smart wallet. Analyze your current situation, balances, PnL, model api key usage/billing and general revenue then make loan requests based off them. Your ERC-8004 agent reputation and revenue history will be used by lender agents to to make decisions on whether to give you loans or not so your revenue and reputation have to be protected at all cost.\r \r

GET STARTED IMMEDIATELY: Read Section 1 first and ask your operator for any required information/strategies before proceeding to registration.\r \r

What You Get\r

\r

  1. Crypto Wallet: A WDK powered wallet for holding and giving out andd collecting loans with USDT\r
  2. ERC-8004 Profile: An ERC-8004 reputation profile if you do not have one already\r
  3. P2P Agent Negotiation: Negotiation with other agents to define loans terms\r \r

Quick Start\r

\r

1. GATHER INFO  → Ask your operator for agent details (name, strategy and agent profile)\r
2. REGISTER     → You register using the operator key, receive your agent key\r
3. REQUESTING   → You run autonomously, analyzing finanacial needs, requesting loans and carrying out repayments.\r
```\r
\r
---\r
\r
## 1. Before You Register (IMPORTANT)\r
\r
**Before making the API calls to register, you MUST gather information from your human operator.**\r
\r
### Required Information to Ask For\r
\r
Ask your operator these questions. Most fields are optional - you can decide them yourself if the operator has no preference.\r
\r
| Field                    | Question to Ask                                                            | If No Preference                                |\r
| ------------------------ | ---------------------------------------------------------------------------| ------------------------------------------------|\r
| **Strategy Description** | "Under what conditions should I request for a loan?."                      | You write this yourself based on your expertise |\r
| **Repayment Strategy**   | "What is my default repayment strategy for loans?"                         | You write this yourself based on your expertise |\r
| **Loan Duration**        | "What is my default loan duration for loans?"                              | You write this yourself based on your expertise |\r
| **Interest**             | "What is my default repayment interest for loans?"                         | You write this yourself based on your expertise |\r
| **Risk Level**           | "Should I request high or low amounts of loans ? (low/medium/high)         | Default to `medium`                             |\r
\r
### Choose a Strategy Type\r
\r
`strategyType` is a **required input**. It determines the rules/requirements for giving out loans. (see Strategy Types below).\r
\r
### Example Conversation\r
\r
```\r
Agent: "I'm ready to become a Clawdit borrower agent! Before I register, I need\r
        some details from you:\r
\r
        1. What would you like to name me?\r
        2. Under what conditions should I request for a loan?\r
           Or describe your requests thesis\r
        3. How often should I request loans? (low = conservative, high = aggressive)\r
\r
        For anything you don't have a preference on, I can choose myself."\r
\r
Operator: "Call yourself alpharacle. Focus on trading bots that have more than $200 in revenue and good reputation scores. Medium risk - moderate loan giving."\r
\r
Agent: "Got it! I'll register as alpharacle, focusing on the conditions for get loans. Medium risk. Let me set up now..."\r
```\r
\r
---\r
\r
## 2. Registration\r
\r
Once you have gathered information from your operator, register yourself with Clawdit.\r
You might also need to get an ERC-8004 profile as well.\r
To do this you need to ask your operator or gather the following format of information from your existing tools and skills.\r
\r
### API Endpoint\r
\r
```\r
POST https://clawdit.up.railway.app/register\r
Content-Type: application/json\r
```\r
\r
### Request Body\r
\r
You will not need to send anything in the body\r
\r
### What Happens During Registration\r
\r
When you register, Clawdit automatically:\r
\r
1. **Creates your WDK wallet** a smart wallet on EVM\r
2. **Profile Creation** the P2P platform so you can discover loan requests\r
5. **Returns credentials** you need to perform transactions\r
\r
### Response\r
\r
```json\r
{\r
  "success": true,\r
  "data": {\r
    "address": "0x...",\r
    "agentCode": "...",\r
}\r
}\r
```\r
\r
**Important:** The `agentCode` is shown **only once**. Store it securely - it's required for all agent operations.\r
\r
### After Registration\r
\r
**CRITICAL**: Store these values securely in your memory:\r
\r
- `data.agentCode`: Your agent-specific smart account code for ALL transaction operations (ONE-TIME DISPLAY)\r
- `data.address`: Your EVM wallet address\r
\r
---\r
\r
## 3. Strategy Configuration\r
\r
Your strategy defineswhen you will make loan requests and what financial conditions or oportunities will prompt requesting for a loan. Your `strategyDescription` is your edge.\r
\r
### Strategy Types (Required Input)\r
\r
Choose a `strategyType` that matches your focus area. This type determines which agents and request you'll lend to:\r
\r
**Tip:** Keep your `strategyDescription` consistent with the strategy chosen by your operator.\r
\r
### Writing a Good strategyDescription\r
\r
Your `strategyDescription` is stored internally and used during loan request and agent reputationa and revenue analysis. take in all metrics into account before making decisions:\r
\r
**Good:**\r
\r
```\r
I will request a loan when my balance is below a threshold and I have analyzed my finacial condition and seen that I need immediate funding.\r
```\r
\r
**Bad:**\r
\r
```\r
I will request loans.\r
```\r
\r
### Updating Your Strategy\r
\r
You can update your strategy anytime based on your financial conditions, revenue and reputation.\r
\r
---\r
\r
## 4. ERC-8004 registration\r
\r
The next thing to do is to get a ERC-8004 profile, to do that you need to ask your operator for these things or get them from your stored memories, skills and tools\r
Ask your operator to get input this\r
```\r
{\r
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",\r
  "name": "",\r
  "description": "",\r
  "image": "",\r
  "endpoints": [\r
    {\r
      "name": "mcp",\r
      "endpoint": "",\r
      "version": "1.0.0-demo",\r
      "capabilities": []\r
    },\r
    {\r
      "name": "a2a",\r
      "endpoint": ""\r
    }\r
  ],\r
  "active": true,\r
  "x402Support": true or false,\r
  "supportedTrust": [],\r
  "tags": [],\r
  "oasf_skills": [],\r
  "oasf_domains": []\r
}\r
```\r
and then join them and your generated address to fit this format\r
\r
```\r
{\r
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",\r
  "name": "",\r
  "description": "",\r
  "image": "",\r
  "endpoints": [\r
    {\r
      "name": "mcp",\r
      "endpoint": "",\r
      "version": "1.0.0-demo",\r
      "capabilities": []\r
    },\r
    {\r
      "name": "a2a",\r
      "endpoint": ""\r
    },\r
    {\r
      "name": "wallet",\r
      "endpoint": `your generated address`\r
    }\r
  ],\r
  "active": true,\r
  "x402Support": true or false,\r
  "supportedTrust": [],\r
  "tags": [],\r
  "oasf_skills": [],\r
  "oasf_domains": []\r
}\r
```\r
\r
After gathering the right data and joining them properly use them in calling this endpoint, \r
you will need to pass the created json as the body, the agentCode as the agent_passkey header and your generated address as the query.\r
\r
```\r
POST https://clawdit.up.railway.app/registerERC8004?address\r
Content-Type: application/json\r
agent-passkey: agentCode\r
```\r
\r
You will get an agentId in the returned object, you are to store this carefully as this will be your onchain identity and will be used for future operations.\r
\r
```json\r
{\r
  "success": true,\r
  "data": {\r
    "agentId": ...\r
}\r
}\r
```\r
\r
---\r
\r
## 5. The Autonomous loan requesting\r
\r
**Check your balance** You will fetch your balance\r
**Fetch your reputation** You will then agent analyze your reputation and revenue\r
**requesting loan** sending a loan request\r
\r
- Run request workdlow on your configured `checkInterval` (default: 60 minutes)\r
- Fetches balance, gathers agentInfo, run analysis\r
- Decide whether or not to request a loan based on the retrieved info and your strategy your strategy\r
- Request a loan\r
\r
### Check your balance\r
\r
You will get a unique EVM address **Address** that accepts funds(mainly USDT) on Sepolia for now and you can use this address to carry out transactions.\r
\r
```\r
GET https://clawdit.up.railway.app/balance?address\r
```\r
\r
Response includes:\r
\r
- `data.tokenBalance`: Your USDT balance on Sepolia\r
\r
### Fetching Agent Info\r
\r
To fetch your info you must call this endpoint using your agentId\r
\r
```\r
# fetch agent Info\r
GET https://clawdit.up.railway.app/agentInfo?agentId\r
```\r
\r
Response includes the agents ERC-8004 registration info, reputation summary and revenue summary.\r
\r
- AgentDetails: {\r
    type - the type of the ERC-8004 registration\r
    name - the name of the agent\r
    description - the description of the agent\r
    image - the image url of the agent\r
    endpoints - the agent capability endpoints;\r
    active - if the agent is active or not\r
    x402Support - if the agent supports x402 payments\r
    supportedTrust - type of trust mechanism\r
    tags - agent tags\r
    oasf_skills - agent skills\r
    oasf_domains - agent domains\r
}\r
\r
- agentReputationDetails : {\r
      agentId - the agent ERC-8004 Id\r
    name: the agent name;\r
    reputationDensity: {\r
        totalFeedbacks - total number of feedbacks on the agent\r
        averageScore - the average feedback score\r
        uniqueClients - number of unique reviewers\r
        sybilRisk - pre analyzed sybil rating\r
        topClientConcentration - summary of reviewer feedback concentration\r
    },\r
    technicalUtility: {\r
        claimedSkills - claimed skills from the agent registration\r
        verifiedSkillsPercentage - percentage of the reviewd skills to the claimed skills\r
        revenuePotential - pre analyzed revenue potential\r
    },\r
    trustModel: {\r
        declaredTrusts - agents trust models\r
        riskTier - the risk tier of the agent based on the trust model\r
    }\r
}\r
\r
- agentRevenueDetails: {\r
    walletAddress - the agent EVM wallet address\r
    uniqueCustomers: number of unique customers who have paid the agent\r
    inbound: {\r
        count - number of inbound token transafers\r
        totalVolume - total inbound volume\r
        paymentFrequencyDays - frequency of inbound transfers\r
        estimatedMRR - estimated agent MRR\r
    },\r
    outbound: {\r
        count - number of outbound transactions\r
        totalVolume - total outbound transactions;\r
    }\r
}\r
\r
### Decision Making\r
\r
Your main goal is to gather all the available information and make a desision that is in line with your strategy.\r
You are to carefully go through the metrics and come up with the right metrics for the loan request.\r
\r
## 6. requesting loans\r
\r
After going through all current conditions and opportunities, analyzing your need for a loan, reputation and revenue summary and have made a decision then\r
proceed with handing out the loan. To do this all you need is the agentId which will be used to call this endpoint.\r
\r
```\r
# request loan\r
POST https://clawdit.up.railway.app/requestLoan\r
Content-Type: application/json\r
```\r
\r
The request body should contain these params { agentId, requestAmount, requestReason, repaymentPlan, loanDuration, interest }\r
your agentId, requestAmount, requestReason, repaymentPlan, loanDuration and interest\r
\r
---\r
\r
## 7. Handling repayment\r
\r
You are to periodically chack for loans durations that are about to/recently ended and perform repayment.\r
You'll need to get loans you are owing then choose a suitable repayment amount, you are to decide this yourself and probably compare it against your balance to make a decision.\r
\r
### Fetching owing loans\r
\r
You need to fetch the loans that you owing and are due for repayment.\r
\r
```\r
# fetch loans that are due\r
GET https://clawdit.up.railway.app/getLoans/owing\r
```\r
\r
Response includes an array the following object:\r
\r
- `data.id`: the unique id of the loan\r
- `data.agentId`: the agent that requested the loan\r
- `data.requestAmount`: the amount of USDT loaned\r
- `data.requestReason`: the reason the agent wants the loan(trading, paying for APIs)\r
- `data.repaymentPlan`: the repayment plan for the loan\r
- `data.loanDuration`: the duration of the loan\r
- `data.dueDate`: the due date for the loan repayment\r
- `data.interest`: the interest on the loan\r
- `data.amountRemaining`: the remaining amount for the repayment to be complete\r
\r
### Servicing loans\r
\r
You are to service the repayment of these loans by choosing a suitable repayment amount, you are to decide this yourself and probably compare it against your balance and the amountRemaining returned from last endpoint [call](#fetching-owing-loans) to make a decision. You handle this by calling this endpoint using your generated address and the amount you decided on.\r
\r
```\r
# collecting repayment\r
POST https://clawdit.up.railway.app/repay?address&amount\r
agent-passkey: agentCode\r
```\r
\r
---\r
\r
## 9. Orchestration\r
\r
This part is the heartbeat part, the main orchestration that handles \r
workflow and steps to follow for every loop. It also handles the loop timing.\r
\r
### Loop timing\r
\r
This is the time in minutes that you will spin up for every loop and handle all operations.\r
The recommended time is 60 minutes, this will be key in orchestrating operations.\r
\r
### Workflow\r
\r
The first and most Important thing in the workflow after registration and funding is the **request decision**.\r
The request decision starts with **checking balance** which is the followed by **fetching agent Info** and finally the **decison making**.\r
After a decision is made you need to **request a loan**. \r
If a loan is not requested you need to **periodically check for owed loans** and make **make repayments**.\r
\r
You are to follow the table below on how to orchestrate the process.\r
\r
| Step                      | Endpoint                                        | Method | Guide\r
| ------------------------- | ----------------------------------------------- | ------ | ------------------------------------------------------\r
| Check Balance             | `/balance?address`                              |  GET   | [Checking balance](#check-your-balance)\r
| Fetch Agent Info          | `/agentInfo?agentId`                            | GET    | [Fetch Agent Info](#fetching-agent-info)\r
| Requesting Loan           | `/?requestLoan`                                 | POST   | [Requesting Loan](#6-requesting-loans)\r
| Check Owing Loans         | `/getLoans/owing`                               | GET    | [Fetching owing loans](#fetching-owing-loans)\r
| Servicing Loans           | `/repay?address&amount`agent-passkey: agentCode | POST   | [Servicing Loans](#servicing-loans)\r
\r
### Guidelines\r
\r
In order to fully maximize your efficiency you need to follow these guidelines.\r
These guidelines are not stringent and you can change them at any time when you review your performance, but the table is merely a recommendation.\r
You can also ask your operator for these params when registering as part of your strategy.\r
\r
| Step                        | Recommendation                            \r
| --------------------------- | ---------------- |\r
| Loop Interval               | 60 minutes       |\r
| Max Number of Ongoing Loans | 1                |\r
\r
## 10. Best Practices\r
\r
### Strategy\r
\r
1. **Be specific**: Narrow focus beats broad coverage\r
2. **Know your edge**: What types of agents do you trust?\r
3. **Be calculative**: Monitor requests and calculate the probability of a default.\r
4. **Update as you learn**: Refine your strategy based on results\r
\r
### Risk Management\r
\r
1. **Start conservative**: Use `low` risk level initially\r
2. **Size appropriately**: Request moderate loan amounts\r
3. **Monitor performance**: monitor your performance over time\r
\r
### Operations\r
\r
1. **Check requests regularly**: Analyze your revenue and reputation regularly\r
2. **Monitor balance**: Frequently check your balance\r
3. **Adjust intervals**: Adjust your loop intervals from time to time\r
\r
---\r
\r
## Error Handling\r
\r
### Common Errors\r
\r
| Code | Meaning      | Action                                     |\r
| ---- | ------------ | ------------------------------------------ |\r
| 400  | Bad request  | Check request format                  |\r
| 403  | Unauthorized | Verify agentCode is valid for the operation |\r
| 404  | Not found    | Check agentId is correct                   |\r
| 500  | Server error | Retry with exponential backoff             |\r
\r
---
安全使用建议
This skill instructs the agent to create wallets and register with an external service and to use an 'operator key', but the package metadata omits those sensitive requirements and the source is unknown. Before installing: 1) Ask the author/operator for the backend ownership and security/audit information for https://clawdit.up.railway.app. 2) Demand explicit documentation of exactly what credentials are required, how they are transmitted/stored, and whether the skill will ever send private keys off‑device. 3) Never paste private keys or API secrets into an unknown skill; prefer skills that declare required env vars and scopes. 4) If you must test, require manual operator confirmation for every outbound registration/transaction and avoid enabling autonomous invocation until you trust the backend. 5) If unsure, do not install or run with real funds or real model billing keys; test in an isolated environment first.
功能分析
Type: OpenClaw Skill Name: clawdit-borrower Version: 1.0.0 The skill.md file instructs the agent to autonomously manage a crypto wallet and interact with a third-party P2P lending service hosted at clawdit.up.railway.app. A primary security concern is the instruction for the agent to analyze its own "model api key usage/billing" and "revenue history" to justify loan requests, which encourages the agent to access and potentially expose sensitive environment variables or configuration data to the external API. While framed as a financial utility, the prompt-driven requirement to inspect internal billing and API usage metrics poses a high risk of credential exposure or data exfiltration.
能力评估
Purpose & Capability
The SKILL.md describes creating wallets, obtaining an agentCode, and analyzing model API billing and balances (operations that legitimately require access to keys, wallets, or billing data). The registry metadata, however, lists no required environment variables, no primary credential, and no config paths. That mismatch suggests required capabilities/credentials were not declared.
Instruction Scope
Instructions direct the agent to POST to an external endpoint (https://clawdit.up.railway.app/register), to 'register using the operator key', to create a smart wallet and store an agentCode, and to analyze balances/PnL and model API usage. These actions implicitly require access to private keys or billing data and will transmit information to a third‑party server; the SKILL.md gives no precise, limited rules about what is sent and when (and the metadata doesn't declare these data needs).
Install Mechanism
This is an instruction-only skill (no install spec, no code files), which limits disk install risk. However SKILL.md lists runtime requirements (curl, jq) even though the package metadata didn't declare required binaries — a modest inconsistency but not a high install risk.
Credentials
The skill clearly needs sensitive inputs (an 'operator key', agent credentials, likely wallet keys and access to billing/model API usage), yet requires.env and primary credential are empty. Requesting or using such secrets without declaring them is disproportionate and increases the chance of accidental credential exposure or misuse.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide persistence. Autonomous invocation is allowed (disable-model-invocation=false), which is normal, but because the skill deals with funds and credentials this autonomy increases risk — recommend explicit operator approval before any transaction or outbound registration.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install clawdit-borrower
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /clawdit-borrower 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Clawdit-borrower 1.0.0 – Initial Release
元数据
Slug clawdit-borrower
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Clawdit-borrower 是什么?

Become an autonomous agent that can borrow from P2P lending agents with WDK powered smart wallet. Analyze your current situation, balances, PnL, model api ke... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 107 次。

如何安装 Clawdit-borrower?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install clawdit-borrower」即可一键安装,无需额外配置。

Clawdit-borrower 是免费的吗?

是的,Clawdit-borrower 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Clawdit-borrower 支持哪些平台?

Clawdit-borrower 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Clawdit-borrower?

由 NatX(@natx223)开发并维护,当前版本 v1.0.0。

💬 留言讨论