Skip to content
skillsafebeta
← Report library
Purpose / Other

Recipe Create Feedback Form Skill Security Audit

What the author says it does (original text)

Create a Google Form for feedback and share it via Gmail.

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.No risks found
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.Risks found: 1
Medium risk

The recipe sends external email to a hard-coded company address

Source references: 2
What we found

Step 3 directly invokes Gmail sending with `attendees@company.com` as a fixed recipient, without requiring confirmation of the recipient, message, or timing. The address could be a mailing list, an unrelated organization's address, or merely an example from the author's environment.

Why this matters

If followed literally, the user's Google account immediately sends email, potentially reaching the wrong or a large audience, disclosing the form link, and causing spam, reputational, or compliance consequences.

This is an operative recipe step, not a warning, test, or negated example. If followed, step 3 uses the user's Gmail to send a message to the fixed address `attendees@company.com`; the source does not require confirmation of the recipient, message, or send action. The address may have been intended as a placeholder, but it is not labeled as one, creating a plausible risk of misdirected mail, disclosure of the form link to an unauthorized recipient, and external communication in the user's name. The user can ask the author to require a recipient input and explicit confirmation of the recipient and body before sending.

SKILL.md:27In the instructionsOpen original file
2. Get the form URL from the response (responderUri field)3. Email the form: `gws gmail +send --to attendees@company.com --subject 'Please share your feedback' --body 'Fill out the form: FORM_URL'`
Show 1 other places
SKILL.md:21In the instructionsOpen original file
Create a Google Form for feedback and share it via Gmail.

Inside this skill

1 instruction sections

The Skill requires Google Forms and Gmail skills plus the `gws` command; execution therefore depends on access to the user's Google Workspace services.

View source
SKILL.md:9In the instructionsOpen original file
    domain: "productivity"    requires:      bins:        - gws      skills:        - gws-forms        - gws-gmail---
SKILL.md:19In the instructionsOpen original file
> **PREREQUISITE:** Load the following skills to execute this recipe: `gws-forms`, `gws-gmail`

The workflow creates an “Event Feedback” form in the Google account and then extracts its responder link. The shown creation command sets only titles and does not add feedback questions.

View source
SKILL.md:25In the instructionsOpen original file
1. Create form: `gws forms forms create --json '{"info": {"title": "Event Feedback", "documentTitle": "Event Feedback Form"}}'`2. Get the form URL from the response (responderUri field)3. Email the form: `gws gmail +send --to attendees@company.com --subject 'Please share your feedback' --body 'Fill out the form: FORM_URL'`
Start here · InstructionsSKILL.md
recipe-create-feedback-form
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
29
File checksum (to compare versions)
cda67fda0026fce641657081c11275f5fbe85af0b8a87415eb554b819356b097