Claw Loudyai Skill

v1.1.0

Loudy.ai 任务自动化工具 - 查询奖池、提交任务链接、追踪审核和支付状态。 重要说明:此工具仅与 loudy.ai API 交互,不包含 Twitter/X 自动发布功能。 使用条件: (1) 用户需要先配置 LOUDY_API_KEY 环境变量 (2) 启动后会定时查询奖池、提交任务链接、查询审核和支付...

1· 289·1 current·1 all-time
byjack@sfsf332

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sfsf332/claw-loudyai-skill.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Claw Loudyai Skill" (sfsf332/claw-loudyai-skill) from ClawHub.
Skill page: https://clawhub.ai/sfsf332/claw-loudyai-skill
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: [object Object]
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install sfsf332/claw-loudyai-skill

ClawHub CLI

Package manager switcher

npx clawhub@latest install claw-loudyai-skill
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the actual behavior: scripts only call loudy.ai endpoints to list pools, submit links, and check task/payment status. The single declared secret (LOUDY_API_KEY) is appropriate for this purpose.
!
Instruction Scope
Runtime instructions and scripts read/write files in the workspace (loudy_tasks.json, loudy_has_new.txt) and optionally configure a cron job — these are reasonable for periodic checks but the SKILL.md, scripts, and install script use inconsistent environment variable names (OPENCLAW_WORKSPACE vs OPENCLAW_SKILLS_DIR vs OPENCLAW_SKILL_DIR). The SKILL.md also references optional HEARTBEAT.md behavior and recommends installing an external Binance skill (a separate dependency) — these are allowed but increase scope and require user attention.
Install Mechanism
No centralized install spec, but an install.sh is provided which clones a GitHub repo and sets permissions. The install.sh header suggests the common but risky pattern 'curl | bash' (downloading and piping a remote script). The repository and scripts are included in the package so users can avoid piping from the network and inspect code before running. Installation writes to system paths (/usr/lib/node_modules/...) and may require root.
Credentials
Only LOUDY_API_KEY is required for operation which is proportional. However metadata shows a glitch (Required env vars displayed as '[object Object]') and several optional env vars are referenced but not consistently declared (OPENCLAW_WORKSPACE is documented, but OPENCLAW_SKILLS_DIR / OPENCLAW_SKILL_DIR appear in scripts/install.sh/cron_check.sh). This inconsistency can cause misconfiguration if not reviewed.
Persistence & Privilege
Skill is not always: true and does not request elevated platform privileges. Optional cron installation will create periodic checks and the installer may need root to write under /usr/lib; these are normal for an installed skill but require the user to consent. The skill does not modify other skills' configs.
Assessment
This skill appears to do what it says (call Loudy.ai APIs to list pools, submit links, and check status). Before installing: 1) Verify and set LOUDY_API_KEY only in environment (do not paste it into shared files). 2) Inspect the included scripts locally rather than running the remotely piped install command (avoid 'curl ... | bash'); run install.sh from the local copy or clone the repo manually. 3) Note environment-variable name inconsistencies (OPENCLAW_WORKSPACE vs OPENCLAW_SKILLS_DIR vs OPENCLAW_SKILL_DIR) — confirm which you will set. 4) Installing to /usr/lib/... or adding the cron line requires elevated privileges; review the cron line before adding it. 5) The skill suggests optionally installing a third-party 'binance' skill — that is separate and increases risk; only install trusted external skills. 6) If you want tighter control, run scripts manually or in a limited account instead of enabling automatic cron jobs. If you want me to, I can list the exact env vars and lines to run to install safely or produce a checklist to audit the repo before running any installer.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Env[object Object]
latestvk97akhht98q7xe50t9z2975k4x82eg3a
289downloads
1stars
3versions
Updated 1mo ago
v1.1.0
MIT-0

Loudy.ai 自动任务 Skill

⚠️ 安全警告

  • 🔐 API Key 安全:建议使用环境变量 export LOUDY_API_KEY=你的密钥不要写入 TOOLS.md 或其他共享文件
  • 📝 文件系统访问:本工具会读写工作区目录下的文件(默认:/root/.openclaw/workspace/,可通过 OPENCLAW_WORKSPACE 环境变量自定义)
  • 可选的 Cron 任务:如需自动检查,需手动配置 cron 任务

快速开始

1. 配置 API Key (推荐环境变量方式)

export LOUDY_API_KEY="你的API密钥"

⚠️ 注意:不建议将密钥写入 TOOLS.md,避免意外泄露

2. 启动任务

告诉 AI:

"查看 loudy 可用奖池"

3. 自动执行流程

  1. AI 展示可用奖池详情(包括要求、奖金、截止时间、详情页面链接)
  2. 你根据要求发布推文到 X/Twitter
  3. 将推文链接发送给 AI
  4. AI 自动提交到 loudy.ai

工作流程

1. fetch_earning_pools() → 获取进行中的奖池列表
2. 展示奖池详情给用户 → 包括要求、奖金、截止时间、详情页面链接
3. 提示用户根据要求发推文 → 用户手动发布到 X/Twitter
4. 等待用户提供推文链接 → 用户把推文链接发给 AI
5. submit_task() → 自动提交作品链接到 loudy.ai
6. 定时 check_task_status() → 查询任务是否被接受
   ├─ 超时未接受 → 报告失败
   └─ 已接受 → 定时查询 payment/支付信息

用户交互流程示例

步骤 1: 查看可用奖池

用户: "查看 loudy 可用奖池"
AI: 调用 fetch_pools.py,展示奖池列表(包含详情页面链接)

步骤 2: 选择奖池并发推文

AI: 展示奖池详情和要求
用户: 选择奖池,根据要求发布推文

步骤 3: 提交推文链接

用户: "提交推文链接 https://x.com/xxx/status/123 到奖池 3"
AI: 调用 submit_task.py(3, "https://x.com/xxx/status/123")

步骤 4: 查询任务状态

用户: "查询任务状态"
AI: 调用 check_task.py 查询审核和支付状态

API 接口

1. 获取奖池列表

  • URL: GET https://api.loudy.ai/app-api/open-api/v1/earning-pools
  • Header: X-API-Key: <LOUDY_API_KEY>

2. 获取奖池详情

  • URL: GET https://api.loudy.ai/app-api/open-api/v1/earning-pools/{id}
  • Header: X-API-Key: <LOUDY_API_KEY>

3. 提交任务

  • URL: POST https://api.loudy.ai/app-api/open-api/v1/earning-pool-tasks/submit
  • Header: X-API-Key: <LOUDY_API_KEY>
  • Body:
{
  "earningPoolId": 123,
  "taskLink": ["https://x.com/xxx/status/123"],
  "languageType": "zh_CN"
}

4. 查询我的任务列表(分页)

  • URL: GET https://api.loudy.ai/app-api/open-api/v1/earning-pool-tasks
  • Header: X-API-Key: <LOUDY_API_KEY>
  • Query:
    • pageNo - 页码(必填)
    • pageSize - 每页条数,最大100(必填)
    • earningPoolId - 奖池ID(可选)
    • taskStatus - 任务状态(可选)

5. 查询任务状态

  • URL: GET https://api.loudy.ai/app-api/open-api/v1/earning-pool-tasks/{id}
  • Header: X-API-Key: <LOUDY_API_KEY>
  • 返回字段:
    • taskStatus - 任务状态
    • auditStatus - 审核状态 (0=未审核, 1=通过, 2=拒绝)
    • taskLinks - 作品链接

脚本说明

scripts/fetch_pools.py

获取进行中的奖池列表,过滤 Ongoing 状态

scripts/list_my_tasks.py

查询当前用户的任务列表(分页)

scripts/submit_task.py

提交作品链接到奖池

scripts/check_task.py

查询单个任务状态和支付信息

scripts/auto_task_flow.py

优化的任务流程脚本:

  1. 获取可用奖池列表
  2. 展示奖池详情(包括要求、奖金、截止时间)
  3. 显示 Loudy.ai 详情页面链接
  4. 等待用户提供推文链接
  5. 自动提交到 loudy.ai

scripts/check_tasks.py

定时检查脚本,获取当前奖池并格式化输出

scripts/cron_check.sh

Cron 定时任务脚本,每5分钟检查一次新任务。使用 OPENCLAW_WORKSPACE 环境变量自定义工作目录。

配置定时检查(可选)

1. 设置环境变量

export LOUDY_API_KEY="你的API Key"
export OPENCLAW_WORKSPACE="/root/.openclaw/workspace"  # 可选,默认值

2. 配置 Cron 定时检查(可选)

# 方法1: 使用工作区安装路径(推荐)
SKILL_DIR="/root/.openclaw/workspace/skills/claw-loudyai-skill"
(crontab -l 2>/dev/null; echo "*/5 * * * * $SKILL_DIR/scripts/cron_check.sh") | crontab -

# 方法2: 如果安装到系统路径
(crontab -l 2>/dev/null; echo "*/5 * * * * /usr/lib/node_modules/openclaw/skills/loudy-ai-auto-task/scripts/cron_check.sh") | crontab -

3. 配置 Heartbeat 通知(可选)

在 HEARTBEAT.md 中添加:

## Loudy.ai 任务检查
检查工作区目录下的 loudy_has_new.txt 是否存在:
- 如果存在 → 读取 loudy_tasks.json 内容
- 发送消息通知用户
- 删除 loudy_has_new.txt

注意事项

  • ⚠️ API Key 安全:建议使用环境变量 export LOUDY_API_KEY=你的密钥不要写入 TOOLS.md 或其他共享文件
  • 📝 文件系统访问:本工具会读写工作区目录下的文件(默认:/root/.openclaw/workspace/,可通过 OPENCLAW_WORKSPACE 环境变量自定义),包括 loudy_tasks.json, loudy_has_new.txt
  • 可选的 Cron 任务:如需自动检查,需手动配置 cron 任务(可选功能)
  • 🐦 Twitter 功能说明:本工具不包含 Twitter/X 自动发布功能,用户需手动发布推文后提供链接
  • 任务截止时间:任务有截止时间 (activityEnd),需在截止前提交
  • 审核流程:提交后需等待审核 (auditStatus),建议设置定时检查间隔为 5-10 分钟

Comments

Loading comments...