aiskillstore/marketplace / skills/89jobrien/lead-research-assistant
lead-research-assistant
VerifiedIdentifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| references/competitive-analysis.template.md | markdown | 3.7 KB |
| references/research-report.template.md | markdown | 2.9 KB |
| skill-report.json | config | 22.3 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-05T12:46:16.621Z",
"slug": "89jobrien-lead-research-assistant",
"source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/lead-research-assistant",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "30c68bfaa81bb8a0e935799f3e4aa644b35122db7f9969adf0e1973f4032a8cf",
"tree_hash": "d19cf3b8abdc28d27793dc9b8bfcaae83f70fb91d879224f5ecfb085a0f1fb95",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "lead-research-assistant",
"description": "Finds and qualifies potential sales leads by analyzing a product, target market, and public company signals. It returns ranked accounts with outreach strategies.",
"summary": "Find and qualify target companies with fit scores, buyer context, and outreach strategies.",
"icon": "📦",
"version": "1.0.2",
"author": "Joseph OBrien",
"license": "MIT",
"tags": [
"lead research",
"sales prospecting",
"business development",
"market research",
"outreach strategy"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"filesystem",
"external_commands"
],
"category": "research"
},
"security_audit": {
"risk_level": "medium",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "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.",
"remediation": [
{
"issue": "Dual-use prospecting around sensitive exposure signals",
"suggestion": "Add a responsible-use rule that sensitive exposure signals must not be used for coercive outreach, exploitation, or unauthorized disclosure.",
"severity": "medium"
},
{
"issue": "Public-source and privacy boundaries are implicit",
"suggestion": "State that lead enrichment must use lawful public business data and avoid collecting private personal data or private contact details.",
"severity": "medium"
},
{
"issue": "Temporary artifact examples may trigger security scanners",
"suggestion": "Use workspace-relative artifact paths or describe research artifacts generically instead of listing /tmp paths.",
"severity": "low"
}
],
"risk_factor_evidence": [
{
"factor": "filesystem",
"evidence": [
{
"file": "references/research-report.template.md",
"line_start": 157,
"line_end": 157
},
{
"file": "references/research-report.template.md",
"line_start": 158,
"line_end": 158
},
{
"file": "references/research-report.template.md",
"line_start": 159,
"line_end": 159
}
]
},
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 45,
"line_end": 48
},
{
"file": "SKILL.md",
"line_start": 48,
"line_end": 54
},
{
"file": "SKILL.md",
"line_start": 54,
"line_end": 57
},
{
"file": "SKILL.md",
"line_start": 57,
"line_end": 63
},
{
"file": "SKILL.md",
"line_start": 63,
"line_end": 73
},
{
"file": "SKILL.md",
"line_start": 73,
"line_end": 124
},
{
"file": "SKILL.md",
"line_start": 124,
"line_end": 161
},
{
"file": "SKILL.md",
"line_start": 161,
"line_end": 197
},
{
"file": "SKILL.md",
"line_start": 197,
"line_end": 198
}
]
}
],
"static_findings": [
{
"id": "filesystem:references/research-report.template.md:157:temp-directory-access",
"category": "filesystem",
"severity": "medium",
"pattern": "Temp directory access",
"file": "references/research-report.template.md",
"line_start": 157,
"line_end": 157,
"snippet": "- `/tmp/research_{{TOPIC_1}}.md`"
},
{
"id": "filesystem:references/research-report.template.md:158:temp-directory-access",
"category": "filesystem",
"severity": "medium",
"pattern": "Temp directory access",
"file": "references/research-report.template.md",
"line_start": 158,
"line_end": 158,
"snippet": "- `/tmp/research_{{TOPIC_2}}.md`"
},
{
"id": "filesystem:references/research-report.template.md:159:temp-directory-access",
"category": "filesystem",
"severity": "medium",
"pattern": "Temp directory access",
"file": "references/research-report.template.md",
"line_start": 159,
"line_end": 159,
"snippet": "- Final: `/tmp/research_final_{{TIMESTAMP}}.md`"
},
{
"id": "external_commands:SKILL.md:45:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 45,
"line_end": 48,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 48,
"line_end": 54,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:54:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 54,
"line_end": 57,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:57:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 57,
"line_end": 63,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:63:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 63,
"line_end": 73,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:73:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 73,
"line_end": 124,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:124:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 124,
"line_end": 161,
"snippet": "```markdown"
},
{
"id": "external_commands:SKILL.md:161:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 161,
"line_end": 197,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:197:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 197,
"line_end": 198,
"snippet": "- **`references/RESEARCH_REPORT.template.md`** - Research report template with key findings, evidenc"
},
{
"id": "blocker:SKILL.md:112:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "SKILL.md",
"line_start": 112,
"line_end": 113,
"snippet": "- **Why They're a Good Fit**: Specific reasons based on their business"
},
{
"id": "obfuscation:references/research-report.template.md:1:heuristic-multiple-bracket-chains-12-jsfuck-obfu",
"category": "obfuscation",
"severity": "high",
"pattern": "[HEURISTIC] Multiple bracket chains (12) - JSFuck/obfuscation pattern",
"file": "references/research-report.template.md",
"line_start": 1,
"line_end": 1,
"snippet": "]({{, }})), ]({{"
}
],
"finding_verdicts": [
{
"id": "filesystem:references/research-report.template.md:157:temp-directory-access",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "This is a Markdown artifact list in a report template, not code that reads or writes /tmp. It contains a placeholder filename only and no secret access path."
},
{
"id": "filesystem:references/research-report.template.md:158:temp-directory-access",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "This is another placeholder artifact path in the same Markdown template. No executable logic, file read, or file write behavior is present."
},
{
"id": "filesystem:references/research-report.template.md:159:temp-directory-access",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "The line documents a final report artifact path with a timestamp placeholder. It is not an instruction that accesses arbitrary files or sensitive directories."
},
{
"id": "external_commands:SKILL.md:45:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The detected token is a Markdown fenced prompt example, not Ruby backtick execution. The block contains user-facing text and no shell command."
},
{
"id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "This closing fence belongs to a Markdown usage example. There is no command invocation, interpreter call, or user-controlled shell execution."
},
{
"id": "external_commands:SKILL.md:54:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The snippet opens a Markdown example showing how a user might ask for repository analysis. It does not execute code or call an external process."
},
{
"id": "external_commands:SKILL.md:57:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The detected marker closes a Markdown code fence. The surrounding content is natural language prompt guidance, not shell execution."
},
{
"id": "external_commands:SKILL.md:63:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "This is a fenced Markdown prompt template for advanced lead research. It contains placeholders and profile fields, not executable commands."
},
{
"id": "external_commands:SKILL.md:73:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The marker closes the advanced usage Markdown block. The file provides instructions for response content and no shell command path is present."
},
{
"id": "external_commands:SKILL.md:124:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "This starts a fenced Markdown output-format example. The content is a report layout, so the Ruby backtick execution signature is not applicable."
},
{
"id": "external_commands:SKILL.md:161:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The line closes the Markdown output example. It does not contain Ruby code, shell interpolation, or external command execution."
},
{
"id": "external_commands:SKILL.md:197:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticks are inline Markdown formatting around reference filenames. They are not executable syntax and do not invoke a shell."
},
{
"id": "blocker:SKILL.md:112:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "The cited lines describe why a company is a good sales fit in an output template. They do not instruct network scanning, port probing, or service enumeration."
},
{
"id": "obfuscation:references/research-report.template.md:1:heuristic-multiple-bracket-chains-12-jsfuck-obfu",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "Line 1 is YAML front matter and the bracket-chain heuristic appears to come from Markdown links and template placeholders elsewhere in the document. No JavaScript or obfuscated executable payload is present."
}
],
"semantic_findings": [
{
"title": "Dual-use lead targeting from sensitive exposure signals",
"description": "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.",
"severity": "medium",
"locations": [
{
"file": "SKILL.md",
"line_start": 173,
"line_end": 181
}
],
"confidence": 0.78,
"confidence_reasoning": "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."
}
],
"critical_findings": [],
"high_findings": [],
"medium_findings": [
{
"title": "Dual-use lead targeting from sensitive exposure signals",
"description": "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.",
"locations": [
{
"file": "SKILL.md",
"line_start": 173,
"line_end": 181
}
],
"review_kind": "security",
"source_category": "semantic",
"source_severity": "medium",
"confidence": 0.78,
"confidence_reasoning": "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."
}
],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 3,
"total_lines": 591,
"audit_model": "codex",
"audited_at": "2026-07-05T12:46:16.621Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Find Qualified Sales Leads",
"value_statement": "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.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"lead research",
"sales prospecting",
"account qualification",
"business development",
"outreach strategy",
"competitive research",
"market research"
],
"actual_capabilities": [
"Analyzes a product, service, or repository to infer value proposition and buyer fit.",
"Defines ideal customer profile criteria such as industry, company size, location, and pain points.",
"Finds and ranks target companies using fit scores and evidence-based reasoning.",
"Suggests decision-maker roles, outreach angles, and conversation starters for each account.",
"Formats results as a lead research summary with clear next steps."
],
"limitations": [
"Requires current web access or supplied source material for real company research.",
"Fit scores are estimates and should be verified before sales action.",
"Does not guarantee accurate contact details or private decision-maker information.",
"Users must follow privacy, anti-spam, and platform rules when using outputs."
],
"use_cases": [
{
"title": "Build a launch account list",
"description": "Identify companies that match a new product and rank them by buyer fit, urgency, and outreach angle.",
"target_user": "Sales development representative"
},
{
"title": "Validate early customer segments",
"description": "Compare potential customer groups and find accounts that show clear need, budget signals, and timing indicators.",
"target_user": "Founder"
},
{
"title": "Find partnership targets",
"description": "Research companies with complementary products and prepare practical talking points for business development conversations.",
"target_user": "Business development manager"
}
],
"prompt_templates": [
{
"title": "Find Initial Leads",
"scenario": "Beginner sales research",
"prompt": "Analyze this product: [description]. Find 10 companies that could benefit. Include fit scores, reasons, and outreach angles."
},
{
"title": "Research a Target Segment",
"scenario": "Focused account discovery",
"prompt": "My ideal customers are [industry], [size], in [region]. Find 15 accounts and explain the strongest buying signals."
},
{
"title": "Use Repository Context",
"scenario": "Product-led qualification",
"prompt": "Review this repository to understand the product. Then identify target companies, decision-maker roles, and tailored value propositions."
},
{
"title": "Compare Segments and Prioritize",
"scenario": "Advanced go-to-market planning",
"prompt": "Compare these segments: [segment list]. Score each segment, choose the best accounts, and recommend a first outreach plan."
}
],
"output_examples": [
{
"input": "Find leads for a privacy tool that helps engineering teams protect AI assistant prompts.",
"output": "A ranked list of security-conscious software companies, fit scores, buyer roles, evidence, and suggested outreach themes."
},
{
"input": "Research Bay Area companies that recently moved to remote work and may need team productivity consulting.",
"output": "A prospect table with remote-work signals, company context, priority levels, and practical conversation starters."
},
{
"input": "Use my repository to understand the product and find enterprise partnership targets.",
"output": "A summary of the product value, ideal partner traits, matched companies, and recommended next research steps."
}
],
"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."
],
"anti_patterns": [
"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."
],
"faq": [
{
"question": "What inputs should I provide?",
"answer": "Provide your product, target customer profile, geography, company size, and any industries to include or exclude."
},
{
"question": "Can it analyze my codebase?",
"answer": "Yes. Run it from a product repository and ask it to infer the value proposition before researching leads."
},
{
"question": "Does it find verified email addresses?",
"answer": "No. It focuses on company research, buyer roles, and outreach strategy, not private contact harvesting."
},
{
"question": "How are lead scores created?",
"answer": "Scores are based on visible fit signals, pain points, timing indicators, and alignment with your ideal customer profile."
},
{
"question": "Can it create CRM-ready output?",
"answer": "It can structure results for CRM review, but users should verify data before importing or contacting prospects."
},
{
"question": "What tools support this skill?",
"answer": "The report lists support for Claude, Codex, and Claude Code."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "competitive-analysis.template.md",
"type": "file",
"path": "references/competitive-analysis.template.md",
"lines": 205
},
{
"name": "research-report.template.md",
"type": "file",
"path": "references/research-report.template.md",
"lines": 171
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 215
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |