SKILLEMALL.ai
GitHub ↗ RU Sign in

BC daily-briefing

Structured morning briefing skill — daily summaries covering calendar, tasks, weather, news, and priorities. Supports cron, heartbeat, and on-demand triggers.

ClawHub Hermes author: Clawdssen v1.0.0 3 files body ≈ 1 655 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

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

ProcedurePersonal productivityInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent Cursor
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ClawHub

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 158 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "url"

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (daily-briefing) differs from the folder (agentledger-daily-briefing)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 17 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1655 tokens

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
  • +2Single-language instructions
  • +3Description length 158: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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

External checks

ClawHub: clean
This is a transparent daily-briefing instruction skill, but it can summarize private planning data and send it to configured chat channels if the user enables those sources.
LLM: benign (high) · VirusTotal: · 29 May 2026