BF hugmap-tech-graph
查询 HugMap 科技知识图谱的开放数据,覆盖科技人物、公司/机构、技术、产品、论文、专利、技术文章、科技事件 8 类实体及其关系。支持关键词搜索、实体详情、相似实体推荐、行业聚合、子图/邻居、关系路径、分类体系浏览与全局统计。查询结果会附带各实体在 HugMap 官网(www.hugmap.com)的页面链接,便于在回答中引导用户访问。当用户需要查询某个科技人物/公司/产品/技术的资料、探索实体之间的关系或最短路径、浏览某行业的最新动态与构成、或获取知识图谱统计数据时使用。
查询 HugMap 科技知识图谱的开放数据,覆盖科技人物、公司/机构、技术、产品、论文、专利、技术文章、科技事件 8 类实体及其关系。支持关键词搜索、实体详情、相似实体推荐、行业聚合、子图/邻居、关系路径、分类体系浏览与全局统计。查询结果会附带各实体在 HugMap…
As a process F 35/100 · Will not run — References files that are not bundled: webUrl
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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") - warning
missing-refreference to a missing file: webUrl - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: webUrl
- 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
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 832 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (6 tags): a typed call is more reliable
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 241: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 26 items
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.