SKILLEMALL.ai
GitHub ↗ RU Sign in

BF Idle Ping — Proactive Outreach System

Install a complete proactive outreach system — idle detection, randomized dice delivery, topic-driven crawler, share queue, and persona-based messages. Use when the user wants the agent to proactively reach out with interesting content during idle time.

ClawHub Agent Skills author: Leslie v1.0.1 MIT-0 20 files · 5 scripts body ≈ 486 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Install a complete proactive outreach system — idle detection, randomized dice delivery, topic-driven crawler, share queue, and persona-based messages.

As a process F 36/100 · Will not run — References files that are not bundled: scripts/idle-ping.env.example

AnalyzerSales and CRMInfrastructureAI and agentstype 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
F
36/100
Will not run
References files that are not bundled: scripts/idle-ping.env.example
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: 20. 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 missing-ref reference to a missing file: scripts/idle-ping.env.example
  • note frontmatter-key unknown frontmatter key "slug"

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: scripts/idle-ping.env.example
  • 0Tools and files. 1 referenced file(s) missing: scripts/idle-ping.env.example
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 6 mutating operations with no state check
  • 40Consistency. Frontmatter name (Idle Ping — Proactive Outreach System) differs from the folder (idle-ping)
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 19 steps
  • 100Execution cost. Instruction body is 486 tokens
  • 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

  • +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
  • +4No input/output examples
  • -31 of 7 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 253: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 19 items
  • +1License stated

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

External checks

ClawHub: suspicious
This skill appears purpose-built for proactive outreach, but it installs persistent automation that reads local session/persona context and sends Telegram messages, with enough control and validation gaps to require Review before installation.
LLM: suspicious (high) · 29 Aug 2026