webask-response-funnel
Analyze WebAsk Survey Drop-Off
Low survey completion can leave teams unsure which questions need attention. This skill uses WebAsk reports and questionnaire structure to identify potential drop-off points and recommend targeted changes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "webask-response-funnel" from https://skillstore.io/skills/webaskio-webask-response-funnel.md and its manifest at https://skillstore.io/api/skills/webaskio-webask-response-funnel/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "webask-response-funnel". Illustrative data: 200 attempts, 120 completions, 150 answers before a required phone question, and 125 answers at that question.
Expected outcome:
- Completion rate: 60%, based on 120 completed attempts out of 200.
- The phone question has 25 fewer answers than the preceding question, a decrease of approximately 16.7%.
- Required contact information is a possible source of friction, but these counts do not prove the cause.
- Consider making the phone question optional and explaining why the information is needed.
- No survey changes were made.
Using "webask-response-funnel". Illustrative data: 300 attempts and 180 completions; the workspace plan does not expose incomplete responses.
Expected outcome:
- Completion rate: 60%, based on 180 completed attempts out of 300.
- The current plan does not expose incomplete responses, so a question-level exit point cannot be measured.
- Questionnaire length, order, and required fields can still be reviewed.
- Any suggested causes from questionnaire structure remain hypotheses, not measured drop-off findings.
Security Audit
SafeAll six static findings are false positives: one documentation breadcrumb and five Markdown-formatted MCP tool references. The workflow requests survey and plan information through read tools and explicitly prohibits autonomous survey edits. No evidence found of prompt injection, unauthorized data transfer, or shell execution in the reviewed files.
Risk Factors
📁 Filesystem access (1)
⚙️ External commands (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/webaskio-webask-response-funnel?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/webaskio-webask-response-funnel?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/webaskio-webask-response-funnel/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/webaskio-webask-response-funnel.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
webaskio. (2026). webask-response-funnel security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1BibTeX citation
@techreport{webaskio-webaskio-webask-response-funnel-2026,
author = {webaskio},
title = {webask-response-funnel security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "webask-response-funnel security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "webaskio"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1"
identifiers:
- type: other
value: "skillstore:webaskio-webask-response-funnel:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Review customer feedback completion
Locate substantial response losses in a customer feedback survey and propose changes to demanding or sensitive questions.
Evaluate research questionnaire friction
Compare question-level response counts with questionnaire structure while separating measured results from possible explanations.
Assess contact collection timing
Review whether required contact questions coincide with response losses and suggest clearer explanations or later placement.
Try These Prompts
Review WebAsk survey [survey identifier]. How many attempts were completed, and what is the completion rate?
Analyze WebAsk survey [survey identifier] for [date range]. Show response counts by question and identify substantial losses if incomplete responses are available.
Review the response funnel and question structure for [survey identifier]. Suggest specific changes to question order, required fields, or wording without editing the survey.
Analyze [survey identifier] for [production date range], excluding tests before [launch date]. Check plan access to incomplete responses and flag sample-size limits. Separate measured losses from hypotheses, note possible branching effects, and propose prioritized changes without editing anything.
Best Practices
- Provide the survey identifier and a production date range that excludes known test submissions.
- Check incomplete-response availability and sample size before interpreting question-level losses.
- Review proposed changes manually and distinguish observed response counts from explanations that require further evidence.
Avoid
- Treating question-type heuristics as proof of respondent motives.
- Combining test submissions with production responses or drawing firm conclusions from a very small sample.
- Using the skill to modify surveys automatically or initiate workspace plan upgrades.
Frequently Asked Questions
Which tools does this skill require?
Does the skill edit my survey?
What happens when incomplete responses are unavailable?
Can it prove why respondents leave?
How should I handle test submissions?
Which language does it use for findings?
Developer Details
Author
webaskioLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Maintenance freshness
9/30/2026
Usage
0 downloads · 0 views
File structure