SKILLEMALL.ai

DC google-drive

Read, export, upload, rename, move and delete Google Drive files explicitly selected or shared with the app via the Drive v3 REST API. Use when the user provides a Drive file ID/link or has selected files for the Google Drive connector.

AceDataCloud/Skills Agent Skills author: AceDataCloud 1 file body ≈ 2 823 tokens Open the sourcegithub.com↗ analyzed 5 h ago

Read, export, upload, rename, move and delete Google Drive files explicitly selected or shared with the app via the Drive v3 REST API.

As a process C 50/100 · Has gaps — weak spots: steps, result and completion, inputs and preconditions

IntegrationGoogle DriveData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
D
77/100
safety, quality, tests
Safety 60%
75
Quality 40%
80
Run on models
none yet
Process rating
C
50/100
Has gaps
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

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

    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
    • medium Exfiltration net-credential-use SKILL.md:101
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -H "Authorization: Bearer $GOOGLE_DRIVE_TOKEN" \
    • medium Exfiltration net-credential-use SKILL.md:112
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -H "Authorization: Bearer $GOOGLE_DRIVE_TOKEN" \
    • medium Exfiltration net-credential-use SKILL.md:123
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -H "Authorization: Bearer $GOOGLE_DRIVE_TOKEN" \
    • medium Exfiltration net-credential-use SKILL.md:132
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -L -H "Authorization: Bearer $GOOGLE_DRIVE_TOKEN" \
    • medium Exfiltration net-credential-use SKILL.md:147
      Credential used in a network call (verify the destination is the intended service)
      curl -sS -H "Authorization: Bearer $GOOGLE_DRIVE_TOKEN" \

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "connections"
    • note frontmatter-key unknown frontmatter key "allowed_tools"

    Process rating: all ten parameters 50/100

    • 0Steps. Prose only: no discrete steps
    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 8 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2823 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)
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 236: enough signal without eating the budget
    • +4Structure: 20 headings
    • +4Has examples (16 code blocks)
    • +1License stated

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