BC notion-diary
Write diary entries or short 24-hour reports in Chinese or English, then sync them into Notion using a user-supplied NOTION_API_KEY and the bundled Python script. Use when the user invokes /notion_diary, asks to write a diary with one of four preset styles, wants command-driven journal input, wants to authorize Notion by filling an API key, wants to sync diary text or photo notes into Notion, or wants a fallback short report generated from the last 24 hours of conversation when no diary was written today.
Write diary entries or short 24-hour reports in Chinese or English, then sync them into Notion using a user-supplied NOTIONAPIKEY and the bundled Python script.
As a process C 57/100 · Has gaps — References files that are not bundled: references/openclaw-config.example.jsonc
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/openclaw-config.example.jsonc - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 57/100
- 0Tools and files. 1 referenced file(s) missing: references/openclaw-config.example.jsonc
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 100Steps. 78 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2183 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 510: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.