SKILLEMALL.ai
GitHub ↗ RU Sign in

DB daily-update

Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron reminder. Use for daily or morning wiki refresh or scheduler setup and verification.

Not recommendedcritical or high security findings · low grade D
Ar9av/obsidian-wiki Agent Skills author: Ar9av MIT 1 file body ≈ 2 340 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron…

As a process B 66/100 · Nearly there — weak spots: result and completion, when it triggers

AnalyzerObsidianData and analyticsAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
D
77/100
safety, quality, tests
Safety 60%
76
Quality 40%
79
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
When it triggers w 12
20
Tools and files w 18
60
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.
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

  • high Dangerous commands cmd-persistence SKILL.md:147
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"
Medium and low: 2
  • medium Dangerous commands cmd-persistence SKILL.md:144
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    > "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:165
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    Anything else (no systemd, containers, WSL without systemd) — crontab. Append this line via `crontab -e`, skipping it if an `obsidian-wiki` daily-update line is already there:
    quoted

Files scanned: 1. 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 212): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 20 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2340 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 240: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (20 code blocks)

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