SKILLEMALL.ai

BC lark-cli-router

Routes any Feishu/Lark/Doubao operation, including recording lookup by date (按日期找会议录音), through the version-matched lark-cli domain guide embedded in the installed CLI, then executes and verifies the task. Use for 飞书/Lark/Doubao docs, drive, sheets, Base, wiki, minutes, meetings, calendar, IM, mail, tasks, approval, apps, auth/scope, resource URLs or tokens, and lark-cli troubleshooting. This is the single Lark entry point; use ima-copilot instead for Tencent IMA.

daymade/claude-code-skills Agent Skills author: daymade MIT 4 files · 1 script body ≈ 2 180 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Routes any Feishu/Lark/Doubao operation, including recording lookup by date (按日期找会议录音), through the version-matched lark-cli domain guide embedded in the…

As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationPersonal productivityData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
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 53): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 55/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2180 tokens
    • 100Running it twice. No mutating operations
    • 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
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 468: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 11 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)

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