BB google-drive
Google Drive file management: search, upload, download, organize folders, move/copy files, share with permissions, and export Google Docs formats. Use when an agent needs google drive, search drive files by name or content, download files to agentpmt storage for processing, upload files to drive from agentpmt storage, create folder structures and organize files, copy file, file id, new name through AgentPMT-hosted remote tool calls. Discovery terms: google drive.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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-tokenSKILL.md:77High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"file_id": "1Bxi…pms"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:97High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"file_id": "1Bxi…pms",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:208High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"file_id": "1Bxi…pms",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:228High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"file_id": "1Bxi…pms",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:243High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"file_id": "1Bxi…pms"
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5768 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 40 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 5768 tokens
- 100Steps. 128 steps
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +1No license
- +2Single-language instructions
- +3Description length 467: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 128 items
- +3Output format is stated explicitly
- +4Has examples (25 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.