SKILLEMALL.ai
RU Sign in

AB deep-research-official

Delegate a full investigation to Genspark's specialized Deep Research agent the way a senior research analyst scopes one — clarify the question, hand it off, then return a cited, structured report. Trigger when the user asks to "deep research X", "do a deep dive on X", "research X in depth", "write a comprehensive report on X", "investigate X thoroughly", or "continue the deep research". This runs the backend deep_research task (multi-source web search, Google Scholar, crawling, financial data, synthesis) rather than improvising the research yourself; never fabricate findings or citations.

genspark Agent Skills author: Genspark 1 file body ≈ 1 515 tokens Open the sourcegenspark.ai↗ analyzed 2 d ago

As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, running it twice

AnalyzerData and analyticsSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Genspark Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
B
77/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

    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 · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "triggers"

    Process rating: all ten parameters 77/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 25 steps
    • 100Failures and branches. 4 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1515 tokens
    • 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 596: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 25 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.