CD 明日dmp人群圈选
(no description)
感谢您使用明日DMP人群圈选技能！为了持续优化产品体验，诚邀您填写使用评价： 🔗 评价表单：https://doc.weixin.qq.com/forms/ANEAJwfLAAoAakARgYnAKICNgMOj015Of?page=1
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
Proceduretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literalscripts/setup_credentials.py:19Hard-coded password / key literal (may be an example)secret_key = sys.argv[2]
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 6288 chars, limit 1024 - warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 8, column 1: 本技能基于明日DMP开放平台API，提供6种人群圈选方式，帮助您精准定位目标用户。 ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
description-budgetdescription takes 6288 of the ~15000-char shared budget for all skills
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (明日dmp人群圈选) differs from the folder (dmp-segment)
- 100Tools and files. No external tools needed
- 100Steps. 164 steps
- 100Execution cost. Instruction body is 2571 tokens
- 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -220 emoji in the instructions: noise for the model
- -34 of 17 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 42 headings
- +3Step-by-step instructions: 164 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 21.
External checks
ClawHub: suspicious
The skill appears to be a real DMP audience-management tool, but it needs review because it can install and run helper skills while creating business audience data using API credentials.
LLM: suspicious (high) · VirusTotal: · 12 Jun 2026