SKILLEMALL.ai

AF phoenixclaw

Passive journaling skill that scans daily conversations via cron to generate markdown journals using semantic understanding. Use when: - User requests journaling ("Show me my journal", "What did I do today?") - User asks for pattern analysis ("Analyze my patterns", "How am I doing?") - User requests summaries ("Generate weekly/monthly summary")

modbender/skill-library-mcp Agent Skills author: modbender MIT 16 files body ≈ 3 207 tokens Open the sourcegithub.com analyzed 2 d ago

Passive journaling skill that scans daily conversations via cron to generate markdown journals using semantic understanding.

As a process F 45/100 · Will not run — References files that are not bundled: assets/YYYY-MM-DD/

GeneratorObsidianPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: assets/YYYY-MM-DD/
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/YYYY-MM-DD/

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: assets/YYYY-MM-DD/
  • 0Tools and files. 1 referenced file(s) missing: assets/YYYY-MM-DD/
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 85Steps. 60 steps, 3 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3207 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 347: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (8 of 8)
  • +3All 1 scripts are documented

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