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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « webask-response-funnel ». Illustrative data: 200 attempts, 120 completions, 150 answers before a required phone question, and 125 answers at that question.
Résultat attendu:
- 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.
Utilisation de « webask-response-funnel ». Illustrative data: 300 attempts and 180 completions; the workspace plan does not expose incomplete responses.
Résultat attendu:
- 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.
Audit de sécurité
SûrAll 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.
Facteurs de risque
📁 Accès au système de fichiers (1)
⚙️ Commandes externes (5)
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/webaskio-webask-response-funnel?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
webaskio. (2026). webask-response-funnel security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/webaskio-webask-response-funnel/audits/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces 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.
Bonnes pratiques
- 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.
Éviter
- 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.
Foire aux 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?
Détails du développeur
Auteur
webaskioLicence
MIT
Révision Skillstore
r1
Avis de version
L’auteur n’a déclaré aucune version.
Réf
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Récence de maintenance
30/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers