Skills lead-research-assistant

📦

lead-research-assistant

Name: lead-research-assistant
Author: Joseph OBrien

v1.0.1 Content revision r1 Medium Risk 📁 Filesystem access⚙️ External commands

Find Qualified Sales Leads

Sales teams often spend hours turning vague target profiles into useful account lists. This skill structures product analysis, lead qualification, and outreach planning for Claude, Codex, and Claude Code.

Supports: Claude Codex Code(CC)

📊 69 Adequate

Install with my Agent

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

Agent request

Review the Skillstore skill "lead-research-assistant" from https://skillstore.io/skills/89jobrien-lead-research-assistant.md and its manifest at https://skillstore.io/api/skills/89jobrien-lead-research-assistant/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.

Markdown detail GET /skills/89jobrien-lead-research-assistant.md Signed manifest GET /api/skills/89jobrien-lead-research-assistant/manifest Signed lockfile GET /api/skills/89jobrien-lead-research-assistant/lockfile

Test it

Using "lead-research-assistant". Find leads for a privacy tool that helps engineering teams protect AI assistant prompts.

Expected outcome:

A ranked list of security-conscious software companies, fit scores, buyer roles, evidence, and suggested outreach themes.

Using "lead-research-assistant". Research Bay Area companies that recently moved to remote work and may need team productivity consulting.

Expected outcome:

A prospect table with remote-work signals, company context, priority levels, and practical conversation starters.

Using "lead-research-assistant". Use my repository to understand the product and find enterprise partnership targets.

Expected outcome:

A summary of the product value, ideal partner traits, matched companies, and recommended next research steps.

Security Audit

Medium Risk

v6 • 7/5/2026 Open versioned report

Most static findings are false positives from Markdown fences, inline code, template placeholders, and artifact examples. I found one semantic dual-use concern: the skill encourages lead targeting using possible sensitive-data exposure signals linked to decision-maker outreach. It should add clearer responsible-use and privacy boundaries before broad marketplace publication.

Files scanned

591

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:173-181

Dual-use lead targeting from sensitive exposure signals

The example encourages finding companies that may have accidentally exposed sensitive data in code and linking that research to decision-maker outreach. This can support legitimate sales, but it can also create targeted lists around security weakness.

The example directly references accidental sensitive data exposure and LinkedIn URLs for decision-makers. It does not include exploit steps, so the risk is dual-use rather than clearly malicious.

Risk Factors

📁 Filesystem access (3)

references/research-report.template.md:157 references/research-report.template.md:158 references/research-report.template.md:159

⚙️ External commands (9)

SKILL.md:45-48 SKILL.md:48-54 SKILL.md:54-57 SKILL.md:57-63 SKILL.md:63-73 SKILL.md:73-124 SKILL.md:124-161 SKILL.md:161-197 SKILL.md:197-198

Audited by: codex View Audit History →

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

Copy report link

https://skillstore.io/skills/89jobrien-lead-research-assistant/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/89jobrien-lead-research-assistant/security.svg)](https://skillstore.io/skills/89jobrien-lead-research-assistant?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/89jobrien-lead-research-assistant?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/89jobrien-lead-research-assistant/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/89jobrien-lead-research-assistant.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

Joseph OBrien. (2026). lead-research-assistant security audit report (audit version 6) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/89jobrien-lead-research-assistant/audits/6

BibTeX citation

@techreport{joseph-obrien-89jobrien-lead-research-assistant-2026,
  author = {Joseph OBrien},
  title = {lead-research-assistant security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/89jobrien-lead-research-assistant/audits/6},
  note = {Author version 1.0.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lead-research-assistant security audit report (audit version 6)"
version: "1.0.1"
type: report
authors:
  - name: "Joseph OBrien"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/89jobrien-lead-research-assistant/audits/6"
identifiers:
  - type: other
    value: "skillstore:89jobrien-lead-research-assistant:audit:6"
    description: "Skillstore immutable audit report identifier"

Compare variants

4 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

DYAI2025 Recommended

dyai2025-lead-research-assistant

Skillstore Score 78

Evidence Confidence High

Skillstore usage 12

Updated

2026-08-21

ComposioHQ

composiohq-lead-research-assistant

Skillstore Score 75

Evidence Confidence High

Skillstore usage 9

Updated

2026-08-21

davila7

davila7-lead-research-assistant

Skillstore Score 70

Evidence Confidence High

Skillstore usage 9

Updated

2026-08-21

Joseph OBrien Current

89jobrien-lead-research-assistant

Skillstore Score 69

Evidence Confidence High

Skillstore usage 14

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Build a launch account list

Identify companies that match a new product and rank them by buyer fit, urgency, and outreach angle.

Validate early customer segments

Compare potential customer groups and find accounts that show clear need, budget signals, and timing indicators.

Find partnership targets

Research companies with complementary products and prepare practical talking points for business development conversations.

Try These Prompts

Find Initial Leads

Analyze this product: [description]. Find 10 companies that could benefit. Include fit scores, reasons, and outreach angles.

Research a Target Segment

My ideal customers are [industry], [size], in [region]. Find 15 accounts and explain the strongest buying signals.

Use Repository Context

Review this repository to understand the product. Then identify target companies, decision-maker roles, and tailored value propositions.

Compare Segments and Prioritize

Compare these segments: [segment list]. Score each segment, choose the best accounts, and recommend a first outreach plan.

Best Practices

Provide a clear product description, target region, company size range, and excluded markets.
Ask for evidence behind each fit score before adding accounts to a CRM.
Review privacy and outreach rules before using decision-maker information.

Avoid

Do not request private contact data, scraped personal profiles, or unauthorized information.
Do not treat fit scores as verified buying intent without human review.
Do not use security weaknesses as pressure points in sales outreach.