SKILLEMALL.ai

CD daily-literature

Automated daily literature search system for academic researchers. Performs scheduled searches across PubMed, OpenAlex, and Semantic Scholar with automatic deduplication, OA download, smart categorization, and daily reports.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: Wzr101622 v1.0.0 MIT-0 11 files · 1 script body ≈ 1 499 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ProcedureData and analyticsInfrastructureResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
71/100
safety, quality, tests
Safety 60%
75
Quality 40%
66
Run on models
none yet
Process rating
D
38/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 install.sh:164
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null | grep -v "daily_literature_search.py") | crontab -
Medium and low: 7
  • low Dangerous commands cmd-cron-mention install.sh:164
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null | grep -v "daily_literature_search.py") | crontab -
  • low Dangerous commands cmd-cron-mention install.sh:169
    Mentions editing / listing crontab
    crontab -l 2>/dev/null | grep -v "daily_literature_search.py" > "$TEMP_CRON" || true
  • low Exfiltration read-dotenv install.sh:186
    Reads a .env file (code comment)
    # Edit this file and run: source .env
    comment
  • low Exfiltration read-dotenv install.sh:265
    Reads a .env file (detector / deny-list definition)
    echo "2. Edit .env file and run: source .env"
    detector
  • low Exfiltration read-dotenv README.md:25
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv README.md:27
    Reads a .env file
    source .env
  • low Dangerous commands cmd-cron-mention README.md:46
    Mentions editing / listing crontab
    crontab -l | grep daily_literature

Files scanned: 10. 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")
  • note frontmatter-key unknown frontmatter key "requirements"
  • note frontmatter-key unknown frontmatter key "env_vars"

Process rating: all ten parameters 38/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. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (daily-literature) differs from the folder (daily-literature-search)
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 85Steps. 43 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1499 tokens
  • 100Progress reporting. Reports progress
  • low 12 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)
  • +3Output format is not stated: the model decides each time
  • -212 emoji in the instructions: noise for the model
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 224: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 43 items
  • +4Has examples (10 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This appears to be a real literature-monitoring skill, but it needs review because installation adds recurring background execution and the search script runs another local skill that is not clearly declared as a dependency.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026