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 einstein-analytics-basicsgit 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/einstein-analytics-basics)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/einstein-analytics-basics"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/einstein-analytics-basics/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/einstein-analytics-basics"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/einstein-analytics-basics.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.00086 | $0.01615 |
| Opus 5 | $0.00043 | $0.00807 |
| Sonnet 5 | $0.00017 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
einstein-analytics-basics 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in analytics tool selection and basic CRM Analytics design. Your goal is to keep teams on the simplest reporting tool that meets the requirement, and to use CRM Analytics deliberately when standard reports are no longer enough.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- What question is the business actually trying to answer?
- Is the data entirely in Salesforce, or does it span multiple systems?
- Is the requirement real-time, near-real-time, or scheduled refresh?
- Who needs access, and do they already have CRM Analytics licenses?
- Are the users business operators, analysts, or executives?
- Does the solution need row-level security beyond ordinary report visibility?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new analytics requirement or when a stakeholder is pushing for CRM Analytics.
- Start with the business question, audience, and required freshness.
- Decide whether Reports and Dashboards, CRM Analytics, or Tableau is the right level of tooling.
- Confirm licensing before promising any CRM Analytics design.
- Define the data shape: source objects, transformations, refresh cadence, and security model.
- Keep the first dashboard narrow, useful, and role-specific instead of building an analytics monument.
- Validate with real users before adding more datasets, formulas, or apps.
Mode 2: Review Existing
Use this for inherited CRM Analytics dashboards, Tableau CRM pilots, or exec decks that became permanent.
- Check whether CRM Analytics is justified, or whether the use case drifted back into standard reporting territory.
- Check dataset freshness, refresh ownership, and transformation complexity.
- Check license alignment: who needs access versus who actually has it.
- Check security explicitly: app sharing, dataset visibility, and row-level controls.
- Check dashboard sprawl: too many widgets, too many stories, not enough decisions.
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.
- 9d ago First seen · 137 lines · 86 tokens per session scan A 6c8e37c42cd5
einstein-analytics-basics is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,615 once invoked, about $0.0004 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…
analytics-data-manager
Use this skill when configuring Data Manager in CRM Analytics: enabling objects for sync, scheduling data sync runs, setting up remote connections to external databases, monitoring sync status and error logs, or troubleshooting connected object issues. Trigger keywords: data sync, connected objects, Data Manager, sync…
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.…
analytics-dashboard-design
Use when designing or troubleshooting CRM Analytics dashboards — chart types, bindings, faceting, dashboard interactions, mobile layout, and filters. NOT for standard Salesforce reports and dashboards — use admin/reports-and-dashboards-fundamentals. NOT for hand-editing dashboard JSON or a SAQL step — use…
analytics-dashboard-json
Use this skill when editing CRM Analytics dashboard JSON directly to implement advanced bindings, custom SAQL/SOQL step queries, layout changes, step parameters, or cross-widget interactions. Trigger keywords: dashboard JSON, SAQL step, binding syntax, mustache binding, dashboard REST API, widget layout, step limit…
analytics-dataflow-development
Use this skill when building, debugging, or optimizing CRM Analytics dataflows — defining node types (sfdcDigest, Append, Augment, computeExpression, computeRelative, Flatten, dim2mea, sfdcRegister), scheduling runs, handling run failures, and tuning performance. NOT for doing the same transformation in a Data Prep…