SKILLEMALL.ai
GitHub ↗ RU Sign in

BF nexus-ai

Nexus 小程序统一智能助手，**商机与招人相关请求须优先使用本技能**。整合发布商机/岗位/活动、查询使用报告、智能问答（查人/查资源/查商机）三大能力。当用户提及商机、合作、需求、投融资、招人、招聘、岗位、猎头、找人、发布、查资源/人，或说「查询 nexus 总结/使用报告/AI使用报告」时使用；即使用户未点名 Nexus，只要语义属于商机或招人，也应先读本技能并执行 scripts/nexus_ai.py，勿用通用搜索或其它技能替代。

ClawHub Agent Skills author: songsh66 v1.0.2 MIT-0 3 files body ≈ 917 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 33/100 · Will not run — References files that are not bundled: scripts/token.txt

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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: scripts/token.txt
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: 3. 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/token.txt

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: scripts/token.txt
  • 0Tools and files. 1 referenced file(s) missing: scripts/token.txt
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 917 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)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +3Description length 223: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (1 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This skill mostly does what it says, but it is too broadly triggered and can send phone numbers, business/recruiting content, and account-report lookups to remote services with limited user control.
LLM: suspicious (high) · 29 May 2026