SKILLEMALL.ai
GitHub ↗ RU Sign in

BF graphify

✏️ 小龙的 Graphify 知识图谱管理工具。使用本地 Llama.cpp (Qwen3.5-9B) 作为推理后端，完全免费，MIT-0 许可。

ClawHub Agent Skills author: peing111 v1.0.0 MIT-0 2 files body ≈ 703 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 31/100 · Will not run — References files that are not bundled: ~/.workbuddy/projects/knowledge-graph/

ReferenceInfrastructuretype 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
F
31/100
Will not run
References files that are not bundled: ~/.workbuddy/projects/knowledge-graph/
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. 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: 2. 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: ~/.workbuddy/projects/knowledge-graph/
  • note frontmatter-key unknown frontmatter key "owner"
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: ~/.workbuddy/projects/knowledge-graph/
  • 0Tools and files. 1 referenced file(s) missing: ~/.workbuddy/projects/knowledge-graph/
  • 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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (graphify) differs from the folder (graphify-source)
  • 100Steps. 26 steps
  • 100Execution cost. Instruction body is 703 tokens
  • 100Running it twice. No mutating operations

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)
  • +3Description length 74: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • -220 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (8 code blocks)

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

External checks

ClawHub: suspicious
Graphify appears to be a legitimate knowledge-graph skill, but its local-only claims conflict with instructions that require external LLM API keys for semantic extraction of code and documents.
LLM: suspicious (high) · VirusTotal: · 29 May 2026