Skip to content

discolike/discolike-skills / skills/discover-lookalike-companies

discover-lookalike-companies

Verified

Use when the user asks for a target account list, a list of "companies like X", or to "find businesses that" match an ICP. Follow the discolike skill's access and spend rules.

Build a target account list

Follow the discolike skill's How to work rules first.

  1. Size it. MCP count-matching-domains. CLI discolike count --phrase-match "..." --country US. SDK client.count(CountParams(...)). Free.
  2. Discover. MCP discover-similar-companies. CLI discolike discover --icp-prompt "..." --domain seed.com --country US --max-records 500 --format json. SDK client.discover(DiscoverParams(icp_prompt=..., domain=[...], max_records=500)). Start at 100 to 500, inspect, then scale. Do not set an employee minimum unless asked; small-company headcount data is thin and rarely what disqualifies. After every pull, add its domains to an exclusion list: MCP save-exclusion-list, CLI discolike queries create-exclusion-list --name "tam-round-1" --domains-file round1.csv --tag tam (a domain column or one domain per line; --domain for a handful), SDK client.queries.create_exclusion_list(CreateExclusionListRequest(query_name="tam-round-1", domains=[...], tags=["tam"])). Pass that list's id as exclusion_query_id on the next pull so rounds never overlap. Save the search itself with save-mcp-query or queries save-results only when you want to rerun it later.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall