Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Research and qualify B2B prospects using web search. Builds structured profiles with company intel, key contacts, pain points, and engagement recommendations.
Research and qualify B2B prospects using web search. Builds structured profiles with company intel, key contacts, pain points, and engagement recommendations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
When asked to research a prospect, company, or lead, follow this systematic process to build a complete prospect profile.
Search for and gather: Company name, website, HQ location What they do โ one-sentence summary a human would understand Industry and sub-sector Founded year, employee count, funding stage/revenue range Key products or services
Search for recent news, press releases, job postings, and social activity: Funding rounds or acquisitions Product launches or pivots Leadership changes (new CTO, VP Eng, etc.) Hiring patterns โ what roles are they hiring for? (signals priorities) Partnerships or integrations announced
Where possible, identify: Tech stack signals from job postings, BuiltWith, GitHub, or blog posts Tools and platforms they use (CRM, cloud provider, etc.) Technical blog or engineering culture signals
Identify 2-5 relevant decision-makers or influencers: Name, title, LinkedIn URL (if publicly available) Recent public activity (posts, talks, articles) Likely priorities based on role
Based on all gathered intel, infer: Likely challenges given their stage, industry, and hiring patterns Gaps in their stack that your solution could fill Timing signals โ why now might be the right time to reach out
Synthesize into: Qualification score: Hot / Warm / Cold (with reasoning) Best entry point: Which contact, which angle Suggested opener: A 2-sentence personalized hook based on real intel Channels: LinkedIn, email, warm intro, event-based, etc.
Use the research template at {baseDir}/research-template.md as the output structure. Fill in every section. Mark unknowns as "Not found" rather than guessing.
Only use publicly available information. No scraping behind logins. Cite sources โ include URLs for key claims. Be specific over generic. "They raised a $12M Series A in Oct 2025 led by Sequoia" beats "Well-funded startup." Flag uncertainty. If a data point is inferred rather than confirmed, say so. Prioritize recency. Information from the last 6 months weighs more than older data. Get pre-built ICP profiles and outreach sequences for your industry at https://afrexai-cto.github.io/context-packs
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.