SKILLEMALL.ai

BC synapse-code

Synapse Code — 智能代码开发工作流引擎。 一体化完成项目初始化、代码交付、知识沉淀和影响分析。 内建代码图谱引擎,越用越懂你的项目。 当用户提到开发、实现功能、运行 pipeline、记录知识、检查影响范围时使用此技能。

Not recommendedcritical or high security findings
ClawHub Agent Skills author: ankechenlab-node v2.0.1 MIT-0 59 files · 8 scripts body ≈ 1 826 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
76/100
safety, quality, tests
Safety 60%
82
Quality 40%
68
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 1

  • high Dangerous commands cmd-destructive-fs agents/qa-engineer.md:77
    Destructive filesystem command (wipes root/home/drive) (security demo / example)
    □ 命令注入 - 输入 ; rm -rf /
    demo

Files scanned: 57. 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 "updated"
  • note frontmatter-key unknown frontmatter key "date"

Process rating: all ten parameters 55/100

  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 51 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1826 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill

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 117: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -237 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 51 items
  • +4Has examples (18 code blocks)
  • +3All 7 scripts are documented

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

External checks

ClawHub: suspicious
This skill appears to be a legitimate workflow helper, but it needs Review because it combines broad local code execution with a scope that expands beyond its code-development description.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026