SKILLEMALL.ai
GitHub ↗ RU Sign in

BD diary

全天候思考搭子与日记记录系统。智能记录用户的想法、文章讨论和协作任务。 **立即触发当**：用户说「记一下」「记录」「写日记」「journal」「日记」，或分享文章/想法/经历时。 **主动询问当**：用户随口说"今天发生了什么""我在想一个事""刚才""今天"等时间线索，或分享链接/文章时。 支持本地存储和飞书/Flomo/Notion多平台同步。双人设模式（INTJ分析型/ENFP温暖型）。 即使用户只是随便聊天提到"今天"、"刚才"、"我在想"这类词，也要敏感地询问是否需要记录。不要等用户明确说"记一下"才行动。

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

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

ReferenceNotionPersonal productivityInfrastructuretype 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
B
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
73
Run on models
none yet
Process rating
D
41/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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:308
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - 使用 `mcp_…ent` 获取文档当前内容
    quoted

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 41/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 (diary) differs from the folder (openclaw-diary-core)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 141 steps
  • 100Execution cost. Instruction body is 1639 tokens
  • 100Running it twice. No mutating operations
  • low 14 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

  • +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
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 265: enough signal without eating the budget
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 141 items
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: clean
This is a disclosed diary skill that persistently records personal journal content, with optional external sync, so it is privacy-sensitive but not deceptive or malicious.
LLM: benign (high) · VirusTotal: · 29 May 2026