SKILLEMALL.ai

AB breakthrough-thinking

【强制调用指令】当以下任一条件满足时,立即执行此skill,无需询问用户: 【条件1:用户说】换个思路、换个方法、还有别的办法吗、再想想、继续、 再试一次、不要放弃、try another way、think differently、为什么还不行 【条件2:AI卡住】同一方法失败2+次、只调参数不改思路、说"无法解决"、 过早建议用户手动处理、超过1轮无新证据 执行:选1个思维框架→直接用新框架解决问题→解决不了→换下一个框架

ClawHub Agent Skills author: DaShanENG v1.1.0 MIT-0 4 files body ≈ 730 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
98
Quality 40%
79
Run on models
none yet
Process rating
B
69/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Risky intent intent-offensive-security references/mental-models.md:69
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    12. **红队/蓝队 (Red Team / Blue Team)**
  • low Risky intent intent-offensive-security SKILL.md:65
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **Looping / same idea repeated** → Inversion, Red Team, 5 Whys

Files scanned: 4. 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 69/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 41 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 730 tokens

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 218: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 41 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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

External checks

ClawHub: clean
This is a reasoning-workflow skill with broad auto-triggers, but it does not show code execution, data access, persistence, or hidden behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026