salesforce-title-refresh
Refresh Salesforce Contact Titles
Outdated job titles make it harder to route, score, and segment Salesforce contacts. Check current roles with Leadsets, review proposed updates, and flag contacts who may have changed companies.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "salesforce-title-refresh" from https://skillstore.io/skills/leadsets-salesforce-title-refresh.md and its manifest at https://skillstore.io/api/skills/leadsets-salesforce-title-refresh/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「salesforce-title-refresh」を使用しています。 Check 25 contacts from the renewal list and wait for approval.
期待される結果:
- Review ready: 5 proposed title changes, 2 possible company moves, 16 unchanged contacts, and 2 contacts with no match.
- The dated CSV is saved. No Salesforce records were updated.
「salesforce-title-refresh」を使用しています。 Apply the six approved title and seniority changes. Keep company moves flagged.
期待される結果:
- Updated 6 approved Salesforce contacts. The 3 contacts flagged for company moves were not updated.
- The change log records the old and new values, check dates, and actions taken.
セキュリティ監査
中リスクThe command execution and reconnaissance alerts are false positives, and the homepage and signup URLs are documentation links. The Leadsets connection sends contact identifiers to an external service, and review-first mode saves identifiable logs before Salesforce approval. Same-company matching lacks a required per-contact identity, freshness, or confidence check before updates; no evidence of prompt injection was found.
確認済みのセキュリティ上の懸念 (2)
機能レビュー項目 (1)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/leadsets-salesforce-title-refresh/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/leadsets-salesforce-title-refresh?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/leadsets-salesforce-title-refresh?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leadsets-salesforce-title-refresh/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/leadsets-salesforce-title-refresh.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). salesforce-title-refresh security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/leadsets-salesforce-title-refresh/audits/1BibTeX形式の引用
@techreport{leadsets-leadsets-salesforce-title-refresh-2026,
author = {leadsets},
title = {salesforce-title-refresh security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/leadsets-salesforce-title-refresh/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: "salesforce-title-refresh 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-salesforce-title-refresh/audits/1"
identifiers:
- type: other
value: "skillstore:leadsets-salesforce-title-refresh:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review seniority before scoring
Check titles and seniority for a defined account group before running scoring rules. Review the proposed values before they affect routing.
Check contacts before outreach
Check contacts from a Salesforce list view before a new sales sequence. Review possible company moves separately instead of replacing those contact titles.
Reconcile approved title updates
Compare approved Salesforce updates with the dated change log. Use contact IDs and old and new values to verify the changes.
これらのプロンプトを試す
Check up to 20 contacts from [Salesforce list view]. Show me proposed title changes and wait for approval before updating Salesforce.
Review up to 100 contacts at accounts with open opportunities. Flag company moves separately, save a CSV, and wait for Salesforce write approval.
Check Title and [existing seniority field] for contacts in [Salesforce report]. Show old and new values and save the log to [restricted Google Sheet]. Wait for Salesforce write approval.
Check up to 500 contacts from [Salesforce report] whose titles have not changed in 180 days. Fit batches to current Leadsets limits and report when remaining contacts can resume. Flag company moves and wait for approval before updating Salesforce.
ベストプラクティス
- Start with a small report or list view. Confirm the first Leadsets result identifies the intended contact.
- Use review-first mode and verify identity, company, and role freshness before approving each proposed update.
- Confirm that Leadsets is approved for the contact data and restrict access to the CSV or Google Sheet.
回避
- Assuming review-first mode prevents Leadsets lookups or stops the change log from being saved.
- Approving a title update for a contact flagged as having changed companies.
- Sending contact logs to a public or broadly shared spreadsheet.