WebAsk Results Digest

The answer is not a dump of raw responses — it is a few numbers with an
explanation of what they mean.

Reply to the person in the language they write in.

## Which tool for what

This is where the wrong tool gets picked most often:

| What you need | Tool | What it returns |
|—|—|—|
| Overall picture | `get_quiz_summary` | distributions, ready percentages |
| A filtered slice | `get_quiz_report` | the same, over selected responses |
| Individual submissions | `get_quiz_answers` | raw responses one by one |
| Free text of one question | `get_quiz_report_inputs` | all text answers |
| A file for a human | `export_answers_xlsx` and other `export_*` | a download link |

**Start with the summary, not with raw answers.** Raw answers are for a specific
submission or for quoting examples.

## Order

1. `get_quiz_summary` — how many submissions, what the distributions are.
2. Check whether the data is complete: how many finished, how many were abandoned.
If many were abandoned, say so and treat them separately.
3. If a condition was named — “September only”, “only from the mailing” — build a
slice with `get_quiz_report`. Values for filtering by link labels come from
`get_answer_extra_field_values`.
4. Export a file only if a file was asked for. The link lives for one hour.

## How to answer

– **Conclusion first, numbers second.** Not “question 3 has this distribution” but
“two thirds are unhappy with turnaround times — here is the breakdown”.
– **Always name the base** for a percentage: all submissions or completed ones.
– **Do not present conclusions from ten responses as fact.**
– **Do not retell free text one by one** — group it into themes with a couple of
representative quotes.

## What not to do

– **Do not export a file unasked** — chat needs numbers, not an XLSX link.
– **Do not recompute by hand** what the summary already provides.
– **Do not mix completed and abandoned** in one figure without saying so.
– **Do not suggest a plan upgrade or lead to payment.** If a limit is hit, state
the fact and stop.

## Installation

Requires a WebAsk account and your own API key from Settings → API / MCP.
Connect the official hosted endpoint `https://mcp.webask.io/mcp/v1` using
Streamable HTTP and an `Authorization: Bearer` header. Store the key in your
client’s private configuration; do not paste it into chats, public reports or
committed files. Follow the [upstream connection instructions](https://github.com/WebAskio/webask-mcp/blob/main/en/README.md#quick-start)
for your client. The public repository contains documentation, configuration
and skills, not the hosted server implementation.

For a project-local Claude Code skill, copy the original English skill:

git clone https://github.com/WebAskio/webask-mcp.git webask-mcp-source
mkdir -p .claude/skills
cp -R webask-mcp-source/en/skills/webask-results-digest .claude/skills/

For Codex or Cursor, the upstream documentation uses `.agents/skills/`:

mkdir -p .agents/skills
cp -R webask-mcp-source/en/skills/webask-results-digest .agents/skills/

Example request: “Explain what the customer feedback survey showed this month,
with figures, recurring themes and a clear base for each percentage.”

The skill files are available without purchase under MIT. The hosted WebAsk
service has [free and paid plans](https://webask.io/pricing) and uses its own
[user agreement](https://webask.io/agreement). A service limit is a reason to
state the limit and stop, not to suggest payment. Russian instructions are
also available in the [upstream skill directory](https://github.com/WebAskio/webask-mcp/tree/main/skills/webask-results-digest).

## Source and license

Adapted from WebAskio’s official `webask-results-digest` skill. The workflow
instructions above are preserved; this submission adds ASE catalog metadata,
installation guidance and upstream attribution. `verification: listed` does
not claim an independent security review or an authenticated runtime test.

MIT License

Copyright (c) 2026 WebAsk

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.