Skills job-change-detector
๐Ÿ“ฆ

job-change-detector

v1.0 Content revision r1 Medium Risk โš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Detect Job Changes in Your Contact List

Outdated contact lists make it hard to know who still works in the same role or company. Compare stored records with current Leadsets data and review the changes before updating your CRM.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it โš ๏ธ 50 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "job-change-detector" from https://skillstore.io/skills/leadsets-job-change-detector.md and its manifest at https://skillstore.io/api/skills/leadsets-job-change-detector/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "job-change-detector". Check my approved CSV of 20 contacts for employer and title changes.

Expected outcome:

  • Loaded 20 rows and skipped 2 exact duplicates.
  • Found 3 employer moves, 4 title changes, and 9 unchanged contacts. Leadsets did not find 2 contacts.
  • Used 16 enrichment records. The CSV flags old work emails for all 3 movers.

Using "job-change-detector". Check this approved list of six account contacts and propose CRM changes.

Expected outcome:

  • Found 1 employer move, 1 role change, and 4 unchanged contacts.
  • Alex Lee moved from Cedar Labs to Northview Systems. Leadsets did not return a new work email.
  • The proposed updates include the old and new values and their check dates. No CRM records were changed.

Security Audit

Medium Risk
v1 โ€ข 11/18/2026 Open versioned report

Of the 21 static matches, only the Leadsets endpoint represents a real network data transfer. The workflow defaults to sending contact identifiers without explicit approval, and its email verification guidance is inconsistent. No evidence of shell execution, environment access, system reconnaissance, or prompt injection was found.

2
Files scanned
116
Lines analyzed
1
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
Default Bulk Sharing Without Explicit Approval
The workflow defaults to the entire list and sends contact identifiers to Leadsets without an explicit approval step. A CRM export can include records the user is not permitted to share.
The scope defaults to the whole list, and the steps direct the agent to probe and continue with the remaining contacts. Explicit approval applies to CRM write-back, not enrichment.
Medium
Conflicting Email Verification Instructions
The workflow states that all enriched emails are verified, but it also defines catch-all and unknown statuses. The blanket claim could cause unconfirmed addresses to appear in verified output.
The claim that enriched emails are already verified conflicts with the explicit status requirement. The final checks reduce the risk, but the agent still receives contradictory instructions.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
Hardcoded URL
- The Leadsets MCP server connected to your agent: `https://mcp.leadsets.ai` ([setup](https://www.le
The URL identifies the external MCP service used for enrichment. The documented lookup sends contact identifiers to Leadsets, exposing that data outside the agent.
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/leadsets-job-change-detector/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/leadsets-job-change-detector/security.svg)](https://skillstore.io/skills/leadsets-job-change-detector?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/leadsets-job-change-detector?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leadsets-job-change-detector/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/leadsets-job-change-detector.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

leadsets. (2026). job-change-detector security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/leadsets-job-change-detector/audits/1

BibTeX citation

@techreport{leadsets-leadsets-job-change-detector-2026, author = {leadsets}, title = {job-change-detector security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/leadsets-job-change-detector/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: "job-change-detector 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-job-change-detector/audits/1" identifiers: - type: other value: "skillstore:leadsets-job-change-detector:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Review Quarterly CRM Changes

Review a CRM segment for employer and title changes, then prepare proposed field updates for approval.

Review a List Before Outreach

Identify contacts who left their employer and flag old work addresses before using an existing outreach list.

Track Moves Among Key Contacts

Check whether key customer contacts moved companies or changed roles before scheduling account reviews.

Try These Prompts

Check a Small CSV
Use Leadsets to check this CSV for employer and title changes. Save the results to a new CSV and list any contacts you cannot find.
Review Role and Seniority Changes
Use Leadsets to check this sheet and separate promotions from other title changes. Treat equivalent title spellings as unchanged and write the results to new tabs.
Refresh a List Within Usage Limits
Check my Leadsets balance and tell me how many contacts from this export you can process now. Check one approved contact first, then process only the contacts I approve. List unfinished rows and report when I can resume.
Prepare Proposed CRM Updates
Use Leadsets to compare this approved CRM segment by company domain and title. Show the old and new values and the check date for each proposed update. Treat emails without an explicit verified status as unconfirmed. Do not write to the CRM.

Best Practices

  • Confirm that you may share the selected contact identifiers with Leadsets before starting.
  • Start with one approved contact to validate the column mapping and returned data before processing a batch.
  • Review match dates and email status labels before using the results or approving CRM updates.

Avoid

  • Sending an entire CRM export when you only need to check one segment.
  • Treating catch-all, unknown, or missing email statuses as verified.
  • Using a missing match as proof that a contact left the company.

Frequently Asked Questions

Which input formats can I use?
Use a CSV, a Google Sheet, or a CRM export or view that the agent can read.
What fields does each contact need?
Include the stored title and company. Provide a LinkedIn URL, a work email, or a full name with a company domain.
What contact data goes to Leadsets?
The lookup uses a LinkedIn URL, a work email, or a name with a company domain. Confirm that you have permission to share those identifiers.
What happens when I reach my usage limit?
The skill reports completed and pending rows. When Leadsets provides a reset time, the skill tells you when to resume.
Is a new work email always verified?
No. Only an explicit verified status counts. Catch-all and unknown results are not verified, and some movers have no new email.
Will this update my CRM automatically?
No. The skill can propose field changes, but it requires approval of the exact updates before it writes anything to the CRM.

Developer Details

Author

leadsets

License

MIT

Author version

v1.0

Skillstore revision

r1

Version notice

The author-declared version is not valid SemVer.

Ref

2e8507920dcc30a093cf783bb38b0b0b90dc635b

Maintenance freshness

11/20/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ skill.json

๐Ÿ“„ SKILL.md

More from leadsets

View all
View all