AC gis-site-suitability-analysis
Use this skill when a GIS analyst, urban planner, environmental consultant, or site selection professional needs to draft a multi-criteria site suitability analysis (MCSA) report documenting spatial data layers, weighting rationale, analysis methodology, and results interpretation. Covers criteria definition, weighted overlay or Boolean screening, data source documentation, and a defensible methodology narrative. Produces a DRAFT report for analyst and stakeholder review.
Use this skill when a GIS analyst, urban planner, environmental consultant, or site selection professional needs to draft a multi-criteria site suitability…
As a process C 63/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 85Steps. 16 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1616 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 476: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.