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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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 は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/leadsets-catch-all-segmenter/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](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/1BibTeX形式の引用
@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.