SKILLEMALL.ai

CD seedance-fight-scenes

为 Seedance 2.0(Higgsfield)生成强烈的动作场景和打斗序列视频提示词。在用户想要打斗场景、格斗、武术、战斗、动作编舞、剑斗、手对手格斗、追逐场景、超级英雄动作或任何高能动作视频时使用。触发词:打斗、格斗、战争、武术、动作场景、编舞、决斗、剑斗、功夫、追逐、斗殴、拳、踢、武器格斗、超级英雄打斗或任何动作/打斗请求。即使用户说"制作一个高强度动作视频"或"史诗战斗"也要使用。

beshuaxian/higgsfield-seedance2-jineng Agent Skills author: beshuaxian 1 file body ≈ 1 488 tokens Open the sourcegithub.com↗ analyzed 15 h ago

为 Seedance…

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

Proceduretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
49/100
Unfinished process
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

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 · 0

✓ No critical or high findings

Files scanned: 1. 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 49/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
  • 40Consistency. Frontmatter name (seedance-fight-scenes) differs from the folder (zh-CN)
  • 100Tools and files. No external tools needed
  • 100Steps. 20 steps
  • 100Execution cost. Instruction body is 1488 tokens
  • 100Running it twice. No mutating operations

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 198: enough signal without eating the budget
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (23 code blocks)

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