Help us improve
Share bugs, ideas, or general feedback.
From claude-plugin
Generates a holistic, scored, SDR/AE-ready list of accounts to focus on today — combining ICP fit, dev funnel stage, activity score, and recency momentum signals from reo, with territory and CRM stage acting as hard filters. Uses the fast reo_get_daily_focus_list composite endpoint — a single API call that returns pre-scored, pre-ranked, pre-enriched accounts. Use this skill whenever someone asks: "what accounts should I focus on today?", "give me my daily account list", "who should I call today?", "prioritize my accounts", "show me my hot list", "rank accounts by fit", "build my SDR list", "score my accounts", or any request for a ranked or scored account list. Always trigger this skill for daily pipeline triage workflows.
npx claudepluginhub reodotdev/claude-plugin --plugin reo-mcp-toolsHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-plugin:daily-account-prioritizer-v2The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill produces a ranked, scored list of accounts for an SDR or AE to act on
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Create and present web-based slidedecks using Slidev with Markdown, Vue components, code highlighting, animations, interactive demos, LaTeX, and Mermaid for technical presentations, conference talks, code walkthroughs, and teaching materials.
Share bugs, ideas, or general feedback.
This skill produces a ranked, scored list of accounts for an SDR or AE to act on
today. It uses the reo_get_daily_focus_list composite endpoint — a single API
call that handles all data fetching, filtering, scoring, and enrichment server-side.
The composite endpoint computes all scores server-side. Claude does NOT need to
calculate any of these — they arrive pre-computed in the response. This reference
is for understanding the dashboard display:
| Component | Weight | What it measures |
| -------------- | ------ | ------------------------------------------------------------------- |
| ICP fit | 20 | Customer fit tier (STRONG=20, MODERATE=10) |
| Funnel fit | 25 | Developer stage (DEPLOY=25, BUILD=17, etc.) |
| Activity score | 25 | Developer activity score × 0.25, capped at 25 |
| Recency score | 30 | Activity delta (15) + Mgr+ identified (10) + Δ deanon devs (5, n/a) |
Max attainable: 95 (Δ deanon dev scoring is unavailable).
Ask once: "What's your territory? (e.g. US + Canada, EMEA, or 'global')"
Wait for the answer unless it's obvious from context or a prior conversation.
Map the answer to a country_list array:
Call reo_get_daily_focus_list with:
reo_get_daily_focus_list(
country_list = ["United States", "Canada"], // from Step 0
top_n = 20,
recency_days = 7,
customer_fit_score = ["STRONG", "MODERATE"],
excluded_crm_stages = ["Customer", "Closed Lost", "Churned", "Disqualified", "CUSTOMER"]
)
This single call returns everything:
| Response Field | What It Contains |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| meta | Timestamp, territory, filters applied, pool stats |
| meta.pool_stats | total_accounts_fetched, after_hard_filters, stage_a_shortlist, final_top_n |
| accounts[].scores | Pre-computed: icp_fit, funnel_fit, activity_score, stage_a, delta_activity, delta_activity_pts, mgr_plus, mgr_plus_name, mgr_plus_pts, recency, composite |
| accounts[].top_activities | Up to 3 recent high-signal activities per account |
| accounts[].developers | Up to 3 deanonymized developers with email, title, LinkedIn |
| accounts[].prospects | Up to 3 LinkedIn prospects with tech_function_match flag |
If the response has fewer than 5 accounts, note it in the dashboard banner. The
endpoint has already applied all filters — a small result set means the territory
or recency window is genuinely narrow.
For each account, Claude adds two pieces of natural language intelligence that
the endpoint cannot generate:
This must be specific to actual signals, people, and dates. It is the single most
important line on each card — an SDR will decide whether to act based on this.
Good examples:
Bad examples (never produce these):
Base this on the combination of funnel stage, scores, and people identified:
| Signal Pattern | Action Template |
| ----------------------------------------- | -------------------------------------------- |
| DEPLOY + high recency | "Call today — expansion signal" |
| DEPLOY/BUILD + Mgr+ identified | "Book a meeting with [mgr_plus_name]" |
| High activity + multiple developers | "Multi-thread: reach [dev1] and [prospect1]" |
| DISCOVER + strong ICP + rising activity | "Send targeted content + monitor this week" |
| Strong ICP + flat activity | "Warm outbound to [prospect name]" |
| High activity + MODERATE ICP | "Qualify before investing time" |
| prospects with tech_function_match = true | Prioritize those contacts in the action |
Generate a single self-contained dark-mode HTML dashboard file. Save to outputs
folder and share the link.
Each card contains:
3–5 sentences in chat alongside the dashboard link:
Response field reference — exact paths in the reo_get_daily_focus_list response:
Per account:
Activity signal hierarchy (for narrating "Why it's here"):
FORM_CAPTURE > DEMO_LOGIN > COPY_TEXT/COPY_COMMAND > PAGE_VISIT > Identity
Relative time display: convert timestamp to relative format for the dashboard: