SKILLEMALL.ai
RU Sign in

BB conversation-analyzer

Intelligent conversation analysis, summarization, and conclusion recording. Analyzes user personality, tracks tasks, checks incomplete tasks, and writes to memory files.

ClawHub Agent Skills author: jason-tiger v1.0.0 MIT-0 8 files body ≈ 1 019 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process B 70/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting

AnalyzerInfrastructuretype 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
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
72
Run on models
none yet
Process rating
B
70/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
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
  • low Dangerous commands cmd-cron-mention README.md:46
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention README.md:149
    Mentions editing / listing crontab
    crontab -e

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")
  • note frontmatter-key unknown frontmatter key "source"

Process rating: all ten parameters 70/100

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

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

External checks

ClawHub: suspicious
This skill is a disclosed productivity tool, but it repeatedly profiles conversations, writes long-term memory, and may send task details to Feishu without enough user control.
LLM: suspicious (high) · VirusTotal: · 29 May 2026