BD scholar-access
通过中国教育网官方学术通道（scholar.edu.cn / scholar.work，即官方学术浏览器 scholartools 所使用的智能 DNS + 反向代理）访问 GitHub、HuggingFace、Docker Hub、Google Scholar、Wikipedia 等境外学术资源，让任何 Agent 无需翻墙即可合规访问。Routes blocked academic sites through the official CERNET "Scholar" reverse proxy used by the official scholartools academic-browser client — compliant, VPN-free access for any Agent.
通过中国教育网官方学术通道（scholar.edu.cn / scholar.work，即官方学术浏览器 scholartools 所使用的智能 DNS + 反向代理）访问 GitHub、HuggingFace、Docker Hub、Google Scholar、Wikipedia 等境外学术资源，让任何…
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
-
low Dangerous commands
cmd-background-processSKILL.md:63Starts a background / autostarted processnohup ./scholar-proxy.py --listen 127.0.0.1:1080 > /tmp/scholar-proxy.log 2>&1 &
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") - note
frontmatter-keyunknown frontmatter key "whenToUse"
Process rating: all ten parameters 42/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
- 60Tools and files. Uses tools (web, git) that frontmatter does not declare
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1215 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 354: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.