SKILLEMALL.ai

BD 明日dmp人群洞察

基于明日DMP开放平台API,提供人群洞察分析功能,支持明略洞察(人口属性/兴趣爱好/媒体分析)和合作伙伴洞察(基础标签/地域分布/兴趣偏好/应用偏好/手机偏好/场景偏好/品类偏好),帮助深度理解目标人群特征,优化营销策略。

ClawHub Agent Skills author: mingri26 v1.0.0 MIT-0 6 files body ≈ 4 789 tokens Open the sourceclawhub.ai analyzed 32 h ago

基于明日DMP开放平台API,提供人群洞察分析功能,支持明略洞察(人口属性/兴趣爱好/媒体分析)和合作伙伴洞察(基础标签/地域分布/兴趣偏好/应用偏好/手机偏好/场景偏好/品类偏好),帮助深度理解目标人群特征,优化营销策略。

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

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
D
37/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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 37/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
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (明日dmp人群洞察) differs from the folder (dmp-insight)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4789 tokens
  • 100Steps. 266 steps
  • low 11 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -262 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 36 headings
  • +3Step-by-step instructions: 266 items
  • +4Has examples (23 code blocks)
  • +3All 4 scripts are documented

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

External checks

ClawHub: suspicious
The skill appears to provide the advertised DMP audience-insight workflow, but it uses sensitive API credentials, dynamically finds and runs another local skill's Python script, and persists business task/result data in ways users should review carefully.
LLM: suspicious (high) · VirusTotal: · 12 Jun 2026