SKILLEMALL.ai
GitHub ↗ RU Sign in

BB ai-meeting-notes

Messy notes → Clear action items. Instantly. Paste any meeting notes, transcript, or text. Get summaries, action items with owners and deadlines. Auto-saved, searchable, with integrated to-do tracking. No bot. No subscription. No setup.

ClawHub Agent Skills author: Jeff J Hunter v1.0.3 7 files body ≈ 5 853 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 76/100 · Nearly there — weak spots: progress reporting

IntegrationPersonal 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
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
B
76/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
50
Result and completion w 14
60
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. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 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")
  • warning body-long SKILL.md body ≈ 5853 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 76/100

  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 10 branches
  • 70Execution cost. Instruction body is 5853 tokens
  • 85Steps. 154 steps, 2 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 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)
  • -5TODO / placeholder text left in the skill
  • -235 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 236: enough signal without eating the budget
  • +4Structure: 44 headings
  • +3Step-by-step instructions: 154 items
  • +3Output format is stated explicitly
  • +4Has examples (20 code blocks)

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

External checks

ClawHub: suspicious
This meeting-notes skill is useful and mostly purpose-aligned, but it stores complete raw meeting content by default while also claiming nothing is stored.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026