SKILLEMALL.ai

BC Supercharged Daily Briefing

Stop spending your mornings hunting for news, trends, and updates across a dozen tabs. The Supercharged Daily Briefing turns OpenClaw into a production-grade research team that discovers the best sources for YOUR interests, monitors them around the clock, and delivers a personalized executive summary every morning. You pick the topics — OpenClaw finds the signal, cuts the noise, and puts it right where you chat.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 13 files · 1 script body ≈ 4 577 tokens Open the sourcegithub.com analyzed 2 d ago

Stop spending your mornings hunting for news, trends, and updates across a dozen tabs.

As a process C 59/100 · Has gaps — weak spots: inputs and preconditions, consistency

ProcedureInfrastructureAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
74
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Consistency w 8
40
When it triggers w 12
50
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 · 2

✓ No critical or high findings

Medium and low: 2

✓ Guard found no suspicious behaviour. 2 matches are attack strings quoted in this security skill's own documentation.

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 59/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Consistency. Frontmatter name (Supercharged Daily Briefing) differs from the folder (normieclaw-daily-briefing)
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 4577 tokens
  • 100Steps. 101 steps
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 15 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)
  • +2Single-language instructions
  • +3Description length 415: enough signal without eating the budget
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 101 items
  • +3Output format is stated explicitly
  • +4Has examples (6 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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