SKILLEMALL.ai

BD obsidian-inbox-pipeline

将任意来源(AI 资讯、经济雷达、旅游日报、RSS、文章)自动采集、 结构化写入 Obsidian inbox 的完整流水线。支持 Telegram / 飞书推送 和 cron 定时执行。一套配置,永久自动沉淀知识。

ClawHub Agent Skills author: simo v1.0.1 MIT-0 7 files · 1 script body ≈ 949 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ProcedureObsidianTelegramInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
97
Quality 40%
72
Run on models
none yet
Process rating
D
46/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 Exfiltration exfil-webhook-url scripts/daily_pipeline.sh:92
    Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
    f"https://api.telegram.org/bot{token}/sendMessage",
    vendor-hostquoted
  • low Exfiltration read-dotenv SKILL.md:31
    Reads a .env file
    cp references/.env.example .env
  • low Exfiltration read-dotenv SKILL.md:156
    Reads a .env file
    source /path/to/.env && \

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 46/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
  • 60Tools and files. Uses tools (python, node) that frontmatter does not declare
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 949 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 108: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (9 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This Obsidian automation skill is mostly transparent, but its daily pipeline can automatically run code from outside the reviewed skill and handle sensitive vault content, so it should be reviewed before use.
LLM: suspicious (high) · VirusTotal: benign · 28 May 2026