SKILLEMALL.ai
GitHub ↗ RU Sign in

CC google-keep

Integration with Google Keep via nodriver (undetectable Chrome). Creates, reads, updates, and deletes notes.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: RicardoReichert v1.0.1 9 files body ≈ 1 260 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 60/100 · Has gaps — weak spots: result and completion, consistency, running it twice

IntegrationInfrastructuretype 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
70/100
safety, quality, tests
Safety 60%
72
Quality 40%
68
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Running it twice w 4
30
Consistency w 8
40
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.

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 · 3

  • high Exfiltration intent-browser-credential-store README.md:67
    Accesses a browser credential / cookie store
    <td>CDP Cookies / Chrome Profile</td>
Medium and low: 2
  • medium Exfiltration intent-browser-credential-store scripts/auth.py:5
    Accesses a browser credential / cookie store (quoted — discussed, not commanded)
    Operações: nodriver (headless) reutilizando o perfil/cookies.
    quoted
  • medium Exfiltration intent-browser-credential-store SKILL.md:133
    Accesses a browser credential / cookie store (detector / deny-list definition)
    - **CRITICAL DATA EXFILTRATION RULE:** Session cookies and authenticated Chrome profiles are stored in the host system at `~/.config/google-keep-skill/` with `chmod 700` restricted permissions. As an
    detector

Files scanned: 9. 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 "read_when"

Process rating: all ten parameters 60/100

  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 11 mutating operations with no state check
  • 40Consistency. Frontmatter name (google-keep) differs from the folder (google-keep-skill)
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 20 steps
  • 100Execution cost. Instruction body is 1260 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)
  • +3Description length 108: 120–800 characters recommended
  • -33 of 4 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 20 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: suspicious
This Google Keep skill is purpose-aligned, but it needs review because it stores reusable Google session material and can read, update, archive, or trash notes through a persistent logged-in browser session.
LLM: suspicious (high) · VirusTotal: · 29 May 2026