SKILLEMALL.ai

CC flomo-to-obsidian

Parse and sync flomo exported HTML data to Obsidian vault with attachment support. Supports one-time manual export conversion and automatic sync. Use when users want to import flomo notes, convert flomo to markdown, or set up automatic sync.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: 月开 v2.0.0 MIT-0 31 files · 7 scripts body ≈ 2 016 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorObsidianInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
68
Quality 40%
73
Run on models
none yet
Process rating
C
55/100
Has gaps
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.
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 · 15

  • high Dangerous commands cmd-persistence setup.sh:158
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null || echo ""; echo "$CRON_LINE") | crontab -
Medium and low: 14
  • low Dangerous commands cmd-cron-mention AUTO_SYNC.md:145
    Mentions editing / listing crontab
    crontab -e
  • low Exfiltration read-dotenv AUTO_SYNC.md:278
    Reads a .env file
    source .env
  • low Exfiltration read-dotenv PRIVACY_CHECK.md:90
    Reads a .env file
    cp .env.example .env.example  # 如果还没有
  • low Dangerous commands cmd-cron-mention README.md:277
    Mentions editing / listing crontab
    crontab -l | grep flomo
  • low Exfiltration read-dotenv SETUP_GUIDE.md:28
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv SETUP_GUIDE.md:208
    Reads a .env file
    cat .env
  • low Exfiltration read-dotenv SETUP_GUIDE.md:280
    Reads a .env file
    source .env
  • low Dangerous commands cmd-cron-mention SETUP_GUIDE.md:307
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention setup.sh:158
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null || echo ""; echo "$CRON_LINE") | crontab -
  • low Dangerous commands cmd-cron-mention setup.sh:162
    Mentions editing / listing crontab
    crontab -l | grep flomo
  • low Dangerous commands cmd-cron-mention SKILL.md:336
    Mentions editing / listing crontab
    crontab -l > /tmp/crontab_backup
  • low Exfiltration read-dotenv sync.sh:14
    Reads a .env file (quoted — discussed, not commanded)
    echo "  1. 复制模板: cp .env.example .env"
    quoted
  • low Exfiltration read-dotenv sync.sh:23
    Reads a .env file
    source .env
  • low Dangerous commands cmd-cron-mention USAGE_GUIDE.md:271
    Mentions editing / listing crontab
    crontab -e

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

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "cn_name"
  • note frontmatter-key unknown frontmatter key "cn_description"

Process rating: all ten parameters 55/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
  • 100Tools and files. No external tools needed
  • 100Steps. 106 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2016 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 13 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
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -242 emoji in the instructions: noise for the model
  • -32 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 241: enough signal without eating the budget
  • +4Structure: 48 headings
  • +3Step-by-step instructions: 106 items
  • +4Has examples (18 code blocks)

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

External checks

ClawHub: suspicious
This appears to be a real Flomo-to-Obsidian sync tool, but it needs review because it handles passwords/session data and can create ongoing sync jobs with misleading safety wording.
LLM: suspicious (high) · VirusTotal: · 29 May 2026