BC aiseact
AI search enhancement tool. Prioritizes authoritative sources for research and fact-checking.
As a process C 53/100 · Has gaps — 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.
For the model run — optional
- 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 Obfuscation
obf-hex-escape-chainreferences/unreliable-sources.md:7Escaped/char-code string obfuscation (detector / deny-list definition)**Basis**: Ratings compiled from Wikipedia [Perennial Sources List](https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources), [维基百科可靠来源](https://zh.wikipedia.org/wiki/Wikipedia:%E5%
detector
Files scanned: 11. 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: Unexpected scalar at node end at line 4, column 25: - explicit: "aiseact" / "use aiseact" / "enhanced search" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); 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") - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 432 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)
- +3Description length 93: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (3 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.
External checks
ClawHub: suspicious
This is an instruction-only search-quality skill, but its registry summary and autonomous-mode guidance can make it affect searches more broadly than the main skill docs suggest.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026