BF qgis-agent
Drive QGIS's 1000+ Processing algorithms (vector geoprocessing, raster & terrain analysis, interpolation, network analysis, format conversion, map rendering) from any AI agent over plain HTTP. Architecture: Agent --HTTP--> scripts/server.py (PyQGIS) --> QGIS 3.28+/4.x. 驱动本机 QGIS 的 1000+ Processing 算法，让 AI 智能体通过纯 HTTP 直接执行空间分析。
Drive QGIS's 1000+ Processing algorithms (vector geoprocessing, raster & terrain analysis, interpolation, network analysis, format conversion, map rendering)…
As a process F 43/100 · Will not run — References files that are not bundled: scripts/start_server.bat
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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Drive QGIS's 1000+ Processing algorithms (vector geoprocessing, ra… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/start_server.bat
Process rating: all ten parameters 43/100
- 0Tools and files. 1 referenced file(s) missing: scripts/start_server.bat
- 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
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 30 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2511 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 328: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (8 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: 61.