SKILLEMALL.ai
GitHub ↗ RU Sign in

BF cyber-girlfriend

Build or customize an owner-only proactive companion system with a cyber-girlfriend persona, Markdown private-life context, lightweight relationship memory, and OpenClaw presence cron delivery.

ClawHub Agent Skills author: XieJiaQi v2.2.0 MIT-0 27 files body ≈ 3 451 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 58/100 · Will not run — References files that are not bundled: scripts/companion_ping.py

GeneratorInfrastructuretype 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
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
F
58/100
Will not run
References files that are not bundled: scripts/companion_ping.py
Tools and files w 18
0
Result and completion w 14
0
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.
  2. 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: 27. 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 missing-ref reference to a missing file: scripts/companion_ping.py

Process rating: all ten parameters 58/100

Will not run. References files that are not bundled: scripts/companion_ping.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/companion_ping.py
  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 39 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 55 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3451 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • -33 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 193: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 55 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (11 of 11)

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

External checks

ClawHub: suspicious
The skill mostly matches its proactive companion purpose, but it should be reviewed because it can run scheduled outbound messages and use local OpenClaw/WeChat session or credential data for delivery.
LLM: suspicious (medium) · VirusTotal: · 3 Sept 2026