agentleFS
ozgurkarahanozgurkarahan/salesforce-meta-tool-identity-propagation/skills/change-risk/SKILL.md

change-risk

Skill4 starsChanged 9 months agoMITView on GitHub

Assess the business risk of planned ServiceNow change requests against Salesforce customers with deals closing soon. Use when the user asks about a planned change, maintenance window, upgrade or migration and which customers or deals it could affect.

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:

    Do not modify the change request unless the user explicitly asks and confirms.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Change risk

Uses the salesforce-crm, servicenow-itsm and customer360-correlation skills.

Steps

  1. Changes — find the change(s) the user means, or upcoming ones: query(table="change_request", query="short_descriptionLIKE<keyword>^ORdescriptionLIKE<keyword>", fields="number,short_description,description,type,risk,impact,state,start_date,end_date,company", limit=10). ServiceNow risk/impact: 1 High, 2 Medium/Moderate, 3 Low.
  2. Exposure — identify affected customers from company and from systems named in the description (e.g. billing, payments, CRM, SSO).
  3. Deals — open opportunities for those accounts closing within 60 days: SELECT Account.Name, Name, Amount, StageName, CloseDate FROM Opportunity WHERE IsClosed = false AND Account.Name IN (...) AND CloseDate = NEXT_N_DAYS:60 ORDER BY CloseDate LIMIT 50.
  4. Service context — open incidents for the same companies (a change landing on an already unstable customer is higher risk).

Rating

  • High: change risk/impact High, or a deal ≥ $250K closes within 14 days of the window, or a P1/P2 incident is open for that customer.
  • Medium: deals close within 60 days of the window, or risk/impact Medium.
  • Low: otherwise.

Output

Per change: number, summary, window, risk/impact → affected accounts table (Account · Deal · Amount · Close date · Open incidents · Rating) → total pipeline exposed → recommendations (notify account owners, adjust the window, confirm the rollback plan). Do not modify the change request unless the user explicitly asks and confirms.

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.