Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill analytics-adoption-strategygit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/analytics-adoption-strategy)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/analytics-adoption-strategy"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/analytics-adoption-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/analytics-adoption-strategy"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/analytics-adoption-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00142 | $0.04256 |
| Opus 5 | $0.00071 | $0.02128 |
| Sonnet 5 | $0.00028 | $0.00851 |
| Haiku 4.5 | $0.00014 | $0.00426 |
Grade A, and why
analytics-adoption-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Adoption Strategy
This skill activates when an org has built CRM Analytics dashboards and apps but needs a strategy to drive usage — measuring who opens what, making dashboards discoverable in context, enabling self-service for non-analyst users, and defining the right success metrics. It covers the strategy and configuration layer above technical dashboard construction.
Before Starting
Gather this context before working on anything in this domain:
- Is the Analytics Adoption Metadata managed package installed? This is a hard prerequisite for creating the Salesforce-provided Analytics Adoption App template. Without the package the template cannot be created and usage tracking will not work. Confirm in Setup > Installed Packages before advising on the Adoption App.
- Which user personas need analytics access? Executives, operations managers, and field reps have radically different discovery paths — executives want pinned home-page dashboards, field reps need dashboards embedded in record pages they already open, and analysts want direct Analytics Studio access.
- What is the actual adoption problem? Low usage usually falls into one of three categories: users cannot find dashboards (discoverability), users open dashboards but find them irrelevant or confusing (relevance/design, not a strategy problem — escalate to analytics-dashboard-design), or users do not trust the data (data quality — escalate to the appropriate data skill). Strategy interventions only fix the first category.
- Do not confuse the Salesforce Adoption Dashboards AppExchange package (Salesforce Labs, tracks CRM record creation and login frequency) with the Analytics Adoption App (tracks CRM Analytics-specific usage: app opens, dashboard opens, lens opens). They track completely different things and require different setup steps.
Core Concepts
The Analytics Adoption App
Salesforce ships a first-party template app specifically for measuring CRM Analytics usage. It tracks who opened which app, dashboard, and lens — and when. This is separate from general Salesforce adoption metrics.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 265 lines · 142 tokens per session scan A 8a6f3d4b2d7c
analytics-adoption-strategy is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 142 tokens to every session and 4,256 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
analytics-adoption-strategy
Use this skill when driving adoption of CRM Analytics (Einstein Analytics) across an org — the Analytics Adoption App for measuring who uses which dashboards, embedding analytics into Lightning pages, pinning dashboards to the Analytics home page, self-service personas, and analytics success metrics. Triggers…
setup-platform-development
Help set up the platform development policy — contribution mode, governance, and sharing.
ai-adoption-change-management
Use this skill when planning or executing the human side of an Agentforce or Einstein AI feature rollout — user trust-building, AI-specific training, structured feedback collection via the Feedback API, and adoption measurement via Agentforce Analytics. NOT for turning the Einstein for Sales features on — use…
analytics-permission-and-sharing
Configure CRM Analytics (formerly Einstein Analytics) app sharing, dataset-level permissions, row-level security predicates, sharing inheritance, and license assignment. Trigger keywords: CRM Analytics security, row-level security predicate, dataset permissions, analytics sharing inheritance, Analytics Plus license.…
case-management-setup
Configuring Salesforce case management: case queues, assignment rules, escalation rules, auto-response rules, Email-to-Case, Web-to-Case, case teams, entitlements, and milestones. Use when setting up or troubleshooting the Service Cloud case handling layer. Trigger keywords: email-to-case, web-to-case, escalation…
change-advisory-board-process
Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment.…