Agent skill · data analytics · jeremylongshore
salesforce-cost-tuning
Analyze Salesforce license, add-on, storage, event, API, support, middleware, and operating costs from current customer evidence. Use when making cost and value decisions. Trigger with "optimize Salesforce cost".
Why this skill is useful
Provides specific API optimization techniques and Salesforce pricing models that the AI wouldn't reliably generate on its own.
What it needs
Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Cost and Value Governance Overview Build a dated total-cost model that connects commercial terms and technical consumption to business outcomes without inventing public prices or savings. Prerequisites Current order forms, invoices, license assignments, add-ons, storage, support, and vendor or partner statements Org usage, API and event allocations, middleware, compute, operations, incident, and migration evidence Finance, procurement, Salesforce platform, security, data, architecture, and business owners Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce editions, licenses, add-ons, storage, event delivery, API allocations, support, and partner services are customer-specific and change over time. Public documentation cannot establish one customer's price or entitlement. Authentication Use read-only approved billing, contract, org, and telemetry evidence. Separate commercial and technical access and do not expose user-level license, compensation, customer, or record data. Instructions 1. Freeze review window, currencies, orgs, products, contracts, populations, workloads, outcomes, and accountable owners. 2. Reconcile invoices and commitments with assigned and active licenses, storage, API and event usage, add-ons, support, middleware, compute, and labor. 3. Normalize time periods and currencies while preserving source, effective date, allocation method, and confidence. 4. Identify unused or mismatched assignments, duplicate capability, retention growth, event or API pressure, support load, and architectural overhead. 5. Model bounded scenarios with commercial assumptions, technical effects, business impact, security and data risk, reversibility, and confidence. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-cost-tuning