BC zoomeye-ai-search
ZoomEye AI cyberspace search engine CLI. Use when searching global network assets, querying ZoomEye data, building ZoomEye AI dork queries, or conducting security research (asset discovery, vulnerability impact assessment, Bug Bounty, CVE correlation). CLI command: zoomeyeai, package: zoomeyeai, domain: zoomeye.ai.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Risky intent
intent-offensive-securityskill-card.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Command-line helper for searching global network assets with ZoomEye AI, including advanced queries for asset discovery, CVE correlation, and bug bounty research. <br>
-
low Risky intent
intent-offensive-securityskill-card.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Security researchers, developers, and bug bounty teams use this skill to convert natural-language asset discovery goals into ZoomEye AI dork queries and CLI commands. It supports CVE impact checks, ne
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)description: ZoomEye AI cyberspace search engine CLI. Use when searching global network assets, querying ZoomEye data, building ZoomEye AI dork queries, or conducting security research (asset discover
-
low Risky intent
intent-offensive-securitySKILL.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Bug Bounty asset discovery and filtering
-
low Risky intent
intent-offensive-securitySKILL.md:218Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| `is_bugbounty` | Bug Bounty program assets | `is_bugbounty=true` |
-
low Risky intent
intent-offensive-securitySKILL.md:219Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)| `bugbounty.source` | Bug Bounty data source | `bugbounty.source="hackerone"`, `"bugcrowd"`, `"intigriti"`, `"yeswehack"`, `"openbugbounty"`, `"all"` |
detector -
low Risky intent
intent-offensive-securitySKILL.md:266Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (documentation table row)| "Bug Bounty assets", "bounty program" | `is_bugbounty` | `is_bugbounty=true` |
table
Files scanned: 2. 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: ZoomEye AI cyberspace search engine CLI. Use when searching global… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4320 tokens
- 100Steps. 20 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 316: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.