account-tiering
Prioritize Accounts by Customer Fit
Large account lists make it hard to decide which companies to review first. This skill ranks companies against your ideal customer profile and cites evidence for each tier.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "account-tiering" from https://skillstore.io/skills/leadsets-account-tiering.md and its manifest at https://skillstore.io/api/skills/leadsets-account-tiering/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「account-tiering」を使用しています。 Rank 40 event accounts for US software companies with 50 to 500 employees. Use company data only.
期待される結果:
- Removed two duplicate domains and kept all 38 unique domains in the export.
- Tier A: 8 accounts. Tier B: 14. Tier C: 9. Out: 5. No data: 2.
- Example Tier A reason: Leadsets reports US headquarters and 120 employees.
「account-tiering」を使用しています。 Check whether borderline accounts sell to finance teams. Preview the proposed CRM updates.
期待される結果:
- Example account moved to Tier A after its product page named finance teams as its audience.
- Another account stayed in Tier B with low confidence because its public pages did not identify its buyers.
- No CRM changes were made. The preview lists the proposed tier, score, and reasons.
セキュリティ監査
中リスクThe workflow sends company domains to Leadsets for enrichment and optional website research. The other scanner matches are Markdown formatting, informational links, or ordinary API documentation. The skill does not tell the agent to treat scraped website text as untrusted before scoring or exporting results.
確認済みのセキュリティ上の懸念 (1)
機能レビュー項目 (1)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
⚙️ 外部コマンド (13)
🌐 ネットワークアクセス (3)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/leadsets-account-tiering/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/leadsets-account-tiering?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/leadsets-account-tiering?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leadsets-account-tiering/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/leadsets-account-tiering.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). account-tiering security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/leadsets-account-tiering/audits/1BibTeX形式の引用
@techreport{leadsets-leadsets-account-tiering-2026,
author = {leadsets},
title = {account-tiering security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/leadsets-account-tiering/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: "account-tiering 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-account-tiering/audits/1"
identifiers:
- type: other
value: "skillstore:leadsets-account-tiering:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prioritize Event Accounts
Rank companies from an event list and review the strongest matches before planning follow-up.
Plan Account Assignments
Tier target accounts before assigning them to sales representatives, with cited reasons the team can review.
Refresh CRM Account Tiers
Rescore a connected CRM account list and review proposed changes to designated company fields before updating them.
これらのプロンプトを試す
Tier [company domains] for a US software business that targets companies with 50 to 500 employees. Show the rubric and use company data only.
Score [CSV] for [ideal customer profile]. Treat [region] and [headcount range] as hard requirements. Return CSV results and list unmatched domains separately.
Rank [account list] against [ideal customer profile] using weights [weights]. Research public websites only for borderline accounts and stop after [number] scrape units. Cite the evidence.
Score the companies in [CRM view] using [criteria and weights]. Preview proposed changes to [tier field], [score field], and [reasons field]. Wait for my approval before writing.
ベストプラクティス
- Review the rubric and distinguish hard requirements from preferences before scoring.
- Confirm that your organization allows sharing the company domains with Leadsets before enrichment.
- Review low-confidence scores and preview changes before writing to shared systems.
回避
- Do not treat missing company data as proof that an account fails your criteria.
- Do not research every website when only a few scores depend on website evidence.
- Do not write results to unapproved CRM fields or overwrite existing company data.