Skip to content
skillsafebeta
← Report library
Purpose / Other

Recipe Create Shared Drive Skill Security Audit

What the author says it does (original text)

Create a Google Shared Drive and add members with appropriate roles.

Independent security check

Security risks found

Files checked
1
Risks found
1
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.Risks found: 1
Medium risk

The member step directly grants an external account writer access

Source references: 2
What we found

The command creates `writer` permission for the supplied email, but the workflow does not require confirmation of the final address, target drive, or least-privileged role before execution. The stated goal of using “appropriate roles” does not establish that writer is appropriate for a particular user.

Why this matters

If placeholders are replaced incorrectly, autofilled, or reused, the wrong account could receive write access to content in the target Shared Drive.

This is an actionable recipe step: if run with a real address, it grants that user writer access to the shared drive, allowing content changes. `member@company.com` is only a placeholder, so the source does not establish that the account is external. However, the step does not require checking the final address, target drive, or least-privileged role. A user can ask for explicit confirmation and restrict membership to approved domains and minimum roles.

SKILL.md:20In the instructionsOpen original file
Create a Google Shared Drive and add members with appropriate roles.
Show 1 other places
SKILL.md:25In the instructionsOpen original file
1. Create shared drive: `gws drive drives create --params '{"requestId": "unique-id-123"}' --json '{"name": "Project X"}'`2. Add a member: `gws drive permissions create --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}' --json '{"role": "writer", "type": "user", "emailAddress": "member@company.com"}'`3. List members: `gws drive permissions list --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}'`
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

1 instruction sections

The Skill states that it creates and configures a Google Shared Drive, and its first operational step calls `gws` to create a drive named “Project X.”

View source
SKILL.md:20In the instructionsOpen original file
Create a Google Shared Drive and add members with appropriate roles.
SKILL.md:24In the instructionsOpen original file
1. Create shared drive: `gws drive drives create --params '{"requestId": "unique-id-123"}' --json '{"name": "Project X"}'`2. Add a member: `gws drive permissions create --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}' --json '{"role": "writer", "type": "user", "emailAddress": "member@company.com"}'`

The subsequent steps grant a user the writer role on a specified Shared Drive and then list its members. The example values `DRIVE_ID` and `member@company.com` need replacement before execution.

View source
SKILL.md:25In the instructionsOpen original file
1. Create shared drive: `gws drive drives create --params '{"requestId": "unique-id-123"}' --json '{"name": "Project X"}'`2. Add a member: `gws drive permissions create --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}' --json '{"role": "writer", "type": "user", "emailAddress": "member@company.com"}'`3. List members: `gws drive permissions list --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}'`
SKILL.md:26In the instructionsOpen original file
2. Add a member: `gws drive permissions create --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}' --json '{"role": "writer", "type": "user", "emailAddress": "member@company.com"}'`3. List members: `gws drive permissions list --params '{"fileId": "DRIVE_ID", "supportsAllDrives": true}'`
Start here · InstructionsSKILL.md
recipe-create-shared-drive
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
Lines read
28
File checksum (to compare versions)
afee2074f73f8d5901b454ccbfc38813f4d3cb14991161bd73a761668fce6d74