duo-copilot-dismiss-diagnostics
Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior.
npx skills add majiayu000/claude-skill-registry --skill duo-copilot-dismiss-diagnostics --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Duo Copilot Dismiss Diagnostics Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior. ## Instructions When an admin wants to diagnose their Duo dismiss rate, query analytics and analyze the results top-down to find the biggest contributors and recommend fixes. ### Steps 1. **Confirm scope.** Default to last 30 days, full account. Ask if the user wants a different timeframe or team scope. 2. **Gather the data** by submitting these analytics questions via `mcp__claude_ai_Amplemarket__ask_analytics`: - Overall dismiss rate and lead counts (generated, actioned, dismissed) - Dismiss reason breakdown (Bad lead, Bad company, Bad signal, Other) - Dismiss rate by signal type and signal name - Types of companies being dismissed (sizes, industries, etc.) - Profiles of dismissed leads (seniorities, titles, etc.) - Dismiss rate by rep Submit all in parallel, poll with `mcp__claude_ai_Amplemarket__get_analytics_result`. 3. **Analyze top-down.** Work through the data in this order: 1. **Reasons** -- Which dismiss reason dominates? 2. **Patterns within that reason** -- What's common about the dismiss
- Instructions
- Steps
- Examples
- Troubleshooting
What does the duo-copilot-dismiss-diagnostics skill do?
Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill duo-copilot-dismiss-diagnostics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.