AD public-opinion-report
调用Midu-Public-Opinion-Report接口，生成一篇舆情分析报告。支持的报告类型：事件专报、话题报告、行业报告、活动报告、周期性报告、直报点上报快评、直报点上报综述、直报点热点报送、品牌传播洞察报告、城市对标分析报告、城市传播影响力报告、区域网络信息报告、公共政策网络舆情报告。Call the Midu-Public-Opinion-Report interface to generate a public opinion analysis report. Supported report types:incident special report, topic report, industry report, event report, periodic report, direct reporting point quick review submission, direct reporting point overview submission, direct reporting point hot topic submission, brand communication insight report, city benchmarking analysis report, city communication impact report, regional online information report, public policy online public opinion report.
As a process D 44/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 44/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 404 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 671: enough signal without eating the budget
- +4Structure: 8 headings
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.