BC google-workspace-byok
Google Calendar and Gmail integration using your own GCP project credentials (BYoK — Bring Your Own Key). Direct OAuth2 auth against your own Google Cloud project. Read calendars, events, and emails across multiple Google accounts. Use this skill when users want to check their calendar, read emails, or manage schedules. Supports: listing/reading emails, Gmail search queries, downloading attachments, extracting text from PDF attachments, listing calendars, listing/getting events, checking free/busy status, and managing multiple Google accounts.
Google Calendar and Gmail integration using your own GCP project credentials (BYoK — Bring Your Own Key).
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
- 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-tokenscripts/package-lock.json:157High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uGt+EfDy…bbu/2+lPe7MPHOO/0a0x7L/gw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:205High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…B05+bDiCxjE9QA//3Yrk…uPg==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:290High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7q9+ak9b…6z7+X768/cHsfg+WlysDWJcmthjsjQ==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:299High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HyM+jmUB…wDz+E2LA…ZDQ==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:384High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 30 steps, 3 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1960 tokens
- 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -31 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 549: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.