SKILLEMALL.ai
GitHub ↗ RU Sign in

DD opys-calendar-skill

A local markdown-backed calendar with CLI and optional two-way Google Calendar sync.

Not recommendedcritical or high security findings · low grade D
ClawHub Agent Skills author: 21J3phy v0.1.2 22 files · 8 scripts body ≈ 881 tokens Open the sourceclawhub.ai↗ analyzed 14 d ago

A local markdown-backed calendar with CLI and optional two-way Google Calendar sync.

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationPersonal productivitytype 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
D
68/100
safety, quality, tests
Safety 60%
72
Quality 40%
63
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.

Broad scope
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.

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

  • high Broad scope meta-requests-env-secret SKILL.md:1
    Skill asks the runtime to inject credential env vars into its sandbox: GOOGLE_CLIENT_SECRET (high-value: GOOGLE_CLIENT_SECRET) — verify each one is needed for the stated purpose
    required_environment_variables: GOOGLE_CLIENT_SECRET
Medium and low: 6
  • medium Exfiltration net-redirectable-api-key server/index.ts:172
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • low Secrets in code secret-high-entropy-token package-lock.json:313
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…SzS+cfgl…B0A==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:327
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…7pY+zoMV…h0x/Ptw8…8dg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:344
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…b00+Gxjx…zRc/oZwU…hzA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:412
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:446
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…Dsc+j03S…0oA==",
    detector

Files scanned: 22. 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 "env"

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 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. 6 mutating operations with no state check
  • 40Consistency. Frontmatter name (opys-calendar-skill) differs from the folder (opys-calendar)
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 100Steps. 46 steps
  • 100Execution cost. Instruction body is 881 tokens
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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 84: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • -33 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 46 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
The skill matches its calendar-sync purpose, but it ships real-looking personal calendar data and exposes broad unauthenticated local mutation APIs, so it needs review before installation.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026