DD muguozi1-openclaw-feishu-calendar
(no description)
Not recommendedlow grade D
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ReferencePersonal productivityInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:18High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…bR6+k7Fi…rEB/8rLw…bbj/Mp8TWH/v1O+p487m6xskxw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:33High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-j+gKEx…ahh+s1F2HZ+wAce…RkU++ZWQr…uoQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:79High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…rvP+yUUf…4tH/iSSo…tEA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:97High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…vPe+zGay…l5w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:106High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 555 tokens
- low 11 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This Feishu calendar skill matches its calendar-management purpose, but it includes under-disclosed scripts that can delete, create, share, and locally persist calendar data without strong user safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026