risk-identification
Skill41 starsChanged 21 days agoApache-2.0View on GitHub
Identify emerging risks, prioritize intake signals, and route candidates into formal GRC risk assessment workflows
1 other project uses a version of this.
Adopted by
Most recently taken up by
- xiejianjun000/FlowWikitheir own version, first seen Jul 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- xiejianjun000/FlowWiki★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository184 other files it gives its agents.
- happy-platform-skillsSkill
- application-scopeSkill
- batch-operationsSkill
- configuration-validationSkill
- deployment-workflowSkill
- generic-crud-operationsSkill
- instance-managementSkill
- schema-discoverySkill
- script-executionSkill
- script-syncSkill
- smart-assessmentSkill
- task-analysisSkill
- task-summarizationSkill
- update-set-managementSkill
- user-provisioningSkill
- workflow-creationSkill
- workspace-insightsSkill
- approval-summarizationSkill
- approval-workflowsSkill
- catalog-builder-aiSkill
- catalog-item-generationSkill
- item-creationSkill
- multi-turn-orderingSkill
- request-fulfillmentSkill
- ui-policiesSkill
- variable-managementSkill
- ci-discoverySkill
- cmdb-search-analysisSkill
- data-qualitySkill
- impact-analysisSkill
- relationship-mappingSkill
- service-graph-diagnosisSkill
- activity-responseSkill
- csm-case-summarizationSkill
- chat-recommendationSkill
- email-recommendationSkill
- csm-kb-generationSkill
- resolution-notesSkill
- csm-sentiment-analysisSkill
- csm-sidebar-summarizationSkill
- csm-suggested-stepsSkill
- trending-topicsSkill
- automated-testingSkill
- business-rulesSkill
- client-scriptsSkill
- code-assistSkill
- code-reviewSkill
- data-importSkill
- debugging-techniquesSkill
- fluent-sdkSkill
- glide-api-referenceSkill
- mcp-server-installationSkill
- mcp-serverSkill
- notificationsSkill
- performance-optimizationSkill
- scheduled-jobsSkill
- scripted-rest-apisSkill
- script-includesSkill
- servicenow-docs-mcpSkill
- test-generationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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
- Distinctive: line 39
Use this when risk managers need structured early detection, not only post-event summarization.
- Distinctive: line 45
Access: Read/write access to risk identification, profile, risk, and issue tables
- Distinctive: line 61
If your instance uses alternate table names, capture mappings before continuing.
- Distinctive: line 117
Write final intake rationale with scoring factors and escalation decision.
- Distinctive: line 133
Keep scoring model transparent and versioned
- Distinctive: line 134
Use consistent category mapping to avoid duplicate risk records
- Distinctive: line 144
Solution: Use schema discovery and update table mappings for your environment.
≈ “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
Risk Identification
Overview
This skill supports proactive risk identification in ServiceNow® before full assessment and treatment. It helps teams:
- Gather risk signals from business applications, issues, and operational events
- Classify and prioritize risk candidates
- Route high-priority candidates for formal assessment
- Maintain governance-ready evidence for risk intake decisions
Use this when risk managers need structured early detection, not only post-event summarization.
Prerequisites
- Roles:
sn_grc.manager,sn_risk.manager, oradmin - Plugins: GRC / Risk Management enabled
- Access: Read/write access to risk identification, profile, risk, and issue tables
- Policy Inputs: Risk taxonomy, scoring thresholds, and escalation criteria
Procedure
Step 1: Confirm Risk Identification Schema
Validate table and fields used in your instance for risk identification workflows.
Using MCP:
Tool: SN-Discover-Table-Schema
Parameters:
table_name: sn_risk_identificationIf your instance uses alternate table names, capture mappings before continuing.
Step 2: Ingest Risk Candidate Signals
Pull new or updated risk candidates and supporting context.
Using MCP:
Tool: SN-Query-Table
Parameters:
table_name: sn_risk_identification
query: stateINnew,under_review^sys_updated_on>=javascript:gs.daysAgoStart(7)
fields: number,short_description,state,category,profile,owner,likelihood,impact,sys_updated_on
limit: 100Step 3: Enrich with Profile and Historical Context
Gather profile posture and related historical risk records.
Using MCP:
Tool: SN-Query-Table
Parameters:
table_name: sn_grc_risk
query: profile=[profile_sys_id]^active=true
fields: number,short_description,state,residual_risk,inherent_risk,risk_score
limit: 50Step 4: Score and Prioritize Candidates
Apply an intake score based on impact, likelihood, velocity, and control coverage.
Suggested decision bands:
- High: escalate immediately to formal assessment
- Medium: assign analyst review with due date
- Low: monitor and capture rationale
Step 5: Create Follow-Up Actions
Route high/medium items into accountable next steps.
Using MCP:
Tool: SN-Create-Record
Parameters:
table_name: task
fields:
short_description: "Risk identification follow-up"
description: "Perform formal assessment for high-priority risk candidate."
priority: 2Step 6: Record Governance Evidence
Write final intake rationale with scoring factors and escalation decision.
Tool Usage
| Tool | Purpose |
SN-Discover-Table-Schema | Validate table names and field availability |
SN-Query-Table | Retrieve candidate, profile, and historical risk data |
SN-Get-Record | Inspect individual candidate details |
SN-Create-Record | Create follow-up tasks/issues for escalated candidates |
SN-Update-Record | Update candidate state and priority |
SN-Add-Work-Notes | Capture audit-ready intake rationale |
Best Practices
- Separate risk identification from risk treatment decisions
- Keep scoring model transparent and versioned
- Use consistent category mapping to avoid duplicate risk records
- Time-box analyst review for medium-priority candidates
- Link every escalation to an owner and target completion date
Troubleshooting
Risk Identification Table Not Found
Symptom: Query fails for sn_risk_identification.
Cause: Instance uses alternate table naming or scoped table variants.
Solution: Use schema discovery and update table mappings for your environment.
Too Many Low-Quality Candidates
Symptom: Intake queue grows without actionable prioritization.
Cause: Risk signal sources are noisy or scoring thresholds are too permissive.
Solution: Tighten intake criteria and require minimum evidence before escalation.
Related Skills
grc/risk-assessment-summarization- Summarize formal risk assessmentsgrc/risk-event-summarization- Summarize materialized risk eventsgrc/issue-validator- Validate quality of downstream GRC issues
References
- https://github.com/ServiceNow/ServiceNowDocs/blob/australia/markdown/governance-risk-compliance/grc-risk-management-workspace/workflow-risk-identification.md
- https://github.com/ServiceNow/ServiceNowDocs/blob/australia/markdown/governance-risk-compliance/grc-risk-management-workspace/risk-identification-overview-dashboard.md
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.

