← ClaudeAtlas

account-fit-ranklisted

Rank a list of accounts (mixed Explorium business IDs, company names, or domains) by ICP fit, buying intent, recent triggers, and workforce momentum. Returns per-account composite score (0-100), tier (A/B/C), explainable component breakdown (fit / intent / trigger / workforce), and a specific "why now" sentence per account anchored on a real Explorium signal. Resolves name/domain inputs via match-business with explicit confirmation for ambiguous matches. Iteratively refinable. Use for account-based selling, ABM list prioritization, territory planning, signal-based selling, buyer-intent ranking, and B2B prospecting. Triggers on "score these accounts", "rank by ICP fit and intent", "prioritize this account list", "which accounts should I work first", "build a tiered account list", "ICP scoring", "account prioritization".
haroExplorium/sales-skills-for-claude-code-account-fit-rank · ★ 0 · Web & Frontend · score 72
Install: claude install-skill haroExplorium/sales-skills-for-claude-code-account-fit-rank
# Account Fit Rank Score and tier a list of accounts on four axes by fetching firmographics, technographics, intent, events, and workforce trends from Explorium, then applying a transparent weighted composite the calling model computes from the returned data. ## Input - Accounts (required): list of Explorium business IDs, company names, domains, or a mixed CSV. - Use case (default `prospecting`): one of `prospecting`, `abm`, `territory_planning`, `pipeline_acceleration`. Shifts tier thresholds and recommended actions. - ICP definition (required from user or session memory): industries / naics, employee buckets, revenue buckets, country or region, optional tech-stack vendors, optional intent topics. No persisted ICP exists in tool surface, so capture it inline. - Weight overrides (optional): `{fit, intent, trigger, workforce}` summing to 100. Default `45 / 25 / 25 / 5`. - Tier thresholds (optional): `{A, B}`. C is the remainder. Default `A>=75, B 50-74`. ## Workflow ### 1. Lock the ICP and intent topics Restate the ICP from the user. For each tag-style field, resolve it: `autocomplete --field linkedin_category --query <theme>` (or `naics_category` if the user is NAICS-native, never both), `autocomplete --field company_tech_stack_tech --query <vendor>` for technographic ICP checks, `autocomplete --field business_intent_topics --query <topic>` for each topic theme one at a time (fuzzy multi-term queries fail silently). If a tag does not resolve, drop it and flag that axis as