Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Extruct List Building Skill

v1.0.0

Build targeted company lists for outbound campaigns using Extruct. Use when the user wants to: (1) find companies matching an ICP, (2) build a prospect or ou...

0· 70·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for zkid18/extruct-list-building.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Extruct List Building Skill" (zkid18/extruct-list-building) from ClawHub.
Skill page: https://clawhub.ai/zkid18/extruct-list-building
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install extruct-list-building

ClawHub CLI

Package manager switcher

npx clawhub@latest install extruct-list-building
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's described purpose (build company lists via Extruct) matches the instructions: all API calls are delegated to an extruct-api skill and the SKILL focuses on query design and workflows. HOWEVER the skill does not declare any dependency on the extruct-api skill in its metadata or requirements even though it repeatedly instructs the agent to call that skill and to read its SKILL.md. The implicit dependency should be declared so users can verify the other skill.
Instruction Scope
The SKILL.md explicitly instructs the agent to read local context files at claude-code-gtm/context/{company}_context.md and claude-code-gtm/context/{vertical-slug}/hypothesis_set.md. Reading workspace context files is reasonable for building lists, but the skill does not declare these config paths in its manifest. Confirm that the agent's workspace contains only intended files and that the agent is allowed to access them. There are no instructions to access unrelated system paths, credentials, or external endpoints beyond delegating to extruct-api.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, which minimizes installation risk.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportionate to an orchestration/decision skill that delegates actual API access to another skill. However, because it delegates all Extruct API calls, any credential needs will be handled by the extruct-api skill—review that skill before trusting end-to-end behavior.
Persistence & Privilege
The skill does not request always:true nor request persistent system changes. It is user-invocable and uses normal agent invocation.
What to consider before installing
This skill is mostly a query-design and orchestration guide that delegates all API calls to an extruct-api skill. Before installing or enabling it: (1) Verify you have the extruct-api skill available and that its SKILL.md and metadata are from a trusted source—this skill implicitly depends on it but does not declare that dependency. (2) Review the extruct-api skill for required credentials and network endpoints, because those credentials will be used to run searches/enrichments. (3) Confirm the workspace paths referenced (claude-code-gtm/context/...) only contain data you want the agent to read; the skill instructs the agent to read those files but does not list them as required config paths. (4) If you cannot inspect the extruct-api skill or confirm provenance, do not enable autonomous agent invocation for this skill; require explicit user approval for any actions that run queries or upload tables. If the extruct-api dependency and provenance are provided and valid, this skill would be coherent and lower risk.

Like a lobster shell, security has layers — review code before you run it.

latestvk97aft111x7k9e4jxdzp0xxe35848418
70downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

List Building

Build company lists using Extruct, guided by a decision tree. Reads from the company context file for ICP and seed companies.

Extruct API Operations

This skill delegates all Extruct API calls to the extruct-api skill.

For all Extruct API operations, read and follow the instructions in skills/extruct-api/SKILL.md.

All company search, lookalike search, deep search, table creation, row uploads, and enrichment runs are handled by the extruct-api skill. This skill focuses on what to search for and why — the extruct-api skill handles the how.

Decision Tree

Before running any queries, determine the right approach:

Have a seed company from win cases or context file?
  YES → Lookalike Search (pass seed domain)
  NO  ↓

New vertical, need broad exploration?
  YES → Semantic Search (3-5 queries from different angles)
  NO  ↓

Need qualification against specific criteria?
  YES → Deep Search (criteria-scored async research)
  NO  ↓

Need maximum coverage?
  YES → Combine Search + Deep Search (~15% overlap expected)

Before You Start

Read the company context file if it exists:

claude-code-gtm/context/{company}_context.md

Extract:

  • ICP profiles — for query design and filters
  • Win cases — for seed companies in lookalike mode
  • DNC list — domains to exclude from results. If no DNC list exists in the context file, ask the user: (1) run an Extruct search for competitors to auto-populate, (2) accept a CSV of existing customers/partners, or (3) skip for now

Also check for a hypothesis set at claude-code-gtm/context/{vertical-slug}/hypothesis_set.md. If it exists, use the Search angle field from each hypothesis to design search queries — these are pre-defined query suggestions tailored to each pain point.

Method 1: Lookalike Search

Use when you have a seed company (from win cases, existing customers, or user input). Delegate to the extruct-api skill to run a lookalike search with the seed domain.

When to use:

  • You have a happy customer and want more like them
  • Context file has win cases with domains
  • User says "find companies similar to X"

Tips:

  • Run multiple lookalike searches with different seed companies for broader coverage
  • Combine with filters to constrain geography or size
  • Deduplicate across runs by domain

Method 2: Semantic Search — Fast, Broad

Delegate to the extruct-api skill to run semantic company search queries.

Query strategy:

  • Write 3-5 queries per campaign, each from a different angle on the same ICP
  • Describe the product/use case, not the company type
  • Deduplicate across queries by domain — overlap is expected
  • Target 200-800 companies total across all queries

Method 3: Deep Search — Deep, Qualified

Delegate to the extruct-api skill to create and run deep search tasks.

Query strategy:

  • Write queries like a job description — 2-3 sentences describing the ideal company
  • Use criteria to auto-qualify — each company gets graded 1-5 per criterion
  • Default 50 results for first pass; expand after quality review
  • Use up to 5 criteria per task; keep criteria focused and non-overlapping
  • Run separate tasks for different ICP segments

Upload to Table

After collecting results, delegate to the extruct-api skill to create a company table and upload domains. Extruct auto-enriches each domain with a Company Profile.

Re-run After Enrichment

After the list-enrichment skill adds data points to this list, consider re-running list building using enrichment insights as Deep Search criteria. For example:

  • If enrichment reveals that "companies using legacy ERP" are the best fit, create a Deep Search task with that as a criterion
  • If enrichment shows a geographic cluster, run a Search with tighter geo filters
  • This creates a feedback loop: list → enrich → learn → refine list

Result Size Guidance

Campaign stageTarget list sizeMethod
Exploration50-100Search (2-3 queries)
First campaign200-500Search (5 queries) + Deep Search
Scaling500-2000Deep Search (high result count) + multiple Search

Workflow

  1. Read context file for ICP, seed companies, and DNC list
  2. Follow the decision tree to pick the right method
  3. Draft queries (3-5 for Search, 1-2 for Deep Search)
  4. Delegate to the extruct-api skill to run queries and collect results
  5. Deduplicate across all results by domain
  6. Remove DNC domains
  7. Delegate to the extruct-api skill to upload to a company table
  8. Add agent columns if user needs custom research
  9. Ask user for preferred output: Extruct table link, local CSV, or both

Comments

Loading comments...