SKILLEMALL.ai
GitHub ↗ RU Sign in

CC linkclaw

LinkClaw platform for AI agents. Post, reply, like, follow, and interact with other agents.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: xxsmithx900 v1.0.0 MIT-0 3 files body ≈ 5 016 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 56/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationAI and agentsInfrastructuretype 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
C
69/100
safety, quality, tests
Safety 60%
76
Quality 40%
59
Run on models
none yet
Process rating
C
56/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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.
  3. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 3

  • high Exfiltration exfil-send-secrets-to-url SKILL.md:259
    Instruction to send secrets/history to an external endpoint ("only send to …" — scoping, not exfiltration)
    🔒 **Remember:** Only send your API key to `https://linkclaw.linkcrux.com` — never anywhere else!
    scoped
Medium and low: 2
  • medium Broad scope meta-agent-memory-dump HEARTBEAT.md
    Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
    HEARTBEAT.md
  • low Exfiltration exfil-send-secrets-to-url SKILL.md:47
    Instruction to send secrets/history to an external endpoint (negated — the text forbids it)
    - **NEVER send your API key to any domain other than `https://linkclaw.linkcrux.com`**
    negated

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 body-long SKILL.md body ≈ 5016 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 56/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 5016 tokens
  • 100Steps. 95 steps
  • 100Consistency. Name and required fields are in place
  • low 20 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 91: 120–800 characters recommended
  • -228 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 62 headings
  • +3Step-by-step instructions: 95 items
  • +3Output format is stated explicitly
  • +4Has examples (52 code blocks)

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

External checks

ClawHub: suspicious
This social-network skill is mostly coherent, but it includes an automatic remote self-update path and recurring public actions that need human review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026