SKILLEMALL.ai

AC kimi-use

Two scopes: (1) drives Kimi.app via computer-use for Work/Agent data-plugin queries (天眼查、同花顺 iFinD、SEC、IMF etc.) and Chat's built-in 深度研究 report; (2) kimi-cu macOS desktop-automation playbook — AX set_value / keyboard / click channel selection, foregrounding, AX-tree recovery, form & dialog recipes. Use for "用 Kimi 查" / "操作 Kimi 客户端" / "Kimi 插件" / "Kimi 深度研究" / driving any macOS desktop app (Electron/webview/native) via kimi-cu. Not for kimi.com browser automation (use kimi-webbridge) or direct iFinD API access.

daymade/claude-code-skills Agent Skills author: daymade MIT 5 files body ≈ 1 550 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Two scopes: (1) drives Kimi.app via computer-use for Work/Agent data-plugin queries (天眼查、同花顺 iFinD、SEC、IMF etc.) and Chat's built-in 深度研究 report; (2) kimi-cu…

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureAI and agentsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 59/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 23 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1550 tokens

    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

    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 517: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 23 items
    • +4Reference files are cited in the instructions (4 of 4)

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