icp-fit-scoring
Score Accounts and Contacts for ICP Fit
It is hard to prioritize sales lists when company details are missing and fit criteria are unclear. Use Leadsets data to score each prospect against your ideal customer profile and explain the result.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "icp-fit-scoring" from https://skillstore.io/skills/leadsets-icp-fit-scoring.md and its manifest at https://skillstore.io/api/skills/leadsets-icp-fit-scoring/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「icp-fit-scoring」を使用しています。 Score two accounts using the default weights for software, 51 to 200 employees, US location, and HubSpot.
期待される結果:
- Example Software: 80 of 100, tier A. Software, 51 to 200 employees, and HubSpot match. The company is in Canada, so it earns no region points.
- Example Labs: No data. Leadsets found no company record, so this row is separate from No fit.
「icp-fit-scoring」を使用しています。 Score a contact for a sales VP role. Use the default split of 60 points for account fit and 40 for role fit.
期待される結果:
- Example contact: 60 of 100, tier B. The current employer meets all account criteria, but the contact is a finance analyst, not a sales VP.
- Employer change: flagged. Email status: unknown and unconfirmed. Email status did not affect the score.
セキュリティ監査
中リスクOne flag reflects an actual Leadsets connection that can transmit account and contact identifiers; the other 21 static flags are false positives. The workflow exports contact data by default without checking sharing permissions and can spend additional enrichment records when contacts have changed companies. No evidence found of prompt injection, shell execution, host reconnaissance, or environment access.
確認済みのセキュリティ上の懸念 (2)
機能レビュー項目 (1)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
⚙️ 外部コマンド (13)
🌐 ネットワークアクセス (3)
🔑 環境変数 (1)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/leadsets-icp-fit-scoring/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/leadsets-icp-fit-scoring?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/leadsets-icp-fit-scoring?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leadsets-icp-fit-scoring/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/leadsets-icp-fit-scoring.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). icp-fit-scoring security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/leadsets-icp-fit-scoring/audits/1BibTeX形式の引用
@techreport{leadsets-leadsets-icp-fit-scoring-2026,
author = {leadsets},
title = {icp-fit-scoring security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/leadsets-icp-fit-scoring/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: "icp-fit-scoring 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-icp-fit-scoring/audits/1"
identifiers:
- type: other
value: "skillstore:leadsets-icp-fit-scoring:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prioritize a founder's account list
Rank an existing list of companies by industry, size, region, and technology before choosing which accounts to research first.
Qualify webinar contacts
Score registrants by employer fit and current role. Flag changes of employer before handing the list to sales.
Review a CRM segment
Apply a consistent scoring rubric to a CRM view. Export the tiers and keep accounts with no data separate for review.
これらのプロンプトを試す
Score the attached CSV for US software companies with 51 to 200 employees that use HubSpot. Use default weights and explain every score. Export a new CSV.
Score the contacts in this sheet for Canadian software companies with 50 to 500 employees that use HubSpot. Target heads of sales and sales VPs. Flag contacts who changed employers and mark unknown criteria.
Score this CRM view for US software companies with 51 to 200 employees that use HubSpot. Weight industry and region at 35 each, headcount at 20, and technology at 10. Set A at 85, B at 65, and C at 45. Export a new CSV without changing the CRM.
Plan scoring for these CRM contacts using our attached rubric. Count unique companies and contacts, then check the five-hour and weekly quotas. Before enrichment, show the batch plan and wait for approval of the record cap. Write the results to the approved sheet and omit work email.
ベストプラクティス
- Define exact criteria, weights, and tier cutoffs before enrichment.
- Review quota usage and approve a record cap before scoring a large list.
- Confirm who can access the export and omit work emails unless they are needed.
回避
- Treating missing information as evidence that a company does not fit.
- Enriching the same company repeatedly for contacts who share a domain.
- Treating catch-all or unknown email statuses as verified.