Guide · Agent skill
How to use the Analyze Account Signals agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
Analyze Account Signals is an agent skill for sales work. Once it is installed, you can ask your agent what changed with one customer account, or which accounts in your portfolio need attention, and it will return a read-only brief or watchlist summary with recommended actions. This guide explains what the skill does, how to install it, how to trigger it, what it needs, and where to be careful.
Quick start
- 1Download the ZIP. Download the skill ZIP from this directory page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ inside a project for project-only use.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Confirm your CRM connection. Make sure your agent can reach the CRM app you use, since the skill needs it as the account source of truth.
- 5Ask for a brief or a summary. Request an account brief for one account, or a monitor summary for an owner, territory or watchlist, in plain language.
- 6Answer the scope question. If the request is unclear, choose the mode, account or scope the skill offers using ask_user_input or the conversational fallback.
- 7Review the citations and actions. Check each signal's evidence and citation, then decide which recommended actions to carry out yourself.
What is an agent skill and what does this one do?
An agent skill is a folder of instructions and supporting files that an AI agent loads when a request matches the skill's description. This skill is written for sales account owners and managers who already keep account data in a CRM.
The skill gathers recent evidence about accounts from connected sources such as CRM, email, meeting transcripts, internal messages, files and calendar. It sorts that evidence into a fixed set of signal types, such as momentum, expansion opportunity and churn/risk, and then writes an evidence-backed account brief or a bounded watchlist summary with recommended actions.
- Adhoc Account Brief: one account, for example before a customer call.
- Monitor Summary: an owner portfolio, territory or watchlist, ranked by which accounts need attention.
- Read-only: it does not create tasks, post digests, store monitoring state or write updates back to CRM.
Install the skill from a ZIP file
Download the ZIP for the skill from this directory page. Unzip it into one of the following locations, depending on how you want to use it.
For a personal install that is available across your projects, unzip it into your user skills folder at ~/.claude/skills/. To limit it to one project, unzip it into the .claude/skills/ folder inside that project.
If you use the Claude apps instead of a folder on your computer, upload the skill under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload
Check what the skill needs before you start
The skill treats CRM as the authoritative source for account identity, owner, opportunity, stage, amount, activity and account status. It blocks the default account-signal readout unless enough account truth is already available in context. Without CRM or similar account data, the brief will be incomplete or unreliable, so do not expect good results from this skill alone.
Email, meeting transcripts, internal messaging, knowledge and files, and calendar are optional. Each one adds detail about recent movement. The skill uses them to explain recency and momentum, but they do not override CRM fields.
For clarifying questions, the skill prefers the ask_user_input tool and falls back to asking in the conversation if that tool is not available.
- Required: a CRM connection
- Optional: email, meeting transcripts, internal messaging, knowledge and files, calendar
- Clarifying questions: ask_user_input tool, or a conversational fallback
Trigger the skill with natural requests
You do not need a special command. Describe what you want in plain language and the agent will match the request to the skill. The skill's description covers requests about what changed with one account, monitoring an owner portfolio or watchlist, and ranking accounts that need attention.
If your request is vague, the skill will not guess. For a bare request such as "Analyze account signals for me", it offers three choices: an Adhoc Account Brief for one account, a Monitor Summary for accounts you own in CRM, or a Monitor Summary for a watchlist, owner or territory.
- What changed with [account name] in the last two weeks?
- Which accounts I own need attention this week?
- Give me a watchlist summary for these accounts: [list]
- Prepare an account brief for [account] before my call tomorrow.
Understand the scope and time window
An Adhoc brief needs exactly one account, identified by CRM id, exact name or domain, or detailed account context. If you name an account that is not clear, the skill offers up to five candidates to pick from before it pulls deeper evidence.
A Monitor summary needs a watchlist, owner, territory or portfolio. It is capped at 50 accounts. If your scope is larger, the skill uses upcoming external customer meetings over the next 14 days to narrow it, and if that is not enough it asks you for a narrower scope.
The default time window is the last 14 days. Tell the skill a different window if you need one, and name any focus areas you care about, such as expansion, churn, rollout blockers or stakeholder movement.
- Adhoc: one account
- Monitor: up to 50 accounts, or a narrower list if the scope is larger
- Default window: last 14 days
Read the output and act on it
Each signal in the output includes its type, a summary, the source, recency, confidence, evidence, a citation and a suggested action. Several sources describing the same event raise confidence. Weak, stale or contradictory evidence lowers it, and the skill may list it as an evidence gap.
The skill separates real account risk from hygiene-only issues such as ownership gaps or missing routing fields. Treat recommended actions as suggestions: the skill does not change CRM, create tasks or post anything, so you or your team must make those changes.
- Check the citation before you act on a signal.
- Look for the evidence gap section when sources were thin.
- Where a source was checked and had no match, the output says checked/no match when that affects confidence.
What people use it for
- Before a customer call, get a brief showing what changed with the account in the last 14 days and why it matters.
- Review your own CRM portfolio each week to see which accounts need attention first.
- Check a territory or named watchlist for stalled workstreams, unresolved blockers or expansion signals.
- Prepare a manager view of accounts needing attention across a team's owners, scoped to a watchlist you supply.
Frequently asked questions
How do I install the analyze-account-signals skill?
Download the ZIP from this directory page and unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project. In the Claude apps, upload it under Settings → Capabilities → Skills.
Do I need a CRM to use this skill?
Yes, in practice. The skill treats CRM as the authoritative source and blocks the default account readout without sufficiently complete account data. Without CRM or similar account data, the briefs will be incomplete or unreliable.
Is the Analyze Account Signals skill free?
The source lists the skill under the MIT licence. The source does not state pricing for the wider product or for your CRM and connected tools, so check those separately.
Does the skill update my CRM or create tasks?
No. The skill is read-only. It does not create tasks, post digests, store monitoring state or write CRM updates. It only produces a brief or watchlist summary with recommended actions.
Does the skill run scripts or access the network?
It does not run scripts, according to the listing. It does use the network, because it reads from connected sources such as CRM, email, meeting transcripts, files and calendar. Review which connections you grant.
How is this different from general company research?
The skill is built around account and opportunity fields, such as owner, stage, amount and activity. It is not designed for general company research or non-sales uses.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a sales account owner or manager who already keeps accounts in a CRM and wants a fast, cited view of what changed before a call or across a portfolio. Pick something else if you lack CRM data, need automatic CRM updates or task creation, or want general company research.
Download the skill