BD Report-gama
🎯 深度市场调研报告生成技能 —— 专为目标国家+目标品类量身定制。支持13个信息采集模块:多语种搜索、新闻监控、竞争分析、电商价格、广告投放、海关数据、政府招标(Tender)、医疗器械注册证(Roszdravnadzor)、Telegram社群、VKontakte社群、医疗机构分布、参考定价(ЖНВЛП)。生成15章节专业长篇调研报告并导出PDF+图表。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Obfuscation
uni-mixed-script-wordscripts/report_generator.py:609Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence)report += "- **促销活动**:关注Wildberries/Ozon的Чёрная пятница(黑五)折扣\n\n"
Files scanned: 24. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- 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
frontmatter-keyunknown frontmatter key "categories" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage"
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 (Report-gama) differs from the folder (reportgama2)
- 100Tools and files. No external tools needed
- 100Steps. 66 steps
- 100Execution cost. Instruction body is 2617 tokens
- 100Running it twice. No mutating operations
- low 12 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)
- +3Output format is not stated: the model decides each time
- -231 emoji in the instructions: noise for the model
- -37 of 18 scripts are never mentioned in SKILL.md
- +1No license
- +3Description length 181: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 66 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.