revenue-at-risk
Skill4 starsChanged 9 months agoMITView on GitHub
Quantify sales pipeline exposed to service issues by crossing high-priority ServiceNow incidents with open Salesforce opportunities. Use for "revenue at risk", "which deals are affected by incidents", P1/P2 impact, executive cross-system reports, or ranking accounts by risk.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- change-riskSkill
- customer360-correlationSkill
- meeting-prepSkill
- salesforce-crmSkill
- servicenow-itsmSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If an incident has no company, infer it from short_description/description only when the name is explicit, and say you inferred it.
- Distinctive: line 29
Start with the headline: total pipeline at risk and the number of accounts.
- Distinctive: line 35
If no high-priority incidents are open, say so and stop.
≈ “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.
Files
Revenue at risk
Uses the salesforce-crm, servicenow-itsm and customer360-correlation skills.
Steps
- Incidents — one ServiceNow query:
query(table="incident", query="priority<=2^state<6^ORDERBYpriority", fields="number,short_description,priority,state,company,opened_at", limit=50). If an incident has no company, infer it fromshort_description/descriptiononly when the name is explicit, and say you inferred it. - Affected companies — distinct company names from step 1.
- Pipeline — one SOQL query for all of them:
SELECT Account.Name, Name, Amount, StageName, CloseDate FROM Opportunity WHERE IsClosed = false AND Account.Name IN ('A','B',...) ORDER BY Amount DESC LIMIT 100 - Compute per account: open pipeline total, number of P1 and P2 incidents, nearest close date.
- Rank accounts by risk: P1 before P2, then pipeline amount, then nearest close date.
Output
- Start with the headline: total pipeline at risk and the number of accounts.
- Table: Account · Pipeline at risk · P1 · P2 · Nearest close date · Key incident(s).
- Then 2–3 recommended actions (e.g. escalate the incident tied to the largest deal closing soonest).
- Format amounts as currency (e.g. $1.2M, $450K). Only show totals computed from records, never untraceable estimates.
- If no high-priority incidents are open, say so and stop.
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
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.

