SKILLEMALL.ai

AC public-opinion-insights

调用 Midu 舆情分析接口,针对指定主体进行指定维度的舆情分析。分析维度包括:['事件概况', '事件进程', '信息总量', '传播速度', '热搜情况', '跨平台传播', '媒体报道情况', 'KOL参与情况', '传播层级', '热门信息', '情绪烈度', '媒体观点分析', 'KOL观点分析', '网民观点分析', '行业专家观点分析', 'AI虚假信息识别', '已认定谣言传播', '研判建议', '活跃作者', '地域分布图', '关键词云', '信息来源分布', '全网信息走势图', '敏感信息占比', '事件盘点', '网民反馈情况', '分职能信息传播情况', '分区域信息传播情况', '总量', '环比', '占比/分布', '同比', '舆论诉求分析', '观点指向分析', '观点倾向指向分析', '同类案例', '关键传播节点', '溯源分析', '应对效果评估', '热度指数', '热度指数排行', '关键词方案'] Call the Midu public opinion insights API for public-opinion analysis.

ClawHub Agent Skills author: bitallin v0.0.1 MIT-0 6 files body ≈ 379 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
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 54/100

  • 0Result and completion. Does not say what the result is
  • 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 (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 379 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 501: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill appears to use a remote analysis service, but its handling of API keys and user-provided text is under-disclosed enough to merit review before install.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026