recipe-collect-form-responses

Retrieve and review responses from a Google Form.

30,054
installs: 0 up / 0 down, score 0.00
votes
In the catalog since: 30 Sept 2026
From: googleworkspace/cli

Get it through your agent

Skill instructions

Rendered from the published SKILL.md, 13 lines.

Check Form Responses

PREREQUISITE: Load the following skills to execute this recipe: gws-forms

Retrieve and review responses from a Google Form.

Steps

List forms: gws forms forms list (if you don't have the form ID)
Get form details: gws forms forms get --params '{"formId": "FORM_ID"}'
Get responses: gws forms forms responses list --params '{"formId": "FORM_ID"}' --format table

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "recipe-collect-form-responses"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Listing on skills.sh

From googleworkspace/cli via skills.sh

Related skills

recipe-create-feedback-form
Create a Google Form for feedback and share it via Gmail.
29,829 installs
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.
30,133 installs
review-pr
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
28,856 installs
form-cro
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
52,599 installs
respond-to-pr-comments-in-blocklist
Interactively walk a user through PR review comments one at a time, collect a per-comment decision, then post agent-authored replies on GitHub and resolve the review threads once the user approves a preview. Use only when the user wants to reply to or resolve review threads on GitHub. Skip when the user only wants comments fetched or displayed (use `pr-comments`), or only wants the code changes made without posting anything back to GitHub.
25,091 installs