Identifying companies via LinkedIn, locating businesses from LinkedIn data by name,industry, size, and founding year. Helping sales teams, marketers, and B2B lead-generationspecialists discover LinkedIn company profiles, research target clients, and enrichfirmographic data—suitable for customer acquisition, market research, competitor analysis,and account-based sales.
Search companies from LinkedIn filtered by industry, size and founding year. Collect firmographic data to boost client‑hunting and account‑based sales outrea...
upkuajing openapi skills
@upkuajing
What This Skill Does
Searches LinkedIn company profiles by industry, employee size, founding year, and keywords, returning firmographic data for B2B lead generation and market research. Requires an API key from UpKuaJing and bills per search call.
Replaces manual LinkedIn browsing and scattered data collection by providing structured, filterable company lists with firmographic details in a single query.
When to Use It
- Find manufacturers of a specific product type on LinkedIn
- Identify tech companies with 100-500 employees for account-based sales
- Search for companies with publicly listed email or phone contacts
- Research competitors in a given industry and founding year range
- Enrich firmographic data for a list of target client companies
- Generate a lead list of companies matching multiple criteria for outreach campaigns
Install
$ openclaw skills install @upkuajing/linkedin-company-searchLinkedIn Company Search
Search company data from LinkedIn using the UpKuaJing Open Platform API.
Overview
This skill provides access to UpKuaJing's LinkedIn company data through one list search script. API key generation and top-up are provided through the auth.py script.
Running Scripts
Environment Setup
- Check Python:
python --version - Install dependencies:
pip install -r requirements.txt
Script directory: scripts/*.py
Run example: python scripts/*.py
Important: Always use direct script invocation like python scripts/linkedin_company_search.py. Do NOT use shell compound commands like cd scripts && python linkedin_company_search.py
LinkedIn Company List Search (linkedin_company_search.py)
- Return granularity: Each company as one record
- Use cases: Focus on "which companies exist" in LinkedIn data
- Examples:
- "Find manufacturers producing LED lights"
- "Find tech companies with 100-500 employees"
- Parameters: See LinkedIn Company List
API Key and Top-up
This skill requires an API key. The API key is stored in the ~/.upkuajing/.env file:
cat ~/.upkuajing/.env
Example file content:
UPKUAJING_API_KEY=your_api_key_here
API Key Not Set
First check if the ~/.upkuajing/.env file has UPKUAJING_API_KEY;
If UPKUAJING_API_KEY is not set, prompt the user to choose:
- User has one: User provides it (manually add to ~/.upkuajing/.env file)
- User doesn't have one: You can apply using the interface (
auth.py --new_key), the new key will be automatically saved to ~/.upkuajing/.env Wait for user selection;
Account Top-up
When API response indicates insufficient balance, explain and guide user to top up:
- Create top-up order (
auth.py --new_rec_order) - Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;
Get Account Information
Use this script to get account information for UPKUAJING_API_KEY: auth.py --account_info
API Key and UpKuaJing Account
- Newly applied API key: Register and login at UpKuaJing Open Platform, then bind account
Fees
All API calls incur fees, different interfaces have different billing methods.
Latest pricing: Users can visit Detailed Price Description
Or use: python scripts/auth.py --price_info (returns complete pricing for all interfaces)
List Search Billing Rules
Billed by number of calls, each call returns up to 20 records:
- Number of calls:
ceil(query_count / 20)times - Whenever query_count > 20, must before execution:
- Inform user of expected number of calls
- Stop, wait for explicit user confirmation in a separate message, then execute script
Fee Confirmation Principle
Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.
Workflow
Choose parameters based on user intent.
Decision Guide
| User Intent | Use API |
|---|---|
| "Find companies producing XXX" | LinkedIn company list (keywords / companyNames) |
| "Find companies with email/phone" | LinkedIn company list existEmail=1 / existPhone=1 |
| "Find companies with 100-500 employees" | LinkedIn company list companySizes=["51-200","201-500"] |
| "Find companies founded after 2015" | LinkedIn company list minCompanyFounded=2015 |
Usage Examples
Scenario 1: Small Query — Search Companies
User request: "Find Chinese manufacturers producing LED lights"
python scripts/linkedin_company_search.py \
--params '{"keywords": ["LED lights"], "countryCodes": ["CN"], "existEmail": 1}' \
--query_count 20
Scenario 2: Large Query — Multiple Script Calls Required
User request: "Find 1000 US electronics companies with email addresses" Before execution inform user: ceil(1000/20) = 50 API calls, confirm before executing.
python scripts/linkedin_company_search.py --params '{"keywords": ["electronics"], "countryCodes": ["US"], "existEmail": 1}' --query_count 1000
After execution: Script responds {"task_id":"a1b2-c3d4", "file_url": "xxxxx", ……} Continue execution, append data: Specify task_id, script continues from where it left off and appends to file
python scripts/linkedin_company_search.py --task_id 'task-id-here' --query_count 2000
Error Handling
- API key invalid/non-existent: Check
UPKUAJING_API_KEYin~/.upkuajing/.envfile - Insufficient balance: Guide user to top up
- Invalid parameters: Must first check the corresponding API documentation in references/ directory, get correct parameter names and formats from documentation, do not guess
API Documentation Reference
Best Practices
-
Check API documentation:
- Before executing queries, must first check the corresponding API reference documentation
- Check references/linkedin-company-list-api.md
- Do not guess parameter names, get accurate parameter names and formats from documentation
-
Optimize query parameters:
- Use
keywords/companyNamesto filter precisely; industry and product names must be in English - Use
existEmail=1orexistValidEmail=1to filter companies with contact information - Use
countryCodesto limit country scope; usecompanySizesto limit company size
- Use
-
Large result sets:
- For large queries, pay attention to the jsonl file size
Notes
- Company records use
pidas the unique identifier - All timestamps are in seconds (incorp_date is a second-level timestamp)
- Country codes use ISO 3166-1 alpha-2 format (e.g., CN, US, JP)
- File paths use forward slashes on all platforms
- Industry names must be in English
- Search quantity affects API response time, recommend setting timeout: 120
- Prohibit outputting technical parameter format: Do not display code-style parameters in responses, convert to natural language
- Do not estimate or guess per-call fees — use
python scripts/auth.py --price_infoto get accurate pricing information - Do not guess parameter names, get accurate parameter names and formats from documentation
Related Skills
Other UpKuaJing skills you might find useful:
- linkedin-person-search — Search people from LinkedIn data
- global-company-person-search — Search people from the global company database
- global-company-search — Search companies from the global company database
- global-company-shareholder — Query shareholder list from the global company database
- global-company-employee — Query employee list from the global company database
- global-company-person-colleague — Query colleague list from the global company database
- global-company-person-alumni — Query alumni list from the global company database
- global-company-person-experience — Query work experience list from the global company database
- global-company-person-education — Query education history list from the global company database
- global-company-person-school-detail — Query school detail from the global company database
- upkuajing-global-company-people-search — Unified company and people search across all sources
- upkuajing-customs-trade-company-search — Search customs trade companies
- upkuajing-contact-info-validity-check — Check contact info validity
- phone-validity-check — Check phone number validity
- email-validity-check — Check email address validity
- domain-validity-check — Check domain validity and security
Top skills in this category
Session-logs
@guogang1024Search and analyze your own session logs (older/parent conversations) using jq.
Performs web searches using DuckDuckGo to retrieve real-time information from the internet. Use when the user needs to search for current events, documentation, tutorials, or any information that requires web search capabilities.
@10e9928aPerforms web searches using DuckDuckGo to retrieve real-time information from the internet. Use when the user needs to search for current events, documentation, tutorials, or any information that requires web search capabilities.
Computer Use
@ram-raghav-sFull desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag,...
topic-monitor
@robbyczgw-claMonitor topics of interest and proactively alert when important developments occur. Use when the user wants automated monitoring of specific subjects like product releases, news topics, technology updates, RSS/Atom feeds, or GitHub releases. Supports scheduled web search plus feed polling, boolean topic filters, AI importance scoring with sentiment tracking, smart alerts vs weekly digests, and memory-aware contextual summaries.
NotebookLM CLI
@fadelooNotebookLM CLI wrapper via `node {baseDir}/scripts/notebooklm.mjs`. Use for auth, notebooks, chat, sources, notes, sharing, research, and artifact generation/download.