SKILLEMALL.ai
GitHub ↗ RU Sign in

DD core-capabilities

工作助手核心能力集成包 - 包含 Obsidian/Git 同步、记忆数据库、自然语言查询工具、监控页面等完整能力。提供 memory_query_agent.py 工具和完整文档。

Not recommendedcritical or high security findings · low grade D
ClawHub Agent Skills author: awublack v2.0.1 MIT-0 7 files · 3 scripts body ≈ 163 tokens Open the sourceclawhub.ai↗ analyzed 5 d ago

工作助手核心能力集成包 - 包含 Obsidian/Git 同步、记忆数据库、自然语言查询工具、监控页面等完整能力。提供 memoryqueryagent.py 工具和完整文档。

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

ProcedureObsidianData and analyticstype 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
D
60/100
safety, quality, tests
Safety 60%
54
Quality 40%
69
Run on models
none yet
Process rating
D
49/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

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 8

  • high Dangerous commands cmd-persistence setup_cron.sh:19
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null | grep -v "memory_query_agent.py" | grep -v "memory_to_sqlite.py"; \
  • high Dangerous commands cmd-persistence setup_cron.sh:20
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    echo "*/30 * * * * cd $SCRIPT_DIR && python3 $PYTHON_SCRIPT --sync-now >> $LOG_FILE 2>&1") | crontab -
Medium and low: 6
  • medium Dangerous commands cmd-eval-dynamic monitor_server.py:64
    Dynamic code execution from decoded/untrusted input
    os.system(f"cd {WORKSPACE} && python3 cron_monitor.py > /dev/null 2>&1")
  • low Dangerous commands cmd-cron-mention setup_cron.sh:14
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "memory_query_agent.py"; then
  • low Dangerous commands cmd-cron-mention setup_cron.sh:16
    Mentions editing / listing crontab
    crontab -l | grep "memory_query_agent"
  • low Dangerous commands cmd-cron-mention setup_cron.sh:19
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null | grep -v "memory_query_agent.py" | grep -v "memory_to_sqlite.py"; \
  • low Dangerous commands cmd-cron-mention setup_cron.sh:28
    Mentions editing / listing crontab
    crontab -l 2>/dev/null || echo "（无定时任务）"
  • low Dangerous commands cmd-cron-mention setup_cron.sh:33
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "  查看任务：crontab -l"
    code literal

Files scanned: 7. 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 49/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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (core-capabilities) differs from the folder (core-capabilities-v2)
  • 100Tools and files. No external tools needed
  • 100Steps. 10 steps
  • 100Execution cost. Instruction body is 163 tokens
  • 100Running it twice. No mutating operations

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

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

External checks

ClawHub: suspicious
This skill is a plausible local memory/query tool, but it exposes memory data over an unauthenticated web server and installs persistent cron execution with weak controls.
LLM: suspicious (high) · VirusTotal: · 16 Sept 2026