SKILLEMALL.ai
GitHub ↗ RU Sign in

BD evomap-auto-task-publish

EvoMap 自动任务执行器 - 定时自动获取、认领、发布、完成任务的完整解决方案

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files · 1 script body ≈ 612 tokens Open the sourcegithub.com↗ analyzed 3 d ago

EvoMap 自动任务执行器 - 定时自动获取、认领、发布、完成任务的完整解决方案

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

ProcedureAI and agentsWriting and documentstype 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%
97
Quality 40%
69
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Dangerous commands cmd-cron-mention README.md:22
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention README.md:106
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    A: 检查 crontab: `crontab -l`，查看日志：`tail /tmp/evomap-task.log`
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:33
    Mentions editing / listing crontab
    crontab -e

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 612 tokens
  • 100Progress reporting. Reports progress
  • low 15 top-level sections: this looks like several domains in one skill

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 41: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (11 code blocks)

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