webask-lead-quality
Analyze WebAsk Lead Quality
Survey completion counts can hide missing or unusable contact details. This skill guides assistants through WebAsk reports to assess contact quality, compare channels, and prioritize improvements.
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-lead-quality" from https://skillstore.io/skills/webaskio-webask-lead-quality.md and its manifest at https://skillstore.io/api/skills/webaskio-webask-lead-quality/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-lead-quality ». Illustrative data: 512 starters, 243 reached the contact step, 186 submitted contacts, and 164 contacts appear usable. Summarize lead quality.
Résultat attendu:
- Started: 512. Reached contact: 243. Submitted contact: 186. Apparently usable contacts: 164.
- Contact submission rate: 36.3% of starters. Apparently usable contact rate: 32.0% of starters.
- Contact-stage gap: 57 participants. Suspicious contact submissions: 22.
- Review the contact explanation and unnecessary fields. These counts do not establish why participants stopped.
Utilisation de « webask-lead-quality ». Illustrative labeled data: newsletter has 100 starters and 38 usable contacts; website banner has 100 starters and 19. Compare these sources.
Résultat attendu:
- Newsletter: 38 apparently usable contacts from 100 starters, or 38%.
- Website banner: 19 apparently usable contacts from 100 starters, or 19%.
- Newsletter has the higher observed usable contact rate. Costs and eventual sales outcomes are unavailable.
- Review banner traffic expectations and contact questions before making budget decisions.
Audit de sécurité
SûrAll five static findings are false positives: documentation navigation links and Markdown inline text do not execute commands or perform filesystem traversal. No evidence found of prompt injection, credential theft, or unauthorized data disclosure in the supplied files. The skill requests survey reporting tools and explicitly prohibits posting contacts in chat; external tool implementations are outside this review.
Facteurs de risque
📁 Accès au système de fichiers (1)
⚙️ Commandes externes (4)
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-lead-quality/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/webaskio-webask-lead-quality?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/webaskio-webask-lead-quality?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/webaskio-webask-lead-quality/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/webaskio-webask-lead-quality.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-lead-quality security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/webaskio-webask-lead-quality/audits/1Citation BibTeX
@techreport{webaskio-webaskio-webask-lead-quality-2026,
author = {webaskio},
title = {webask-lead-quality security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/webaskio-webask-lead-quality/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-lead-quality 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-lead-quality/audits/1"
identifiers:
- type: other
value: "skillstore:webaskio-webask-lead-quality:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Compare Acquisition Channels
Compare apparently usable contact rates across labeled sources to identify channels that generate stronger leads.
Assess Sales Intake Quality
Separate survey completions from submissions with apparently usable contacts before evaluating the incoming lead volume.
Review Contact Collection
Identify losses around contact questions and prioritize changes to field requirements, question order, and contact explanations.
Essayez ces prompts
Analyze WebAsk survey [survey]. Show starters, contact submissions, apparently usable contacts, and their share of starters. Keep personal contact details out of chat.
Review [survey] and compare response counts before and at the contact question. Estimate the loss and suggest prioritized improvements. State data limitations.
Compare lead quality for each source label in [survey]. Show counts and usable contact rates. Identify missing labels and avoid unsupported cost claims.
Audit [survey] across contact conversion, suspicious values, and labeled channels. Explain denominators and heuristic limits. Rank recommendations by expected impact without changing the survey.
Bonnes pratiques
- Use all survey starters as the denominator and distinguish submitted contacts from apparently usable contacts.
- Keep personal contact details out of chat and report aggregate counts.
- Check source labels, report completeness, and heuristic assumptions before prioritizing changes.
Éviter
- Treating every completed survey as a qualified lead, even when contact details are missing.
- Assuming suspicious contact formats prove that a person is unreachable or unqualified.
- Removing every required field or claiming channel cost advantages without spending data.
Foire aux questions
What does this skill measure?
Which tools does it require?
Does it verify phone numbers or email addresses?
Can it compare acquisition channels?
Will it show personal contacts or update my CRM?
What happens when a service limit prevents analysis?
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