Skills/ClawHub/make-loop

make-loop@1.0.1

CAUTION· static only

Publisher claims: "把用户一句大白话的任务,改写成一个写得清清楚楚、能放心让 AI 自己跑的循环(loop)任务说明。结构是三段:目标(我要做什么)→ 过程(它要怎么做)→ 检查迭代(做完检查,再接着改);里面写全五件事:目标是什么、每轮做什么、怎么检查、记录什么、什么时候停。自带这些经验:评审一次给全清单、开发一口气改完;评审用统一的尺子;定期让用户本人看前后对比;刹车写全但不乱停。用户不会写 loop,只要说「帮我变成 loop」「做成循环」「写个 loop」「让它自己一轮一轮改到好」「反复迭代直到没问题」「让它一直跑」,或者丢来一个任务加一句 /make-loop,就用这个技能。适用任何任务。默认只把任务写成 loop,不开始执行;只有用户明确要求现在就在这次对话里执行,并先确认范围,才动手。任务本身的专业知识由当时的对话和其他技能提供。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher ekko237 · publishing for 3 daysInstalls 48Last detonated 1 h ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

What changed since 1.0.0

vet-skills diff make-loop 1.0.0 1.0.1

In the sandbox, this version reached for nothing 1.0.0 did not. Compared from the two recorded runs, not from source.

1.0.1 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-15 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

No findings across 433 lines in 8 files.

Cost to the agent

Instructions loaded
≈887 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim ekko237: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim ekko237Propose a patch to the maintainer