SKILLEMALL.ai

AD kuaishou-account-works

快手账号作品查询工具,集作品列表与详情两大能力。通过账号平台展示id(kwaiId)或主页链接id(threeXId)查询该账号全部作品列表(按发布时间倒序,含播放/点赞/评论/收藏/分享/时长/封面/视频链接);通过作品ID(photoId)精确查询单条作品正文详情。当用户需要按账号查询快手作品列表、查看某博主全部作品、分析对标账号作品数据、深挖单条爆款作品、查看作品正文数据时使用。触发词:按账号查作品、快手作品列表、账号作品查询、查账号视频、对标账号作品、作品详情、作品正文、查作品详情、单条作品、爆款详情、作品数据详情。

redfox-data/redfox-community Agent Skills author: redfox-data 6 files body ≈ 491 tokens Open the sourcegithub.com analyzed 5 h ago

快手账号作品查询工具,集作品列表与详情两大能力。通过账号平台展示id(kwaiId)或主页链接id(threeXId)查询该账号全部作品列表(按发布时间倒序,含播放/点赞/评论/收藏/分享/时长/封面/视频链接);通过作品ID(photoId)精确查询单条作品正文详情。当用户需要按账号查询快手作品列表、查看某博主全部…

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

IntegrationAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
46/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: 6. 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 46/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
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 491 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 265: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 17 items
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 2 scripts are documented

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