BD modis-product-search
Comprehensive local query tool for NASA MODIS satellite products. Covers 46 products across 13 categories with bilingual (Chinese/English) descriptions, algorithm principles, band information, Google Earth Engine integration, and download information.
Comprehensive local query tool for NASA MODIS satellite products.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokendata/products.json:1171High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"name": "BRDF…nd1", "dtype": "UInt8", "scale": 1, "description": "Band 1 BRDF quality", "description_cn": "波段1 BRDF质量"},quoted -
low Secrets in code
secret-high-entropy-tokendata/products.json:1172High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"name": "BRDF…nd2", "dtype": "UInt8", "scale": 1, "description": "Band 2 BRDF quality", "description_cn": "波段2 BRDF质量"},quoted -
low Exfiltration
net-credential-usescripts/modis_products.py:346Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)lines.append(f' wget --user {u} --password "$EARTHDATA_PASSWORD" "{product.get("download_url", "URL")}"')quoted
Files scanned: 21. 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")
Process rating: all ten parameters 46/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, python) that frontmatter does not declare
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1841 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 251: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (10 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.