SKILLEMALL.ai

CC loudy-ai-auto-task

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

Not recommendedcritical or high security findings
ClawHub Agent Skills author: jack v1.1.0 13 files · 2 scripts body ≈ 951 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
65/100
safety, quality, tests
Safety 60%
61
Quality 40%
71
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

  • high Dangerous commands cmd-persistence SKILL.md:167
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null; echo "*/5 * * * * $SKILL_DIR/scripts/cron_check.sh") | crontab -
  • high Dangerous commands cmd-persistence SKILL.md:170
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null; echo "*/5 * * * * /usr/lib/node_modules/openclaw/skills/loudy-ai-auto-task/scripts/cron_check.sh") | crontab -
Medium and low: 3
  • low Dangerous commands cmd-pipe-to-shell-known-host install.sh:3
    Pipe-to-shell installer from a well-known host (still executes remote code) (code comment)
    # 使用方法: curl -fsSL https://raw.githubusercontent.com/sfsf332/claw-loudyai-skill/main/install.sh | bash
    comment
  • low Dangerous commands cmd-cron-mention SKILL.md:167
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "*/5 * * * * $SKILL_DIR/scripts/cron_check.sh") | crontab -
  • low Dangerous commands cmd-cron-mention SKILL.md:170
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "*/5 * * * * /usr/lib/node_modules/openclaw/skills/loudy-ai-auto-task/scripts/cron_check.sh") | crontab -

Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 38 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 951 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (5 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 188: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 38 items
  • +4Has examples (10 code blocks)
  • +3All 7 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.

External checks

ClawHub: suspicious
The core Loudy.ai task workflow is understandable, but the skill needs review because it combines account-mutating API use with an unsafe installer and guidance toward a separate Twitter-posting skill that is not clearly disclosed in the main description.
LLM: suspicious (high) · VirusTotal: · 29 May 2026