SKILLEMALL.ai

CD tiktok-keyword-topic-search

根据关键词搜索 TikTok 话题数据,并支持按话题 ID 查询该话题下的作品列表。基于红狐数据,按关键词返回话题名称、话题 ID、使用次数、浏览量、参与人数等核心数据;输入话题 ID 可继续查询该话题下的作品,输出播放、点赞、评论、分享等核心数据与可点击完整作品链接,支持分页与排序切换。适用于用户要求搜索 TikTok 话题、查询关键词相关话题、根据话题 ID 查话题作品时使用。触发词:TikTok 关键词搜话题、搜索 TikTok 话题、TikTok 话题数据、话题 ID 查作品、hashtag 搜索。

redfox-data/redfox-community Agent Skills author: redfox-data 6 files · 2 scripts body ≈ 434 tokens Open the sourcegithub.com↗ analyzed 6 d ago

根据关键词搜索 TikTok 话题数据,并支持按话题 ID 查询该话题下的作品列表。基于红狐数据,按关键词返回话题名称、话题 ID、使用次数、浏览量、参与人数等核心数据;输入话题 ID 可继续查询该话题下的作品,输出播放、点赞、评论、分享等核心数据与可点击完整作品链接,支持分页与排序切换。适用于用户要求搜索…

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

ProcedureMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
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 (python) that frontmatter does not declare
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 434 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
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 256: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 25 items
  • +4Reference files are cited in the instructions (1 of 1)

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