SKILLEMALL.ai
GitHub ↗ RU Sign in

BD dingtalk-log

支持发送和查询钉钉日报/周报，可对工作质量总结与评分。

ClawHub Agent Skills author: bigint1 v0.9.4 MIT-0 8 files body ≈ 1 530 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 36/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
D
36/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

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

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "dependency"
  • note frontmatter-key unknown frontmatter key "credentials"

Process rating: all ten parameters 36/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (dingtalk-log) differs from the folder (dingtalk-daily)
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 80 steps
  • 100Execution cost. Instruction body is 1530 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

  • +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 27: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 80 items
  • +4Has examples (9 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 5 scripts are documented

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

External checks

ClawHub: suspicious
This DingTalk report skill matches its stated purpose, but it gives an agent broad company-report and employee-ID access without clear authorization boundaries.
LLM: suspicious (high) · VirusTotal: · 29 May 2026