Skip to content
skillsafebeta
← Report library
Purpose / Documents

Recipe Share Doc And Notify Skill Security Audit

What the author says it does (original text)

Share a Google Docs document with edit access and email collaborators the link.

Independent security check

Security risks found

Files checked
1
Risks found
2
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.Risks found: 1
Medium risk

Broad name search can cause the wrong similarly named document to be shared

Source references: 2
What we found

The lookup uses `name contains 'Project Brief'`, which can return multiple documents containing that fragment, but the later steps do not specify how to verify which `DOC_ID` is intended.

Why this matters

If the agent selects the wrong result, that document receives edit permission and its link is sent to the recipient.

The lookup uses a contains match rather than a unique ID or exact name, so it may return several Google Docs when multiple names include “Project Brief.” The permission step then expects one DOC_ID but provides no visible selection or confirmation rule, creating a plausible risk of sharing the wrong document. A user can require filtering by unique ID, owner, or location and confirmation of the title and owner before access is granted.

SKILL.md:26In the instructionsOpen original file
1. Find the doc: `gws drive files list --params '{"q": "name contains '\''Project Brief'\'' and mimeType = '\''application/vnd.google-apps.document'\''"}'`2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
Show 1 other places
SKILL.md:27In the instructionsOpen original file
1. Find the doc: `gws drive files list --params '{"q": "name contains '\''Project Brief'\'' and mimeType = '\''application/vnd.google-apps.document'\''"}'`2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
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

Grants lasting document edit access and sends the access link

Source references: 3
What we found

The workflow creates a `writer` permission and then actively emails the link to the same address, without requiring confirmation of the recipient, access level, or document identity before execution.

Why this matters

If the email address, document ID, or user intent is wrong, the recipient could read and modify a document that should not have been shared, and access remains until revoked.

This is active behavior and part of the stated purpose. If steps 2 and 3 are run after replacing the placeholders, they create writer access for the specified address and email the document link. The visible steps do not require confirmation of the recipient, document, or access level, so a wrong address or DOC_ID could give an unintended person editing ability. A user can ask for pre-action confirmation and default to view-only or time-limited access.

SKILL.md:27In the instructionsOpen original file
1. Find the doc: `gws drive files list --params '{"q": "name contains '\''Project Brief'\'' and mimeType = '\''application/vnd.google-apps.document'\''"}'`2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
Show 2 other places
SKILL.md:22In the instructionsOpen original file
Share a Google Docs document with edit access and email collaborators the link.
SKILL.md:28In the instructionsOpen original file
2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
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 depends on Google Drive, Docs, and Gmail capabilities and uses `gws` commands to operate the user's Google Workspace.

View source
SKILL.md:9In the instructionsOpen original file
    domain: "productivity"    requires:      bins:        - gws      skills:        - gws-drive        - gws-docs        - gws-gmail---

The workflow searches for a Google document by a name fragment, grants edit access to a specified email address, and then sends the document link through Gmail.

View source
SKILL.md:26In the instructionsOpen original file
1. Find the doc: `gws drive files list --params '{"q": "name contains '\''Project Brief'\'' and mimeType = '\''application/vnd.google-apps.document'\''"}'`2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
Start here · InstructionsSKILL.md
recipe-share-doc-and-notify
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

Operations mentioned in code and instructions

Connect to websites
SKILL.md:28In the instructionsOpen original file
2. Share with editor access: `gws drive permissions create --params '{"fileId": "DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "reviewer@company.com"}'`3. Email the link: `gws gmail +send --to reviewer@company.com --subject 'Please review: Project Brief' --body 'I have shared the project brief with you: https://docs.google.com/document/d/DOC_ID'`
Lines read
30
File checksum (to compare versions)
cfb9b9c17cb9c42fb49a9eb9e7aec0aee32b8de0d6648fe8ad50038de56b8b98