agentleFS
ozgurkarahanozgurkarahan/salesforce-meta-tool-identity-propagation/skills/customer360-correlation/SKILL.md

customer360-correlation

Skill4 starsChanged 9 months agoMITView on GitHub

How to build a unified customer view by joining Salesforce (CRM) and ServiceNow (ITSM) data. Use when a question names a customer/company, asks for a "360" or "full picture", or asks whether Salesforce cases and ServiceNow incidents are related.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If one system has no data for the company, say so explicitly rather than omitting it.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Customer 360 correlation

Uses the salesforce-crm and servicenow-itsm skills for query rules.

Steps

  1. Tell the user the plan: what you will query in each system.
  2. Salesforce (one SOQL query where possible): SELECT Id, Name, Industry, Type, AnnualRevenue, (SELECT Name, Amount, StageName, CloseDate FROM Opportunities WHERE IsClosed = false), (SELECT CaseNumber, Subject, Priority, Status FROM Cases WHERE IsClosed = false) FROM Account WHERE Name LIKE '%<company>%' LIMIT 5
  3. ServiceNow (one query per table, company names combined with ^OR): open incident, open problem, upcoming change_request for the company.
  4. Correlate using the keys below and present one unified view.

Correlation keys

  • Company: Salesforce Account.Name ↔ ServiceNow company.name. Treat legal-suffix variants as the same company ("Contoso" = "Contoso Ltd").
  • Issue: a Salesforce Case and a ServiceNow Incident for the same company whose Subject/short_description share keywords (e.g. "API gateway", "SSO", "payment") and were opened within a few days of each other are likely the same issue seen from the customer side and the IT side.

Presentation

  • Sections: Account snapshot · Open pipeline (total + deals) · Open cases · Open incidents/problems · Upcoming changes · Correlations · Suggested next steps.
  • For every correlation, state what matched (company, keywords, dates) and how confident you are. Never invent a link.
  • Lead with monetary amounts when pipeline is involved.
  • If one system has no data for the company, say so explicitly rather than omitting it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.