catch-all-segmenter
Segment Email Lists by Verification Status
Catch-all results can be mistaken for verified mailboxes when all addresses stay in one list. Use Leadsets to verify addresses, separate four statuses, and group catch-all contacts by domain.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
Review the Skillstore skill "catch-all-segmenter" from https://skillstore.io/skills/leadsets-catch-all-segmenter.md and its manifest at https://skillstore.io/api/skills/leadsets-catch-all-segmenter/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "catch-all-segmenter". Verify an approved list of 120 contact rows and summarize the results.
النتيجة المتوقعة:
After cleanup, 100 unique addresses were checked. Results: 68 verified, 20 catch-all across six domains, eight unknown, and four invalid. The run used 100 records.
جارٍ استخدام "catch-all-segmenter". Create an approved Google Sheet export and show which domains need review.
النتيجة المتوقعة:
- The sheet contains four status tabs and a catch-all domain summary.
- Example.org has both verified and catch-all results. Its catch-all contacts remain separate from verified contacts.
التدقيق الأمني
مخاطر متوسطةThe shell, environment access, and reconnaissance alerts match documentation rather than the reported behaviors. Verification sends contact addresses to Leadsets without a required approval step, and connected exports can include all original contact columns. No evidence found of prompt injection or covert transfers.
مخاوف أمنية مؤكدة (1)
عناصر مراجعة القدرات (1)
هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.
عوامل الخطر
⚙️ الأوامر الخارجية (12)
🌐 الوصول إلى الشبكة (3)
🔑 متغيرات البيئة (1)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/leadsets-catch-all-segmenter/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/leadsets-catch-all-segmenter?utm_source=security_passport_badge)شارة HTML
<a href="https://skillstore.io/skills/leadsets-catch-all-segmenter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leadsets-catch-all-segmenter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>بطاقة قابلة للتضمين
<iframe src="https://skillstore.io/embed/skills/leadsets-catch-all-segmenter.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>الاستشهادات الأكاديمية (APA · BibTeX · CFF)
اقتباس APA
leadsets. (2026). catch-all-segmenter security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/leadsets-catch-all-segmenter/audits/1اقتباس BibTeX
@techreport{leadsets-leadsets-catch-all-segmenter-2026,
author = {leadsets},
title = {catch-all-segmenter security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/leadsets-catch-all-segmenter/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "catch-all-segmenter security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "leadsets"
date-released: "2026-11-18"
url: "https://skillstore.io/skills/leadsets-catch-all-segmenter/audits/1"
identifiers:
- type: other
value: "skillstore:leadsets-catch-all-segmenter:audit:1"
description: "Skillstore immutable audit report identifier"
تقييم Skillstore
سبب هذا التقييم موثوقية الأدلة: متوسطما الذي يمكنك بناؤه
Clean a Contact CSV
Remove duplicate addresses and review all four segments before deciding which contacts to keep.
Review Catch-All Domains
Compare catch-all counts by domain without mixing uncertain mailboxes into the verified segment.
Refresh CRM Verification Statuses
Reuse recent statuses, recheck older entries within the record allowance, and report addresses left unchecked.
جرّب هذه الموجّهات
Clean and deduplicate this pasted email list. Ask before sending addresses to Leadsets, then report verified, catch-all, unknown, and invalid counts.
Verify this CSV with Leadsets after I approve the transfer. Group catch-all rows by domain, sort the domain summary by contact count, and flag domains with mixed results.
Keep statuses checked within 30 days. Show the estimated Leadsets record use and wait for approval before rechecking the rest. Ask before exporting to my Google Sheet.
Show the estimated Leadsets record use and wait for approval before verifying. Verify at most 500 addresses. Show the sequencer workspace and export columns for approval before exporting only verified and catch-all contacts as separate segments.
أفضل الممارسات
- Confirm that you can share the contact addresses with Leadsets before starting verification.
- Set a record limit and reuse recent statuses when they meet your needs.
- Confirm the destination workspace and export only the fields needed for that destination.
تجنب
- Treating catch-all or unknown addresses as verified mailboxes.
- Rechecking every address without reviewing existing statuses or available records.
- Copying every source column to a connected sequencer without reviewing the fields.