# Account Signal Analysis

Explains what changed with an account and ranks accounts needing attention from evidence.

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: Business
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill analyze-account-signals -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill analyze-account-signals -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill analyze-account-signals -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill analyze-account-signals -g -a gemini-cli -y`

## Description

Use when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Analyze Account Signals


## Context-Gathering Intake

Whenever this skill asks for context, strongly prefer using the `answers-ask-user-input` skill and the `ask_user_input` tool over other tools such as `request_user_input`; otherwise ask directly in the conversation.

Turn fresh account evidence into a concise view of what changed, why it matters, and what to do next. This skill owns a read-only account brief or bounded watchlist summary; it does not create tasks, post digests, store monitoring state, or write CRM updates.

## Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to `plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices`.

## Key Dependency Categories

These categories are particularly important for this workflow; use other sources only when they materially improve the signal story.

- [Blocking] ~~CRM for authoritative account identity, owner, opportunity, stage, amount, activity, customer-health, and account-status truth. It blocks the default account-signal readout unless sufficiently complete account truth is already grounded in context.
- ~~Meeting Transcripts for recent customer language, decisions, commitments, objections, follow-ups, and stakeholder movement
- ~~Email for customer-facing progression, unanswered asks, tone shifts, attachments, and promised next steps
- ~~Internal Messaging for internal coordination, blockers, stakeholder alignment, and escalation signals
- ~~Knowledge & Files for account plans, notes, briefs, implementation docs, and prior account context
- ~~Calendar for recent or upcoming customer sessions, commitments, and scope reduction for large portfolios

Use ~~CRM as the default account anchor. Use sufficient user-provided/exported account truth only as a fallback when CRM cannot be used. Communications, files, and calendar evidence explain recency and movement; they do not override CRM-owned account or opportunity fields.

## Reference Loading

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/sales/workflows/analyze-account-signals/SKILL.md