SKILLEMALL.ai

AC consulting-report-search

Consulting and industry report search and QA skill that prioritizes iResearch free reports. Use for consulting report search, industry report QA, iResearch report lookup, and market research report search.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 4 files body ≈ 4 930 tokens Open the sourcegithub.com analyzed 2 d ago

Consulting and industry report search and QA skill that prioritizes iResearch free reports.

As a process C 61/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 113, 149): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 61/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 4 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4930 tokens
    • 85Steps. 102 steps, 2 vague phrases
    • 100Failures and branches. 9 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • low 14 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    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 205: enough signal without eating the budget
    • +4Structure: 35 headings
    • +3Step-by-step instructions: 102 items
    • +4Has examples (16 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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