score-my-list

Look up a person and get their verified phone numbers, email, and company context. Use when the user says "look up [name]", "get me the contact info for [person]", "find [name]'s phone number", "who is [name] at [company]", "enrich [email or name]", or any request to retrieve a single person's contact details.

Find companies or contacts similar to a set of references, then enrich results with verified phone numbers. Use when the user says "find companies like my best customers", "find more contacts like these", "expand from these accounts", "who else looks like [company]", "find similar companies to [list]", or any request to discover lookalike targets from a reference set. Requires at least 5 reference companies or contacts for quality results.

Builds a reusable outreach positioning brief: what the user's company sells, to which personas, with what proof, and against which competitors. Use when asked to build, review or update a positioning brief (including a pasted lusha-outreach-brief), run outreach research, or work out what to say to prospects before drafting ("lusha outreach brief"). Not for drafting emails: use outreach-sequence once a brief exists.

Drafts personalized B2B outreach (Email 1, optional Email 2 and 3, and LinkedIn copy) for contacts the user already has, from an outreach-research positioning brief plus Lusha buying signals. Use when asked to draft outreach, write emails or LinkedIn messages for a contact list or CSV, or personalize a sequence ("lusha outreach sequence", "write email 1 for this list"). Not for building the brief: use outreach-research first.

Build a targeted list of contacts or companies from Lusha and return verified phone numbers alongside emails. Use when the user says "find me [title] at [company type]", "build a list of [ICP description]", "prospect [criteria]", "who should I be calling at [industry]", or any request to generate a lead list from an ICP or persona description.

Save Lusha contacts or companies from this conversation to a Lusha Workspace table, or export them to the user's CRM (Salesforce, HubSpot and other supported CRMs). Use when the user says "save these to a table", "add them to my Lusha list", "put this in a Workspace table", "export to HubSpot", "push these to Salesforce", "send to my CRM", "sync these leads", or picks the save or export next step at the end of another Lusha skill. Works on Lusha ids already in the conversation; to find new people or companies, use prospect, signal-prospect or lookalike-prospect first.

Set up the user's Ideal Customer Profile (an ICP Target Profile in Lusha) by asking the profile questions one at a time, drafting each answer from what is already known about their company and customers, then creating the profile and previewing 10 matching accounts. Use when the user says "set up my ICP", "define my ideal customer", "who's my ideal customer", "create a target profile", "teach Lusha who I sell to", "my recommendations are off", or when another Lusha skill sends them here because no profile exists. Not for a one-off search by criteria: use prospect.

Find companies or contacts triggered by a buying signal, then surface verified phone numbers for the right decision makers. Use when the user says "find companies that just raised funding", "who's surging in sales hiring right now", "show me companies with headcount growth", "find contacts who just got promoted", "who changed jobs recently in [industry]", "show me [title] at companies that just [signal event]", or any request that starts with a real-world trigger rather than a static filter.

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.

Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.

Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.

Obtain or reuse a Prisma Postgres database and connect an application. Use when the user needs a database and has none configured ("I need a database", "add a Postgres database", "set up a database for this app"), runs or mentions `create-db` or `npx create-db`, or asks to set up or connect Prisma Postgres, including in v0 and the Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; reuses an existing connection first and honors an explicit provider, driver, alternative ORM, or database-only choice.

Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching (including schema-only, reset-from-parent, and branch-per-PR workflows), autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, egress optimization, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Live queries, reactive UIs, and realtime data go to `neon-realtime`. Also use for "@neondatabase/serverless", "@neon/neon-js", "neon inspect db", "neon postgres computes", "Neon branch", "schema-only branch", "reset branch", "branch per PR", high database bills, network transfer or egress, SELECT * optimization, query overfetching, "semantic search", "vector search", "full-text search", "BM25", or "hybrid search".